Hi，
https://e2e.ti.com/support/processors/f/791/t/948438
Please see the question in this post, I accidentally clicked on reslove。
Can you tell me about the risks? Then what should we do to avoid these risks?
1.Then I have another question. When xip is running, it will jump to the address 0x500e0000 to run, and the .rstvectors is also at the address 0x500e0000; but the arm core will run from the address 0x0 after each reset, then do we need to copy a copy of the .rstvectors To address 0x0?
2.Is the app file required for xip running in *.bin format (such as can_profile_xip_app_mcu1_0_release.xer5f.bin)? Can it be in other formats? Such as *.HEX?
3.We compiled in the windows environment, and then used armobjcopy.exe to convert *.out to *.bin file, but the generated bin file is much larger than the out file. We think this is because of the problem of address discontinuity. How to avoid it What about this problem? I will attach our lds file later to help you troubleshoot problems
lds file:
map file:
Can you explain in detail how to implement data cection relocation in xip mode?
At what stage is relocation implemented? Which piece of code does this function? I did not find it in the SDK package
Regards,
Xie
