In all of my projects I have my own bootloader which is located at 0x8000000 and is specially designed to communicate with my own Windows universal Flasher-Tool.
My bootloader initializes necessary components for the needed communication ports (e.g. USB) and looks into a defined flash address (0x08020000) for a start address of the final application.
This is flashed by the bootloader after the final application has been loaded to the application sectors (0x08080000 in this case).
If a correct address is read, then the bootloader deactivates Interrupts, unitializes components and jumps to the start-address + 4.
This handling works perfectly on my multiple other projects with STM32F4 and STM32F7 processors.
Now with the STM32H7 this does not work. The system simply crashes after the jump to 0x8080000 + 4.
I took care that the interrupt vectors are linked to the correct offset, have set SCB->VTOR to the offset 0x80000 and when I compare the flash memory with the hex file, all looks as expected.
But it doesn't work after the jump. Now i am stuck.
Does anybody know what might be the reason that the jump does not work? Is there anything else, which has to be initialized additionally?
Here is my code snippet of the jump part:
if (bApplVorh)
{
ARM_DisableAllInts();
HAL_DeInit();
__DI(); // Interrupts sperren
if (ulStartAppl == 0) // ulStartAppl = 0x8080000
ulStart = 0xFFFFFFFF;
else /* Test if user code is programmed starting from address "ulStartAppl" */
ulStart = (*(__IO uint32_t*)ulStartAppl);
if (ulStart != 0xFFFFFFFF) // FlashROM not empty?
{
/* Jump to user application */
JumpAddress = *(__IO uint32_t*) (ulStartAppl +4);
Jump_To_Application = (pFunction)JumpAddress;
/* Initialize user application's Stack Pointer */
__set_MSP(*(__IO uint32_t*) ulStartAppl);
Jump_To_Application();
}
// never returns to here !
}
