Hi TDK, and thank you for your response.
I followed the guide you linked and built my JumpToBootloader function as follows:
#define BOOT_ADDR 0x1FF09800 // my MCU boot code base address
struct boot_vectable_ {
uint32_t Initial_SP;
void (*Reset_Handler)(void);
};
#define BOOTVTAB ((struct boot_vectable_ *)BOOT_ADDR)
void JumpToBootloader(void)
{
/* Disable all interrupts */
__disable_irq();
/* Disable Systick timer */
SysTick->CTRL = 0;
/* Set the clock to the default state */
HAL_RCC_DeInit();
/* Clear Interrupt Enable Register & Interrupt Pending Register */
for (uint8_t i = 0; i < 8; i++)
{
NVIC->ICER[i]=0xFFFFFFFF;
NVIC->ICPR[i]=0xFFFFFFFF;
}
/* Re-enable all interrupts */
__enable_irq();
// Set the MSP
__set_MSP(BOOTVTAB->Initial_SP);
// Jump to app firmware
BOOTVTAB->Reset_Handler();
}
I executed my function on the CM4 core and noticed that it doesn't work because it calls the HardFault_Handler function. Then, I executed the function on the CM7 core instead, and it works.
So, my first question is: Can I only call the bootloader from the CM7 core?
If the answer is yes, since my application code runs on the CM4 core, how do I call the function that's on the CM7 core from the application running on the CM4 core?
Once the bootloader is started, can I update both the CM7 core firmware and the CM4 core firmware?
I read Application Note AN4221, which explains the commands to use for operations on the microcontroller via I2C. Is there an example of how to upload a .hex or .bin file using these commands?
Finally, if something goes wrong and the new firmware isn't loaded correctly (e.g., the battery drains), I'll lose the ability to restart the bootloader because I've corrupted the firmware, right? In that case, I absolutely need to have access to the BOOT pin to put the microcontroller back into bootloader mode, right?
Thank you for your time.
