CCS/TMDXIDK5718: Bug report CCBT-1993

Markus,

Please look at this HOWTO note for specifying different data load and run addresses for GNU targets: processors.wiki.ti.com/.../BIOS_with_GCC_(CortexA)

Doing this, every time the program starts over the .data section runtime locations will get reinitialized from the initial values the loader placed in memory.

Is this what you are looking for?  If not, can you please clarify the specific use case and issue you are having?

Thanks,
Scott

Hi Scott

Concerning your suggestion "if you specify addresses instead of segments do you see the same result?":
Yes, I also tried this, but the result is the same. The load address is not used.

Thank you for involving an other engineer.
I'm Looking forward to his answer.

Regards,
Markus

OK, thanks Markus.

Sorry for the delay.  I haven’t heard back yet from the engineer assigned your thread.  I’ve not used the SDK you are using, and I’m hoping he may be able to recognize what the problem is.

I hope to get a response for you soon…

Regards,
Scott

Hi Scott

Any updates on this question?

Regards,
Markus

Hi Markus,

I did make contact with Eric and saw that he replied to your original thread.  I left it at that, and didn’t know you were still having an issue.  At the time I probably should have asked for this thread to be closed as a duplicate.  

Anyways, sorry for the delay.

I now see your reply back to him on that other thread, that it works for your own sections, but not for predefined sections like .text, .data etc.  When I’d experimented I’d moved .data without any issue.  My guess is that the problem relates the custom platform somehow.  There is an engineer at my local site that I can ask about this (he wrote that HOWTO info on the wiki), but he has left for the day.  I will talk to him tomorrow and see if he has any suggestions…

Regards,
Scott

Hi Markus,

I heard back.  The trick described on the wiki page generates a second placement directive, with the goal that it will override the default directive auto-generated within the platform.  This override has since been found to not work for some linker versions.  This is probably what is happening for your project.

An alternative that forces the different load and run addresses for .data is to edit your custom platform to separately partition code and data regions.  By default the auto-generated linker script places the .data section into Program.platform.codeMemory, and has the run address in Program.platform.dataMemory.  If you edit your memory configuration to have codeMemory and dataMemory point to different memory regions then this will result in different load and run addresses for .data, allowing the .data values to be re-initialized when the CPU is reset.

Does this work for you?

Thanks,
Scott  

Hi Scott

I changed to platform settings as follows:

This did the trick:
The section ".data" now has separate load and run addresses (load: DDR_CODE, run: DDR_DATA).

I also added the following to my config file:

Program.sectMap[".data"] = new Program.SectionSpec();
Program.sectMap[".data"].loadSegment = "DDR_CODE";
Program.sectMap[".data"].runSegment = "DDR_DATA";

Strangely after I did this the program always crashes before main().
But it works when I remove those lines.
Any ideas why this is wrong here?

Regards,
Markus