CubeMX minimal example not working correctly about dapboot HOT 2 CLOSED

As per the discussion on Gitter, it is possible that there is a conflict where the bootloader has configured peripheral registers that the CubeMX HAL expects to still be at their initial reset values. The obvious area of conflict would be the core system clock configuration and the SysTick, though I would expect it to tick at the wrong rate, rather than failing to tick at all.

I would suggest using a debugger that has support for viewing peripheral registers (using a CMSIS-SVD file), placing a breakpoint at the call to HAL_Delay(), and comparing the values of all major peripheral registers in the case where it works (without the bootloader, or with a pared down bootloader) vs the case where it does not work with the bootloader.

Assuming it is a peripheral conflict, you could then implement a target_pre_main() function to ensure that those peripherals are correctly reset before launching your application.

Depending on the scope of the changes needed, it would also be possible to roll those changes into the core bootloader code, but I don't have CubeMX setup, so it would be a bit difficult for me to test.

from dapboot.

Turns out it has nothing to do with the bootloader. STM libraries (HAL as well as StdPeriph) hard-code the IRQ vector table address to 0x8000000. They need to have the offset explicitly defined in the VECT_TAB_OFFSET parameter (for HAL) and don't read them from the linker script.

from dapboot.