HAL_Delay() function is not working after jump from Bootloader

[asukarnikhil]

Hello,

I am working on NUCLEO-F070RB board, I have developed the Custom Bootloader Code

to test the Bootloader functionality I am using blinky application with HAL_Delay(1000);

When I run the blinky application independently the application is working fine.

When I remove the HAL_Delay(1000); function and use for(int i = 0; i< 1000000; i++); for the delay, the Bootloader is successfully jumps to application and led starts blinking

from above cases I observed that there is issue with HAL_Delay() function with jump from  bootloader to application

Can you explain what could be the issue and how to resolve it.

following is the function to jump from bootloader to application .

void Bootloader_JumpToApplication(void)
{
#if DEBUG_ENABLED
UART_Debug_Print("Gonna Jump to Application\n");
#endif
void (*app_reset_handler)(void) = (void*)(*((volatile uint32_t*) (APP_START_ADDRESS + 4U)));

__disable_irq();

/* Jump to application */
app_reset_handler();
}

[######]

Hello,

Other users will probably have more experience knowledge, but I believe for the F0 series there is something extra that is required with the Vector Table Offset Register VTOR. I think this needs to be amended to match the new start of code execution.

Because HAL_Delay uses Systick interrupt it may be that your VTOR value is incorrect, hence the Systick version doesnt work.

Apologies in advance if this is misleading / not the case.

[Tesla DeLorean]

Check if you disabled MCU interrupts and didn't re-enable

Check code in SystemInit(), or wherever, pointed SCB->VTOR at the location of your new/current vector table basis.

For the Cortex-M0 you'll need to copy the vectors to the base of RAM, and then remap that at zero. Likely via SYSCFG / RMP. Check for IAP code examples within CubeF0