-
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
cmsis5/rtx2: ST: execution never leaves SystemInit #3683
Comments
Hi,
|
I know it is ok on master and the feature branch is almost up to date with master anyway. But it seems to be broken (for all ST platforms I've tried) with the update to cmsis5/rtx2 and my debugging led me into bowels of the platform. It's the change we'll be landing soon on master and I'd like to have ST boards passing all the tests. Could you guys help us with debugging it please. |
ping |
Hi, I have installed the latest uVision V5.23 toolchain and generated a project using "mbed export" in order to start debugging. But I have these 2 errors:
It's strange because when I compile with Do you use a uvision project for your debug ? |
I don't generally use windows, but yes when I was trying to debug this issue I was using uVision 5.20 (ARMC 5.06). It seems that the flag is correctly set |
I don't know if this is feasible or not ? Anyway I have commented the 2 lines just to see if the rest was ok and I have now 4247 errors during linking...
... |
Do you have similar issues on |
Yes same error on master. |
OK, it explains a lot I did a rebase on monday. You mind creating a bug report for master? |
@bcostm I manage to reproduce the issue with current master and only CMSIS changed, I prepared branch for F401 https://github.com/bulislaw/mbed-os/tree/st401_update_cmsis_no_rtx |
I have now a uvision project that compiles thanks to the fix Martin suggested. I have tested your branch
The basic test hangs after "tick 10" print and there is a timeout (?)
Are you sure it hangs for you ? or maybe I misinterpreted what you wrote and the Do you confirm my results ? |
I retested the |
Yes I tried also yesterday to debug the feature_cmsis5 branch with a simple blinky program but I didn't find anything... |
Humm... I have retested this morning the
But all other tests are fail:
|
I have generated a uVision project from the feature_cmsis5 branch. I have these warnings for non-declared functions: Other thing: When I compile the rtos-basic test main.cpp, I have an error due to the DEFAULT_STACK_SIZE not declared. In the master branch this is defined in the rtos/rtx/target_cortex_m/cmsis_os.h file. But I didn't find it in the feature_cmsis5 branch ? |
@bcostm we will fix those warnings, I was planning to send a patch |
The DEFAULT_STACK_SIZE was removed, I have fix for the tests, I'll merge it soon. As for the test results, I'm getting timeouts for all tests for |
@0xc0170 any news? |
@bcostm I've got some results, that looks similar to yours. Could you please have a look at the failures. I think the issue with building tests is resolved now. ARM:
GCC(v6):
|
OK no more error due to the DEFAULT_STACK_SIZE, I can compile the project but I still have these warnings:
|
We've found something that seems to fix the issue (thanks @jamike) but we need first to launch a full non-regression tests on all our platforms to see if this doesn't break anything else... I'll keep you updated. |
@bcostm any news? |
Hi, |
That's fixed now. |
Description
Bug
Target
ST platfoms (tested with NUCLEO F401RE and F411RE)
Toolchain:
GCC_ARM ARM
We're trying to finalize CMSIS5/RTX2 (https://github.com/ARMmbed/mbed-os/tree/feature_cmsis5) update in next month or two, but we're having issues with ST platforms. When executing tests (eg
mbed test -n tests-mbedmicro-rtos-mbed-basic -m NUCLEO_F401RE -vv
) I'm getting a timeout. I had a bit of troubles trying to debug the issue, but as far as i can tell the execution never leavesSystemInit
, it's stuck inTIM5_IRQHandler
in an infinite loop. While stepping through the code it seems the interrupt was happening while trying to access SysTick counter (HAL_GetTick
), but I'm not 100% sure.@0xc0170 Could you ping some ST people, maybe they could have a look into it?
CC: @sg- @c1728p9
The text was updated successfully, but these errors were encountered: