This thread has been locked.

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.

SYS/BIOS using the Task Example (Seperate Config Project) and getting multiple memory link sections overlapping...

Other Parts Discussed in Thread: SYSBIOS

I am using a 3rd party board and their examples work great.

Now I want to build one of my own and use SYS/BIOS in the project (using Code Composer Studio 4.2.4.00033).

The configuration package seems to have defined memory sections (given in SYSBIOS/System/Program under Available Memory Segments) IROM, IRAM, L3_CBA_RAM, and DDR.  IROM and IRAM overlap the linker.cmd file provided from the 3rd party.

I dont seem to be able to edit or delete these sections.

Any advice on what to do?

Thanks,

 

  • If you are using a custom board, one that is not listed in the RTSC platform drop-down menu, you should use the Platform Wizard and create your own platform. Then, use that platform instead of whichever platform you selected previously. Please let me know if you need more detailed help for these steps.

  • My intent was to use the one provided by the 3rd party.

    How do I tell wich one the 3rd party is using?

    Thanks for you help...

     

     

  • Do you mean that the 3rd party provided you a RTSC platform? Either way, you had to select something in the dialog box displayed below:

    So, when you start the Platform Wizard, use the platform from the circled field as a starting point and then adjust the memory map according to the provided linker command file. When you create a new platform, you create it in a repository that you have to add to the available repositories. In the attached screenshot, you can see under Other Repositories a directory that actually contains the RTSC platform I am using. You add these additional directories using the button "Add ..." on the right.

    For some device families (Stellaris, c2800, MSP430) you can use the provided linker command file directly. Let me know if you are building for one of these.