A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
TMS320F28069: Combine two .out files/images and read back from password-locked MCU
I am working on a combination of two .out files (bootloader and application images). I have tried using hex2000 method based on the past related discussion in the forum. (e2e.ti.com/.../combining-out-files)
However, I met errors that said "memory ranges out of order". I have checked the .map files and makes sure there are no overlapping in Flash A~H. Only ROM has overlapping on section like CSM parts and reset but I used DSECT type on the application image.
Is there any guideline on the section allocation for combination of multiple .out ? like other than Flash A~H must not be overlapping or everything including RAM also follow. I am aware that processors.wiki.ti.com is EOL now, any alternative sources to find the explanation about the topic?
I have also tried other method which is to read back from the MCU that have boot and app images loaded and export the data on the whole FLASH A~H. For unlocked version it works fine. I could load back the exported .out to the MCU and the program can run normally. For locked version, I have successfully read back the whole Flash A~H using CCS and the password. When I loaded the exported .out to the MCU, the program can run normally. However, I cannot read back the FLASH using the password.
I would like to confirm whether the second method can be used as alternative of combining the images. Also, to read the whole data and program on MCU, I just need to read the flash A~H (start address: 0x3d 8000, size: 0x1 FFFF), right?
Is there any possibility to the second method that the Password is loaded wrongly? I set the password in the F2806x_CSMPasswords.asm.
I hope my issue description is clear and would like to get some feedback from TI experts here.
I have also tried other method which is to read back from the MCU that have boot and app images loaded and export the data on the whole FLASH A~H. For unlocked version it works fine. I could load back the exported .out to the MCU and the program can run normally. For locked version, I have successfully read back the whole Flash A~H using CCS and the password. When I loaded the exported .out to the MCU, the program can run normally. However, I cannot read back the FLASH using the password.
I would like to confirm whether the second method can be used as alternative of combining the images. Also, to read the whole data and program on MCU, I just need to read the flash A~H (start address: 0x3d 8000, size: 0x1 FFFF), right?
Is there any possibility to the second method that the Password is loaded wrongly? I set the password in the F2806x_CSMPasswords.asm.
I think I made a mistake I should read the Flash from start address: 0x3D 8000 with the SIZE 0x2 0000. Due to incorrect size, I omit PWL7 during the loading which is located at 0x003F 7FFF. So, PWL7 is set to 0xFFFF. After rectify the flash size, I can read the Flash using the Password without Issue.
Appreciate your response. I solved my issue 2&3 but issue 1 is still open. I am aware of user guide for Assembly Language Tools on https://www.ti.com/lit/ug/spru513p/spru513p.pdf But I would like to know more about a common guideline on the section allocation for combination of multiple .out.
I attached the bootloader and application map file below for your reference to check whether my section allocation violates any common guideline.
I'm not sure if the link to the E2E article you mentioned pointed here but thought I'd post it here in case this was helpful. It references the WIKI article as well, but has some extra steps to create the coff at the end.
In terms of the files that you attached, I see there are overlapping sections, but I assume these contain shared functions. Specifically the Lx RAMs seem to be used in both the .map files.
I don't think the map file will show me this, but I would think in one of the .outs for the overlapping sections you've defined this as NOLOAD, since the other coff will load it? If the data is same it shouldn't matter, but perhaps this is what is causing you issues.
I've used your approach #2 to do this myself, since CCS allows you to save off memory contents in .coff format so agree with everything you've mentioned there.
The E2E link above seems to be quite systematic. I will try the steps using my files.
So, Beside the sections from Flash A~B, Lx RAM sections must be separated and not overlap? I didn't know this because I assume RAM functions will be stored in FLASH and only FLASH sections is loaded to DSP. I will look more into Lx RAM allocations in that case to ensure there are no overlapping.
How about ROM sections like CSM password, etc.? I have specify one of them to be DSECT type.
Yes, Approach #2 works fine, I can load them with no issues by using Uniflash. However, I can not Load the combined COFF by using C2Prog from Codeskin. I planned to use their additional code security features. I am not sure if you're aware of their product (C2Prog), I probably need to contact them.
I think in case of sections we know will be the same, like the ROM, or password they can be defined in both projects. I'll see if there are some more examples we can reference to help clear this up more
I can not Load the combined COFF by using C2Prog from Codeskin
Just to clarify to others, C2Prog stated in their manual that it needs hex file with specified memwidth and romwidth. So, COFF file need to be converted to hex before it is used in C2Prog.
