Skip to content
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

Conversation

erwango
Copy link
Member

@erwango erwango commented Mar 5, 2021

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]

@github-actions github-actions bot added the platform: STM32 ST Micro STM32 label Mar 5, 2021
@erwango erwango added the Hotfix Fix for issues blocking development, i.e. CI issues, tests failing in CI, etc. label Mar 5, 2021
@erwango erwango requested review from nashif, FRASTM, galak and ioannisg March 5, 2021 14:41
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]>
@erwango erwango force-pushed the fix_null_pointer_exception_detection branch from 2713a29 to 990a67f Compare March 5, 2021 14:54
@galak
Copy link
Collaborator

galak commented Mar 5, 2021

Does this only apply to STM32? Seems like the issue could possibly impact other Cortex-M based SoCs

@erwango
Copy link
Member Author

erwango commented Mar 5, 2021

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.
@ioannisg had a preference for this solution (cf #32867 (comment)). He might be able to comment more.
Meanwhile a wide bunch of STM32 tests are failing, so if this could be merged, even as a temp patch, it would be nice.

Copy link
Collaborator

@galak galak left a 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.

@ioannisg
Copy link
Member

ioannisg commented Mar 5, 2021

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.

@galak
Copy link
Collaborator

galak commented Mar 5, 2021

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.

@erwango erwango closed this Mar 9, 2021
@erwango erwango deleted the fix_null_pointer_exception_detection branch January 27, 2022 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Hotfix Fix for issues blocking development, i.e. CI issues, tests failing in CI, etc. platform: STM32 ST Micro STM32
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tests/kernel/sched/schedule_api does not start with stm32wb55 on nucleo
4 participants