-
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
Twister: Broken on NRF52840 with pyocd option timeout error #39216
Comments
Could you try setting CONFIG_ NULL_POINTER_EXCEPTION_DETECTION= NULL_POINTER_EXCEPTION_DETECTION_NONE and see if that helps? |
Apologies for the delay, so this issue is related to #32984 which got auto closed for being stale. So, what part of the subsys this issue is related? West |
I am having the same problem when running twister with openocd and nrf. Setting CONFIG_NULL_POINTER_EXCEPTION_DETECTION_NONE=y in the testcase.yml works for me, but I do not understand why... |
Now a twister issue, this is the good old CONFIG_NULL_POINTER_EXCEPTION_DETECTION bug. |
This is essentially this issue: #33590 |
Having DWT-based NULL-pointer detection enabled by default trips a lot of users since it will make any debugging fail when enabled. Disable it by default and let users enable it if they desire to. Fixes zephyrproject-rtos#39216. Signed-off-by: Carles Cufi <[email protected]>
Having DWT-based NULL-pointer detection enabled by default trips a lot of users since it will make any debugging fail when enabled. Disable it by default and let users enable it if they desire to. Fixes #39216. Signed-off-by: Carles Cufi <[email protected]>
Describe the bug
The twister framework bails with timeout error when executed while choosing pyocd option as west runner
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Impact
Projects using pyocd with cmsis daplink firmware on nrf52840 dk board
Logs and console output
Environment (please complete the following information):
Additional context
There is one interesting observation though,the same twister command works on 2.5.0 version, and when we execute on 2.6 and higher we get this warning of possible DAPLINK:Overflow error, as highlighted below
The text was updated successfully, but these errors were encountered: