Why am I unable to use a custom linker command file using the Embedded Target for TI C6000?

I am trying to include my own linker command file when generating code for a model that has the "Incorporate DSP/BIOS" option checked in the "TI C6000 code generation" category under the RTW options.

I edit RTW Options, go to "TI C6000 linker" category, and specify the location of my custom linker command file. When I check on the generated project in Code Composer Studio, I find that the command file is not the one I specify but the one generated by DSP/BIOS according to the configuration (.cdb) file.

Answer 1

[MathWorks Support Team]

This has been verified as a bug in Embedded Target for TI C6000 DSP in the way that Embedded Target handles code generation.

Currently, to work around this issue, try the following steps:

1. Disable DSP/BIOS option.

2. If you need to use DSP/BIOS, you will have to enter your memory objects manually into the DSP/BIOS configuration (.cdb) file. Add memory segments in the MEM module, according to the physical memory present on the board. Then, modify the memory section assignments in order to optimize usage of internal and external memory.

Note: You have to modify the generated cdb file every time you generate code for a model. However, there is a way to streamline this process. Consult TI's documentation of the "tconf.exe" and "cdbcmp.exe" utilities, in ti/bin/utilities/tconf. First, generate code, then make a backup copy of the new cdb file. Then, apply your changes manually to the cdb file. Use cdbcmp.exe to compare the two cdb files and produce a tcf script which converts one to the other. Then, in future builds, you can use tconf.exe to add your customizations to any compatible cdb file.