TMS320F28379D: C2000ware example compiling error

Hello,

1. Which C2000Ware example? Can you share path? Also please share the C2000Ware version you're using?

The reason you are getting this error is a COFF/EABI mismatch.

Option 1: If you want to use the EABI (ELF) format 

1. Update Linker Settings:
   • Open your project in Code Composer Studio (CCS).
   • Right-click the project and select Properties.
   • Navigate to C2000 Linker -> File Search Path.
   • Look for rts2800_fpu32.lib in the "Include library file..." box.
   • Remove rts2800_fpu32.lib
   • Add libc.a instead. When you use libc.a, the linker will automatically select the correct EABI-compatible version (e.g., rts2800_fpu32_eabi.lib) for you.
2. Verify C2000Ware:
   • Ensure you are using a modern version of C2000Ware (v3.00.00 or later), as older versions primarily provided COFF-formatted libraries.
3. Clean and Rebuild:
   • Perform a Project ->Clean to remove any old .obj files before rebuilding.

Option 2: If you want to use the Legacy COFF format

1. Change Output Format:
   • In Project Properties, navigate to General.
   • Ensure the Output format is set to legacy COFF [ti_coff].
2. Check Object Files:
   • If you recently switched from EABI to COFF, you might have leftover .obj files in your Debug/Release folders that were compiled as ELF. Delete the entire Debug or Release folder to ensure a fresh COFF build.

Thanks,

Ira

Hi Holger,

If you are migrating from COFF to EABI then you also need to make some changes in your linker command file.

Fix the "creating output section without a SECTIONS specification"

Go to you .cmd file and and add the following in your SECTIONS block.

SECTIONS
{
/* ... existing sections like .text, .econj, etc ... */

/* Add these to satisfy the EABI linker requirements */
.init_array : > FLASH, PAGE = 0 /* Or wherever your code resides */
.data : > RAMLS0, PAGE = 1 /* Adjust RAM block to your device */
.bss : > RAMLS0, PAGE = 1 /* Adjust RAM block to your device */

/* If you have initialized data, you might also need .dseg */
.dseg : > RAMLS0, PAGE = 1
}

Note: Ensure the memory ranges (FLASH,RAMLS0, etc.) match the names defined in your MEMORY block at the top of the .cmd file.

 Fix the "unresolved symbols" (Ramfuncs)

The symbols RamfuncsLoadStart, RamfuncsLoadSize, and RamfuncsRunStart are used by the C2000 startup code to copy functions from Flash to RAM at runtime. In EABI, the linker needs to be explicitly told to group these and provide the addresses.

SECTIONS
{
    /* ... */
    .TI.ramfunc : Load = FLASH, Run = RAMLS0, Load addresses into FLASH 
                  and runs from RAM.
    /* ... */
}

Check your F2837xD_SysCtrl.c or your startup file to see if it is looking for .TI.ramfunc or a custom .ramfuncs section. If the error persists, ensure the section name in your .cmd file matches the section name attribute in your C code (e.g.,
#pragma CODE_SECTION(..., ".TI.ramfunc")

).

I highly recommend going through C2000 Migration from COFF to EABI, specifically the section on Linker Command File Changes.

You could also simply go ahead with option 2 if you want to stay COFF.

Thanks,
Ira