• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 294 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

AM625: Optimize reserved memory configuration in dts

AM2634: errors encountered during linking to a static library

zhou nanyi
Prodigy 135 points
Part Number: AM2634

Tool/software:

Hello,

    I'm using compiler version TI Clang v3.2.2.LTS to build my application.

    I am linking to a static library to the project(The library is built in same compiler and chip setting) and I'm getting the below error.

    Description Resource Path Location Type
    #16004-D file "../func/DRV/DRV_LIB/AM263x_DRV_LIB.lib<drv.o>" has a Tag_CPU_arch_profile attribute value of "77" that is different than one previously seen ("82"); combining incompatible files MyProject_AM263x              C/C++ Problem

     Also, i don't see any symbol Tag_CPU_arch_profile in the specified file as shown in the error.

Best regards

  • +1
    TI__Guru**** 249420 points

    Please extract the object file from the library with a command similar to ...

    tiarmar -x AM263x_DRV_LIB.lib drv.o

    Then inspect the build attributes ...

    tiarmreadelf -A drv.o

    Do the same thing with an object file built for the main application.  Compare the output.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 135 points

    Hi George,

         I extracted the information from the lib according to the method you provided and found that the chip core is M4 instead of R5. Then I checked the settings of CCS and  realized following setting is different:

         Properties->Arm compiler->-march/-mcpu/--mfloat-abi/-mfpu/arm/thumb. All settings are empty, When I set them up to be the same as my executable project and recompiled them, everything went smoothly and the program compilation no longer reported errors.

    Thanks.