SPRACM8A June 2019 – January 2021 OMAP-L132 , OMAP-L132 , OMAP-L138 , OMAP-L138 , TMS320C6742 , TMS320C6742 , TMS320C6746 , TMS320C6746 , TMS320C6748 , TMS320C6748
If you are using SYS/BIOS, system start up and initialization is handled by XDCtools. For some targets, the c_int00 code is a C function. The C code is compiled with the "-mo" flag, which places the symbol _c_int00 in a subsection of .text (.text:_c_int00).
To place the .text symbol at an explicit address, add a custom linker command (.cmd) file to your project with a directive similar to:
SECTIONS {
.text:_c_int00 > 0xc3000000
}
On other targets, the _c_int00 code is written in assembly language. As of XDC 3.24.02, this assembly code is placed in .text and not .text:_c_int00. This will be fixed in a future release of XDC and BIOS. But, until then, the following linker workaround can be applied to place the _c_init00 function. You will have to update your path and library name accordingly. Check your .map file for the name of the boot library and the generated linker.cmd filed for the full path.
boot : > 0x3D8000 PAGE = 0
{-l"C:\ti\ccsv5_3_0_00042\xdctools_3_24_02_30\packages\ti\targets\rts2800\lib\boot.a28FP" <boot_cg.o28FP> (.text)
}