-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question/bug: recent CMSIS RTOS initialisation/memory/behaviour change (possible issue with #2642) #2786
Comments
Looking at the history, https://github.com/ARMmbed/mbed-os/commits/master/rtos , there's stack check enabled, some targets fixes, Thread class clean up. |
Thanks Martin. It's definitely one of those as, if I revert the changes in that directory, my target works again. Digging... |
It appears to be the Add RTX API to report stack usage commit, #2642, that's causing my problem. Investigating... |
If I include the |
It looks as though there might be an issue with #2642 (at least, there is for me). With the Now I'm not exactly sure what I'm doing here as this code is somewhat obtuse, and I've no idea why this isn't a problem for anyone else (possibly only those with Help! |
I've proposed changing |
Thanks for resolving this. |
I'm in the process of integrating a new target into mbed-os. A week ago, at #7669d7f, I had a working Pull Request that passed all the
htrun
tests ready to go. Because of RTX file change collisions I've had to rebase to #c1c1492 and now CMSIS RTOS doesn't even get intombed_sdk_init()
:rt_tsk_create()
returns 0.Can anyone point me at any recent changes to do with memory configuration, initialisation or RTOS behaviour before I start diffing the world and tearing my hair out?
Rob
The text was updated successfully, but these errors were encountered: