-
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
soc: stm32: Disable null pointer exception detection by default #32983
soc: stm32: Disable null pointer exception detection by default #32983
Conversation
Null pointer exception detection systematically triggers an assert when program is run with debug mode on, which is currently systematic when flashed using openocd runner. Until this is fixed in openocd, make sure this detection is not enabled by default (which is currently the case in zephyr tests). Signed-off-by: Erwan Gouriou <[email protected]>
2713a29
to
990a67f
Compare
Does this only apply to STM32? Seems like the issue could possibly impact other Cortex-M based SoCs |
Not sure, but this was dicussed in #31481. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So this issue is related to openOCD and not STM32, so I think it best we try and find an OpenOCD solution. ie can we have the west runner
for openocd set the mode correctly.
Fully agree, though, I wanted to unblock, temporarily, @erwango , that's why I +1'ed this. |
If we want to unblock than we should disable the feature completely for now. Since non-STM32 OpenOCD users will run into the same issue. |
Null pointer exception detection systematically triggers an
assert when program is run with debug mode on, which is currently
systematic when flashed using openocd runner.
Until this is fixed in openocd, make sure this detection is not
enabled by default (which is currently the case in zephyr tests).
Fixes: #32867
Signed-off-by: Erwan Gouriou [email protected]