• Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 1101 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.

DM8148 client example compilation issue.

Touseef
Intellectual 280 points

I am using TI compiler 5.2.6,NDK 2.21.01.38, nsp_dm814x_01_00_00_10,  XDC 3.31.2.38core, Bios 6.42.3.35. I am trying to compile ARM example on DM8148 ev. But having these errors, Can anyone tell me how do I get rid of these?

error: file
"C:/ti/pdk/nsp_dm814x_01_00_00_10/packages/ti/drv/centaurus/lib/debug/ti.drv
.centaurus.aea8f<ethdriver.oea8f>" has a Tag_ABI_VFP_args attribute value of
"1" that is different than one previously seen ("0"); combining incompatible
files
error: file
"C:/ti/pdk/nsp_dm814x_01_00_00_10/packages/ti/drv/centaurus/lib/debug/ti.drv
.centaurus.aea8f<nimu_eth.oea8f>" has a Tag_ABI_VFP_args attribute value of
"1" that is different than one previously seen ("0"); combining incompatible

>> Compilation failure
files
error: file
"C:/ti/pdk/nsp_dm814x_01_00_00_10/packages/ti/drv/centaurus/lib/debug/ti.drv
.centaurus.aea8f<cpsw_miimdio.oea8f>" has a Tag_ABI_VFP_args attribute value
of "1" that is different than one previously seen ("0"); combining
incompatible files
error: file
"C:/ti/pdk/nsp_dm814x_01_00_00_10/packages/ti/drv/centaurus/lib/debug/ti.drv
.centaurus.aea8f<csl_emac.oea8f>" has a Tag_ABI_VFP_args attribute value of
"1" that is different than one previously seen ("0"); combining incompatible
files
error: errors encountered during linking; "client.out" not built
gmake: *** [client.out] Error 1
gmake: Target `all' not remade because of errors.

  • TI__Guru**** 249420 points

    The linker says the object files in the ti.drv.centaurus.aea8f library are not compatible.  To investigate this, please show your build options, exactly as the compiler sees them.  Compare that to how that library is built.  That is encoded in the build attributes.  You can see the build attributes with this command ...

    %prompt> armofd --obj_display=none,battrs ti.drv.centaurus.aea8f

    That will show you the build attributes for every file in the library.  Show the build attributes from just one file.

    At the same time, you probably ought to look through this thread, which appears to be similar.

    Thanks and regards,

    -George