Search results

Thank you for your response. After properly handling the interrupts, the issue resolved now i can be able load the firmware from secondary location. I have another question: is it possible to load the secondary firmware into a new region in flash without modifying bootdata.c and the linker script?

Thanks for the quicky reply I have modified the aforementioned files and built the image (I am using Teensy in vs code) MEMORY { ITCM (rwx): ORIGIN = 0x00000000, LENGTH = 512K DTCM (rwx): ORIGIN = 0x20000000, LENGTH = 512K RAM (rwx): ORIGIN = 0x20200000, LENGTH = 512K FLASH...

Thanks for the quick reply I will try that.also I could not be able to build the firmware for secondary location (0x60100000) I have tired using the custom linker script can you check and this thread and let me know if I am missing something...

Hello, I’m working on implementing Device Firmware Update (DFU) on the Teensy 4.0. In my primary firmware, I attempt to launch a secondary firmware image located at an offset within the flash memory using the following code: #if 1 FLASHMEM void disableCache() { // Disable Data and...

hi, I also have same requirement as below If your second application was built to start at an address 0x100000 into the flash (when it was built FLASH in the .ld file is modified to start at 0x60100000) then runApp(0x100000); i have included this function in my source FLASHMEM bool...