-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
tests/kernel/sched/schedule_api does not start with stm32wb55 on nucleo #32867
Comments
It seems that with the nucleo_wb55rg, the CoreDebug is at address 0xe000edf0:
|
We actually have a whole bunch of tests failing with this commit on various platforms (tests/drivers/gpio , ...). |
Will take a look asap, thanks. |
@erwango I guess the problem is that you are trying to execute tests on the board with the Debug mode on. But this should not be the case, right? I believe that west flash should never leave the Debug mode on. If some runners do that, I would argue we need to fix the runners instead. I noticed the problem in openOCD, but might be more runners that do the same... |
@ioannisg, confirmed this is due to debug mode being enabled by runner. As discussed, waiting for this to be fixed in various runners (openocd at least), let's remove the assert temporarily. |
@erwango removing the assert will still make several tests failing due to a raised DebugMonitor exception, it is not a complete workaround. Better to disable null pointer exception detection feature in these stm32 platforms where west flash leaves the debug mode on. |
@ioannisg That's the whole family then (which is easier). Ok, let me do that. |
That' fine with me. As discussed offline, we need to track the openOCD issue (ideally in a different ticket). |
What is the Debug mode referenced here. Are we talking about building Zephyr with DEBUG enabled or some hardware mode? |
Hardware mode. It's about the debugger leaving the DHCSR bit0 to 1 after flashing. |
This issue is fixed, tests/kernel/sched/schedule_api passed on nucleo_wb55rg
|
Describe the bug
when testing the tests/kernel/sched/schedule_api on the nucleo_wb55rg board form STMicroelectronics, the test does not start.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
test PASSED
Logs and console output
none
Environment (please complete the following information):
Additional context
The kernel is falling in the
__ASSERT((CoreDebug->DHCSR & CoreDebug_DHCSR_C_DEBUGEN_Msk) == 0,
of the arch/arm/include/aarch32/cortex_m/dwt.h
This is a new ASSERT command which is added by the commit "arm: cortex_m: assert if DebugMonitor exc is enabled in debug mode" (2c45c82)
from PR #31481 "Implement null-pointer de-referencing detection for Cortex-M"
The text was updated successfully, but these errors were encountered: