How to debug user application firmware after relocated it from the base 0x70000000 to 0x70040000.

[Phang]

Hi, 

I'm facing a problem where either the EVKMiMXRT1064 eval board or our own board cannot run DEBUG mode after relocated the user application firmware's "PROGRAM FLASH" from location 0x70000000 to 0x70040000. The size the of the user application firmware is 0x3c0000. Am I missing any configuration in order to get the debug mode work? Thanks.

[djarin]

Hi, i tried appending a mkimage header (64bytes length) at the starting of the binary file (hex/bin).

Which also mean that this header file will be on top of the FCB/IVT/DCD.

Is there an option for me to offset this 64 bytes, so that the ROM bootloader can locate the FCB for QSPI initial init?

Thanks

[Phang]

Hi Jing, 

1. Does this "put application code to 0x70040000 but still put FCB/IVT/DCD at 0x70000000." action will conflict with the bootloader later?  I'm using MCU Xpresso IDE for firmware development.

2.  How do you do this "put application code to 0x70040000 but still put FCB/IVT/DCD at 0x70000000."? Can you give sample file if it is done is linker script file else can share with me the settings or configuration. 

Thanks.

[jingpan]

Hi @Phang ,

1. If you have flash bootloader, you should add IVT/DCD/FCB to flash bootloader image. 

2. There is two position need to be change.

 The RT1170_reset.scp read PC and stack pointer from your image, the address should be change to 0x4000.

And the linker file.

After modify the file, you should not let IDE manager linker scriptor.

Regards,

Jing

[jingpan]

Hi @Phang ,

You can put application code to 0x70040000 but still put FCB/IVT/DCD at 0x70000000. Otherwise, ROM bootloader can't find data to config QSPI flash and entry address.

Regards,

Jing