-
Notifications
You must be signed in to change notification settings - Fork 233
[nrf fromtree] boot: zephyr: RAM cleanup debug loop #460
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
base: main
Are you sure you want to change the base?
Conversation
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.
submit upstream?
boot/zephyr/Kconfig
Outdated
bool "Loop after RAM cleanup" | ||
depends on MCUBOOT_CLEANUP_RAM | ||
help | ||
Debug option that keeps execution in infinite loop after RAM cleanup |
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.
Shouldn't this be called "test" or "verification" option, and Kconfig named accordingly?
boot/zephyr/main.c
Outdated
@@ -294,6 +294,9 @@ static void do_boot(struct boot_rsp *rsp) | |||
" b clear\n" | |||
"out:\n" | |||
" dsb\n" | |||
#if CONFIG_MCUBOOT_LOOP_AFTER_RAM_CLEANUP |
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.
Grumpy me would still prefer scripting gdb, but not going to put up a fight over this.
3a5fa0c
to
e8642c9
Compare
Some problems with commit tags |
Needs fix so CI passes |
Option to put execution in infinite loop. Meant to be used for debug. Signed-off-by: Mateusz Michalek <mateusz.michalek@nordicsemi.no> (cherry picked from commit 5eaf190a8a9d8fc032b989bf96fc56b3b756dd55)
|
Option to put execution in infinite loop.
Meant to be used for debug.