fix(bootloader): keep the DFU jump out of secure-boot bootloaders

The ROM's DFU bootloader writes any image, so a bootloader that checks
signatures would let reboot -i get past them. Those boards just restart
the app on reboot -i.
This commit is contained in:
Jacob Dahl committed 2026-11-20 12:13:43 -07:00
1 parent 599340727e
commit cd265fe1a7
1 file changed
+2 -1
@@ -658,7 +658,8 @@ arch_do_jump(const uint32_t *app_base)
for (;;) ;
}
#if defined(CONFIG_ARCH_CHIP_STM32H7)
/* A bootloader that checks signatures leaves this out, because the ROM's DFU bootloader writes any image. */
#if defined(CONFIG_ARCH_CHIP_STM32H7) && !defined(BOOTLOADER_USE_SECURITY)
/* NuttX's __start calls this before any clock setup, so the chip is still as reset left it, which is how the ROM's
* DFU bootloader expects to find it. The app asks for it with reboot -i.
*/