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.

NDK problem?

Other Parts Discussed in Thread: CCSTUDIO, OMAP-L137

I am using the DM6437 EVM and I am new with the NDK.

I installed the NDK version 2.0.0 and I am trying to use the client.pjt example. It works, but sometimes I lose the ethernet communication using ping command and it is restored after some minutes.

In the DM6437 NSP Revision History from PSP 1.10.03 (ReadMe.htm file) I found this information: "Approximately 2 % packet loss is observed with ping packets when used from a Windows Platform. However no drops are seen for flood ping & ping from Linux machines."

Have you ever seen this problem? Is it an NDK issue or an HAL (Hardware Adaptation Layer) issue? Have you already solved it?

Thank you very much for your kind help.

Umberto Amadei

  • I am sorry for the insistence, but are there any news for me about this problem?

    Has anyone similar problem with DM6437 EVM or also with other EVM / DSK?

    Thanks!

     

  • Umberto

    I'm having problems with the client example. It doesn't "build up"

    When i try to do it, i get this error messages, among others:

     

    [conipaddr.c] "C:\CCStudio_v3.3\C6000\cgtools\bin\cl6x" -g -o2 -fr"C:/CCStudio_v3.3/ndk_2_0_0/packages/ti/ndk/example/network/client/evmdm6437/debug" -i"C:/dvsdk_1_01_00_15/ndk_1_92_00_22_eval/packages/ti/ndk/inc" -i"C:/dvsdk_1_01_00_15/ndk_1_92_00_22_eval/packages/ti/ndk/src/hal/evmdm6437/eth_dm6437" -i"C:/dvsdk_1_01_00_15/ndk_1_92_00_22_eval/packages/ti/ndk/example/tools" -i"C:/CCStudio_v3.3/boards/evmdm6437_v2/include" -i"C:/CCStudio_v3.3/ndk_2_0_0/packages/ti/ndk/inc/stack/inc" -d"CHIP_DM643" -d"_INCLUDE_NIMU_CODE" -d"_INCLUDE_IPv6_CODE" -d"_NDK_EXTERN_CONFIG" -mv6400+ --c64p_l1d_workaround=on -@"../../../network/client/evmdm6437/Custom.lkf" "conipaddr.c"
    "conipaddr.c", line 40: error: identifier "NIMU_IF_REQ" is undefined
    "conipaddr.c", line 41: error: identifier "MAX_INTERFACE_NAME_LEN" is undefined
    "conipaddr.c", line 54: error: identifier "NIMU_GET_DEVICE_INDEX" is undefined
    "conipaddr.c", line 69: error: identifier "NIMU_GET_DEVICE_MTU" is undefined
    "conipaddr.c", line 77: error: identifier "NIMU_GET_DEVICE_MAC" is undefined
    "conipaddr.c", line 85: error: identifier "NIMU_GET_DEVICE_NAME" is undefined
    "conipaddr.c", line 130: error: identifier "NIMU_IF_REQ" is undefined
    "conipaddr.c", line 141: error: identifier "NIMU_GET_DEVICE_INDEX" is undefined
    "conipaddr.c", line 184: error: identifier "NIMU_IF_REQ" is undefined
    "conipaddr.c", line 193: error: identifier "NIMU_GET_DEVICE_INDEX" is undefined
    "conipaddr.c", line 209: error: identifier "NIMU_SET_DEVICE_MTU" is undefined
    "conipaddr.c", line 243: error: identifier "NIMU_IF_REQ" is undefined
    "conipaddr.c", line 255: error: identifier "NIMU_GET_DEVICE_INDEX" is undefined
    "conipaddr.c", line 293: error: identifier "NIMU_SET_DEVICE_MAC" is undefined
    "conipaddr.c", line 320: error: identifier "NIMU_IF_REQ" is undefined
    "conipaddr.c", line 332: error: identifier "NIMU_GET_DEVICE_INDEX" is undefined
    "conipaddr.c", line 348: error: identifier "NIMU_IF_REQ" is undefined
    "conipaddr.c", line 351: error: identifier "NIMU_IF_REQ" is undefined
    "conipaddr.c", line 355: error: identifier "NIMU_GET_DEVICE_HANDLE" is undefined
    "conipaddr.c", line 407: error: identifier "NIMU_GET_NUM_NIMU_OBJ" is undefined
    "conipaddr.c", line 423: error: identifier "NIMU_GET_ALL_INDEX" is undefined
    21 errors detected in the compilation of "conipaddr.c".

    >> Compilation failure

    Compile Complete,
      21 Errors, 0 Warnings, 0 Remarks.

     

    I don't know why it happens... this is a clean installation of all TI programs and packages.

     

    Thanks for your help

  • Dear Felipe,

    I think you compile client example attached with NDK 2.0.0, that supports NIMU code, with the NDK library in your "ndk_1_92_00_22_eval" directory, which is an old NDK version.

    Yuo have to put the right NDK install directory for NDK 2.0.0 in your environment variables: in Windows click on Start > Control Panel > Advanced > Environment Variables > New > Name: NDK_INSTALL_DIR , Value: put the path of your NDK 2.0.0 installation > OK

    Then try to compile again. Good luck!

    Umberto

     

  • Dear Umberto,

    I want to transmit a pocket of data from my PC to the EVMOMAP-L137 and receive a pocket of data from the EVM.

    I am using the NDK 2.0.0 on evmomap-l137.

    I am running the example called "client" in "ndk_2_0_0\packages\ti\ndk\example\network\client ".i compile and build it correctly but when i am going to loading the "clien.out " this error message appears:

    "error: file loader

    data verification failed at address 0xc00dd000.

    please verify target memory and memory map."

    can you help me?

    Regards,

    Zahra Mazaheri.

  •  

    Dear Zahra Mazaheri,

    did you compile the project for your processor OMAP-L137? Or it could be a problem with GEL file, did you load the correct GEL file for OMAP-L137?

    Regards,

    Umberto

     

     

  • Umberto,

    what your mean from "did you compile the project for your processor OMAP-L137?" . I could load and run some other test project on my target but could not run load and run the three examples of ndk ( in this directory : D:\ndk\example\network ).

    I have the " evmomapl137_dsp.gel " that was in EVMOMAP-L137s CD.

    Regards,

    Zahra.

  • If you download NDK 2.0.0 from TI Embedded Software Download (http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/ndk/index.html), in "ndk_2_0_0\packages\ti\ndk\example\network\client" directory you have the client project: here you have the "common" sub-directory in which you can find the source code and then you have some other sub-directories in which you can find the project files for some platforms (i.e. dsk6455, evmdm6437, evmomapl137, ...). You have to compile the project in "ndk_2_0_0\packages\ti\ndk\example\network\client\evmomapl137": it should have all memory map ok.

    Regards,

    Umberto