I made a bootloader that makes it possible to program the device in application. The bootloader software uses interrupts and communicate over an RS485 bus. When I jump to the base address of my firmware, it seems that the interrupts aren't working. I use the command below to redirect the vectortable in the firmware.
NVIC_SetVectorTable(NVIC_VectTab_FLASH, 0x08008000);
The method of jumping to my applicaton is the one documented in the AN2557.
static const uint32_t FIRMWARE_START_ADDRESS = 0x08008000ul; typedef void (*pFunction)(void); ... //Initialize jump to firmware uint32_t startAddress = *(__IO uint32_t*)(FIRMWARE_START_ADDRESS + 4); pFunction RestartFirmware = (pFunction)startAddress; //Initialize firmware Stack Pointer */ __set_MSP(*(__IO uint32_t*)FIRMWARE_START_ADDRESS);
I've tested the code and the jump occurs, and the code is run, but none of my interrupt driven deviced work properly.
I've tested the code by using the example from the AN2557 to jump to the my bootloader (recompiled to address 0x08002000) and then the jump to my bootloader works. Then I let my bootloader jump back (FIRMWARE_START_ADDRESS = 0x08000000) to the AN2557 bootloader and that also worked. But when I jump for a second time to my bootloader it doesn't work anymore. I've added the vector redirection to both projects and it still doesn't work.
My bootloader is written in c++. Most of my hardware is managed by singleton classes. Is something not initialized properly (statics)?
I've solved the problem. The reset input was connected in such a way that the internal reset circuit couldn't drive the reset correctly. I've change de external reset circuit (is now open collector driver) and the NVIC_SystemReset() works. (The Watchdog didn't work either, but works fine now).
I've also changed part of the code so that I de-initialize all the periferals before I try to jump to the other application. Every class will now neatly deinitialize the used periferals on destruction.
well done ;-).