TMS320F2812 CCS 4.2.3 unresolved symbol errors when building the project imported from CCS 3.3

Looks like the legacy project migration was not fully successful. You are most likely missing a reference to a library in the project settings which has these symbols. Is there a 'migration.log' file that was generated inside your project folder?

Thanks

ki

HI Ki thanks for the reply.

Actually No such file is created in the project folder..

ok, you'll need to determine which library is missing and add it to the build. I would suggest looking at your CCSv3.3 project file (*.pjt) and see all the included libraries and compare it with your v4 project.

I am getting the below shown warning as well.

'Building target: C:/Sample/BT/DSP_CEI_BT.out'
'Invoking: Linker'
"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c2000/bin/cl2000" --silicon_version=28 -g -O1 --define="_DEBUG" --define="LARGE_MODEL" --quiet --diag_warning=225 --issue_remarks --large_memory_model --asm_listing --obj_directory="C:/Sample/Debug" -z -m"C:/Sample/Debug/DSP_CEI_BT.map" --warn_sections -i"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c2000/lib" -i"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/c2000/include" -i"C:/Program Files/Texas Instruments/bios_5_40_02_22/packages/ti/rtdx/lib/c2000" -i"C:/Program Files/Texas Instruments/bios_5_40_02_22/packages/ti/bios/lib" -i"C:/Sample/DSP_BT" -i"C:/Sample" --reread_libs --absolute_exe --rom_model -o "C:/Sample/BT/DSP_BT.out"  "C:/Sample/Debug/TL_EXTERN_API_TABLE.obj" "C:/Sample/Debug/StartupMode.obj" "C:/Sample/Debug/ResetVector.obj" "C:/Sample/Debug/BT_Version.obj" "C:/Sample/Debug/BT_UT_Test_RAM.obj" "C:/Sample/Debug/BT_UT_Move_Block.obj" "C:/Sample/Debug/BT_UT_Fill_RAM.obj" "C:/Sample/Debug/BT_UT_Calculate_Checksum16.obj" "C:/Sample/Debug/BT_UT_Calculate_CRC32.obj" "C:/Sample/Debug/BT_API_TABLE.obj"
warning: creating output section ".econst" without a SECTIONS specification
warning: creating output section "BOOTSTATESECT" without a SECTIONS
   specification
warning: creating output section "BTAPITBL" without a SECTIONS specification
warning: creating output section "BTCDSEC" without a SECTIONS specification
warning: creating output section "BTRAMFUNC" without a SECTIONS specification
warning: creating output section "BTVERSEC" without a SECTIONS specification
warning: creating output section "COMPLWRMSTARTSECT" without a SECTIONS
   specification
warning: creating output section "codestart" without a SECTIONS specification

 undefined                  first referenced                               
  symbol                       in file                                    
 ---------                         ----------------                               
 __BTDT_START        C:/Sample/Debug/StartupMode.obj
 _btRamFuncLdEnd     C:/Sample/Debug/ResetVector.obj
 _btRamFuncLdStr       C:/Sample/Debug/ResetVector.obj
 _btRamFuncRnStr       C:/Sample/Debug/ResetVector.obj

error: unresolved symbols remain
error: errors encountered during linking;
   "C:/Sample/BT/DSP_BT.out" not built

>> Compilation failure
gmake: *** [C:/Sample/BT/DSP_BT.out] Error 1
gmake: Target `all' not remade because of errors.
Build complete for project DSP_BT

Hi Ki,

Any solution to the above mentioned issue.

yogendra tanguturu said:

 undefined                  first referenced                               
  symbol                       in file                                    
 ---------                         ----------------                               
 __BTDT_START        C:/Sample/Debug/StartupMode.obj
 _btRamFuncLdEnd     C:/Sample/Debug/ResetVector.obj
 _btRamFuncLdStr       C:/Sample/Debug/ResetVector.obj
 _btRamFuncRnStr       C:/Sample/Debug/ResetVector.obj

Do you know where are these symbols defined? Are they from a library?

I think The above symbols are not from a library.

_BTDT_START is the Starting address of Boot Config Tabel.

extern BT_CONF_TBL  _BTDT_START; 

I had included the headerfile in which BT_CONF_TBL is declared.

The extern is saying that _BTDT_START is defined elsewhere and you need to make sure that the file which contains the "definition" of those symbols is included in the build.

The linker warnings say that those output sections do not have a SECTIONS specification in the linker command file, so the linker will use some default algorithm to place those sections in memory. It is advisable to modify the linker command file to specify placements for those sections so the allocation is within your control and the warnings will be eliminated.

Hi Arthi,

I am using the same build which was used in CCS 3.3 and I am able to compile wiht out any warnings/ Erros in CCS 3.3

The same build I had imported to CCS 4.2.3.

CCS 4.0.1 was installed and I updated CCS to 4.2.3 and then imported the CCS 3,3 working projec.

Will the upgradation might cause any problems since the Same build I am able to compile in CCS 3.3

It is hard to tell for sure without looking at your project, but maybe something went wrong in the import process. Are you able to share your CCS 3.3 project along with all necessary files? If we can reproduce the issue, it will be a lot easier to track down the source of the error.

If you do not wish to post your project here on the public forum, you can start a private conversation with me and send the project directly to me. To do this, click on my User name and "Add as Friend" to add me as your friend. After that we should be able to start a private conversation with each other.

Glad to hear the errors are resolved. Sounds like the linker command file(.cmd) was not being added to the project and your solution is the correct one for resolving it. Another way of adding the linker command file to the project would be to "add" or "link" the file to project using Project->Add Files to Project or Project->Link Files to Project.