I have a STM32F407 application, developed with standard libraries which is launched by a bootloader. The application is loaded at flash address 0x08020000, the bootloader, once recognized a valid application at that address, reset the stack pointer and then set the PC to jump to the first instruction
/* ----------------------------------------------- */
/* Jump to user application */
JumpAddress = *(__IO uint32_t*) (USER_FLASH_FIRST_PAGE_ADDRESS + 4);/* +4 perché è lì che c'è il main */
Jump_To_Application = (pFunction) JumpAddress;
/* Initialize user application's Stack Pointer */
__set_MSP(*(__IO uint32_t*) USER_FLASH_FIRST_PAGE_ADDRESS);
SysTick->CTRL = 0;
SysTick->LOAD = 0;
SysTick->VAL = 0;
everything is fine.
Now I have a second application very similar to the first, which has been developed with HAL libraries.
I can debug this application with no problems but when I flash the bin at the location 0x08020000 with the same bootloader as before flashed at 0x08000000, it does not start (or probably it crashes during the init).
When the bootloader jumps to the application, in fact, it hangs up. I am not able to debug the application from bootloader (is it possible with STM32_SW4?) but what I can check is that:
1) The application JumpAddress corresponds to the address i red from the 4th byte fo the bin file.
2) The stack pointer is set correctly as in the first 4 bytes of the bin which is the end address of the SRAM.
3) The isr_vector table is placed at 0x08020000 as I see from the .map
.isr_vector 0x08020000 0x188 ..\obj\startup_stm32f4xx.o
What could the cause of this behaviour?