• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 1349 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.

_NIMUDeviceTable definition?

Richard Zuber
Prodigy 210 points

Hello,

I am trying to determine the library in which _NIMUDeviceTable resides within the NDK.  My setup is as follows:

Target: C6472

Compiler: C6000 Code Generation Tools 7.2.4

XDC Tools: xdctools_3_20_08_88

BIOS: bios_6_31_04_27

NDK: ndk_2_20_04_26

I am currently linking against to following libraries:

ndk_2_20_04_26/packages/ti/ndk/lib/C64plus/netctrl.lib
ndk_2_20_04_26/packages/ti/ndk/lib/C64plus/nettool.lib
ndk_2_20_04_26/packages/ti/ndk/lib/C64plus/os.lib
ndk_2_20_04_26/packages/ti/ndk/lib/C64plus/stack.lib
ndk_2_20_04_26/packages/ti/ndk/lib/C64plus/all_stk/stk6.lib
ndk_2_20_04_26/packages/ti/ndk/lib/C64plus/hal/hal_eth_stub.lib
ndk_2_20_04_26/packages/ti/ndk/lib/C64plus/hal/hal_ser_stub.lib
ndk_2_20_04_26/packages/ti/ndk/lib/C64plus/hal/hal_timer_bios.lib
ndk_2_20_04_26/packages/ti/ndk/lib/C64plus/hal/hal_userled_stub.lib
ndk_2_20_04_26/packages/ti/ndk/inc

 

The linker error I get is:

cl64P package/cfg/bios6_udp_test_x64P.c ...
lnk64P bios6_udp_test.x64P ...

 undefined        first referenced
  symbol              in file
 ---------        ----------------
 _NIMUDeviceTable C:/P4STC_QNX/tidsp/ti_rtsc/ndk_2_20_04_26/packages/ti/ndk/lib/C64plus/stack.lib<nimu.o64P>

error: unresolved symbols remain
error: errors encountered during linking; "bios6_udp_test.x64P" not built
gmake[1]: *** [bios6_udp_test.x64P] Error 1

I am building directly from the command line, not using Code Composer.

 

Thanks for the help.

  • 0
    TI__Mastermind 45025 points

    Are you using the MCSDK?

    This device table should be defined in the Ethernet driver that comes with the MCUSDK.

    If you are not using that, please let me know and I can help point you to where you can get it.

    Steve

  • 0 in reply to Steven Connell
    Prodigy 210 points

    Thanks Steve, that was the tip off I needed.  The libraries I needed to include were:

    mcsdk_1_00_00_08/packages/ti/platform/nimu/lib/nimu_eth.lib
    mcsdk_1_00_00_08/packages/ti/platform/lib/platform_utils_evm6472.lib
    pdk_c64x_1_00_00_06/packages/ti/drv/emac/lib/emac_drv_c6472.lib

  • 0 in reply to Richard Zuber
    Expert 1425 points

    Hi All:

    I encountered same issue these days. The difference is: I am using MCSDK2.0. I tried to find the file you listed but I cannot find all of them.

    What should I do? 

     

    Thank you very much!

  • 0 in reply to Richard Zuber
    Expert 1425 points

    There is no "package" folder in "mcsdk_2_00_01_12" folder.

    And there is no "emac" folder in "pdk...../drv/" folder.

     

    So what should I do?

  • 0 in reply to Lucifar He
    TI__Mastermind 23525 points

    Lucifar,

    The MCSDK 2.x doesn't support the C64x devices at all.  Are you using C64x or C66x?  If using C64x, you must stick to the MCSDK 1.x release.  If using C66x, the libraries are different and are found here:

     

    C:\Program Files\Texas Instruments\pdk_C6678_1_0_0_xx\packages\ti\platform\evmc6678l\platform_lib\lib\release

    C:\Program Files\Texas Instruments\pdk_C6678_1_0_0_xx\packages\ti\drv\pa\lib

    C:\Program Files\Texas Instruments\pdk_C6678_1_0_0_xx\packages\ti\transport\ndk\nimu\lib\release

     

    If you build and run any of the EMAC examples, it will link to these libs.

     

    Regards,

    Travis

     

  • 0 in reply to tscheck
    Expert 1425 points

    Hi Travis:

    Thank you very much though some one else had already told me that.

    Well, I am still doubt that why the demo and example can't be a compile-to-run style ?

    Those  does take us lot of time. Why can't it be more friendly to user?