• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 102 subscribers
  • Views 909 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

OMAP-L138: Several Linker warning and one unresolved symbol in linking code (porting from CCS 5 to CCS 8 and updating RTOS/Libs)

Mike Geppert
Expert 1980 points
Part Number: OMAP-L138
Other Parts Discussed in Thread: SYSBIOS, OMAPL138

Porting my code base from CCS5 to CCS8 (and using the newer libraries) I am getting lots of strange Linker warnings (like 100s) and then one unresolved symbol.

<These are examples of the Linker warnings, there are 100s of them>  Note: It looks like that now all of the stuff that used to be in Utils is now in IPC.  I could not see what in the CFG file forced the generation of the Utils?

------------------------------------------------------------

warning #10252-D: Symbol "EDMA3_RM_Ioctl" (pulled from "C:\ti\edma3_lld_2_12_05_30C\packages\ti\sdo\edma3\rm\lib\omapl138-evm\674\debug\edma3_lld_rm.ae674<edma3resmgr.oe674>") defined in 2 places:

C:\ti\edma3_lld_2_12_05_30C\packages\ti\sdo\edma3\rm\lib\omapl138-evm\674\debug\edma3_lld_rm.ae674<edma3resmgr.oe674>

C:\ti\edma3_lld_2_12_05_30C\packages\ti\sdo\edma3\rm\lib\omapl138-evm\674\debug\edma3_lld_rm.ae674<edma3resmgr.oe674>

...

warning #10252-D: Symbol "MultiProc_getBaseIdOfCluster" (pulled from "C:\Users\bh44962\workspace_v8\DSP_Main\src\ipc\ipc.ae674<Ipc.obj>") defined

in 2 places:

C:\Users\bh44962\workspace_v8\DSP_Main\src\ipc\ipc.ae674<Ipc.obj>

C:\Users\bh44962\workspace_v8\DSP_Main\src\utils\utils.ae674<UTILS.obj>

...

warning #10252-D: Symbol "__c6xabi_get_tp" (pulled from "C:\Users\bh44962\workspace_v8\DSP_Main\src\sysbios\sysbios.ae674<ti_tls_get_tp.obj>") defined in 2 places:

C:\Users\bh44962\workspace_v8\DSP_Main\src\sysbios\sysbios.ae674<ti_tls_get_tp.obj>

C:\ti\ccsv8\tools\compiler\ti-cgt-c6000_8.2.3\lib\rts6740_elf.lib<tls_get_tp.obj>

...

warning #10252-D: Symbol "_c_int00" (pulled from "C:\ti\bios_6_52_00_12\packages\ti\targets\rts6000\lib\boot.ae674<boot.oe674>") defined in 2 places:

C:\ti\bios_6_52_00_12\packages\ti\targets\rts6000\lib\boot.ae674<boot.oe674>

C:\ti\ccsv8\tools\compiler\ti-cgt-c6000_8.2.3\lib\rts6740_elf.lib<boot.obj>

------------------------------------------------------------

This is the one undefined symbol

------------------------------------------------------------

undefined first referenced

symbol in file

--------- ----------------

_mfence C:\Users\bh44962\workspace_v8\DSP_Main\src\ipc\ipc.ae674<Ipc.obj>

error #10234-D: unresolved symbols remain

error #10010: errors encountered during linking; "DSP_Main.out" not built

------------------------------------------------------------

Versions:

CCS 8.0.0.00016

Compliler: TI V8.2.3

XDCtools: 3.50.5.12_core

EDMA3: 2.12.5

IPC: 3.47.1.00

SYS/BIOS: 6.52.0.12

  • 0
    TI__Guru 65405 points
    The team is notified. They will post their feedback directly here.

    BR
    Tsvetolin Shulev
  • 0
    TI__Guru** 114410 points
    Mike,

    Can you please indicate that when you moved from CCSv5 to CCSv8 ...did you also change BIOS, CGT, XDC, IPC and EDMA component version or is this consistent with your CCSv5 project. If you are also migrating all those components then you need to upgrade more gradually than you are currently attempting.

    I would recommend that you port the project to CCSv8 and point to the versions of components that were similar to what you used in CCSv5. Then update the compiler. If you were using COFF binary and older than CGT 8.x compiler on previous project, you may see errors as the CGT 8.x only supports ELF binaries to align with binary format that is widely used in the industry. Once you get past this you can look to upgrade BIOS, XDC and IPC versions and finally update the EDMA version (which should not have chnaged significantly for this device.).

    Also, note from TI support perspective we prefer if users follow the component versions that are being released through Processor SDK RTOS rather than running into issues due to version mismatch of different components so I highly recommend that you download the Processor SDK RTOS baseline for OMAPL138 for your project baseline upgrade and CCSv7.4 (CCSv8 will be supported with release at the end of the quarter)

    Good Luck.

    Regards,
    Rahul
  • 0 in reply to Rahul Prabhu
    Expert 1980 points

    Correct, Both the move to CCS8 and the libraries are updated at the same time.

    Will try CCS7.4...

    Thanks