CCS 5.1.0.09000 - Trying to change Linker Sections for the app.cfg file for SYSBIOS and it keeps becoming undefined?

Can you share your app.cfg file so that I can see how you're attempting to place the sections in different memory segments?

Below is an example of how to place the ".text" section in the memory "L3_CBA_RAM" segment.

Program.sectMap[".text"] = new Program.SectionSpec();
Program.sectMap[".text"].loadSegment = "L3_CBA_RAM";

Alan

The following FAQ also addresses this topic:

    http://processors.wiki.ti.com/index.php/SYS/BIOS_FAQs#3_Placing_SYS.2FBIOS_code_in_different_memory_segments

Alan

 I am using the XGCONF utility to edit the file.

It looks like the second line above is missing.

Are you not supposed to use XGCONF?  How do I edit all the other paramaters in the file.

So I edited it with the Text Editor and it seems to stick now.

So this looks like a parsing error from XGCONF?

So is the configurations of SYSBIOS documented so that I can create it from the Text Editor?  Sounds painful.

Thanks,

Mike,

If you enclose the memory segment name in quotes (ie "L3_CBA_RAM") I think xgconf will work.

Alan

I need to take that last suggestion back.

I was able to reproduce the behavior you described only once.

And it seemed to behave correctly when I surrounded the memory segment name in quotes.

Now I can't get it to misbehave (with or without quotes).

Which version of SYS/BIOS and XDC tools are you using?

Alan

I tired the quotes and it did not work for me.

Since you have only been able to reproduce it once, I am wondering if this might be a configuration issue?

SYS/BIOS - 6.32.5.54

XDCtools - 3.22.4.46

Thanks,

One more thing, since I added the .text section using the Text Editor as you suggested, that seems to be holding.

If I use XGCONF to change it, it does go back to L3_CBA_RAM.

Thanks,

Can you provide a screen shot of the what the xgconf page looks like when you've unsuccessfully added a section with it?

Alan

Before Save...

 After Save...

Well, I didn't really get to the bottom of it. But if you're "enabled" now, I'll set this issue aside for the moment.