Skip to content

Support for eCos/eCosPro#97

Open
RallySmith wants to merge 3 commits into
mcu-debug:mainfrom
RallySmith:ecospro
Open

Support for eCos/eCosPro#97
RallySmith wants to merge 3 commits into
mcu-debug:mainfrom
RallySmith:ecospro

Conversation

@RallySmith
Copy link
Copy Markdown

Initial support for eCos run-times.

The work is (apart from the minor references in the existing "RTOS Views" files) self-contained in the new rtos-ecos.ts source. It is an initial, basic, thread list view. If the changeset is acceptable and merged then I do intend to extend the eCos functionality to present more useful "system run-time state" information as opposed to just the thread view.

Apologies in advance for my rudimentary TypeScript skills.

@PhilippHaefele
Copy link
Copy Markdown
Collaborator

Hi @RallySmith

Thanks for contributing the eCOS support.

Is there an easy way to get an eCOS example for an STM32F429 running?

Best regards
Philipp

@haneefdm
Copy link
Copy Markdown
Contributor

Thank you very much. Could you also fix the lint errors?

@RallySmith
Copy link
Copy Markdown
Author

Is there an easy way to get an eCOS example for an STM32F429 running?

I assume you mean a stm32f429i_disco (rather than the eval board)?

If so: I have placed a simple test ELF on my local web server:
http://www.rallysmith.co.uk/stm32f429i_disco_kmutex4
and the source for that test:
http://www.rallysmith.co.uk/kmutex4.c

Annoyingly it would be quite a few hoops to get a complete source and build world for you, since I only have the eCosPro sources to hand - hence just providing a binary and the source for that test case just now in the hope that it is useful.

At least that way you could at least set some BKPTs on the function names, or system calls and satisfy yourself that the XRTOS display reflects the thread status.

kmutex4 is just one of the standard kernel test suite applications, and just bashes a few mutexes with a few threads.

You can have the Cortex Debug OpenOCD (or whatever) setup halt on cyg_user_start to get past the run-time init and stop on startup at the test code start, and if you want you can also set a BKPT on cyg_test_exit to catch the end of the code (since it just busy loops on termination). Diagnostic output is to the VCP (STLink) 115200 8N1 and it just outputs some status as it barrels along.

@RallySmith
Copy link
Copy Markdown
Author

Thank you very much. Could you also fix the lint errors?

Pushed. Cheers

@haneefdm
Copy link
Copy Markdown
Contributor

A Nucleo is fine if you can get it. Disco's are pricey arent they...

@RallySmith
Copy link
Copy Markdown
Author

A Nucleo is fine if you can get it. Disco's are pricey arent they...

Sadly I do not have in my collection a NUCLEO-F429ZI and it seems that they are harder to get hold of these days (none of the standard main suppliers have stock; and eBay is asking silly money).

I could provide binaries for the NUCLEO-H723ZG or NUCLEO-L476RG. Mostly the available eCosPro STM32F/H/L targets are for -DISCO or -EVAL boards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants