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

EVM dm642 not working with NDK 2.0

vsMax
Prodigy 75 points
Other Parts Discussed in Thread: CCSTUDIO

I'd like to upgrade a DM642 project to NDK 2.0 so I started from my EVM (v3) board and I started from the examples comimg with the NDK.

I tryied the network examples and I had no problem for loading and compiling but it seems the board can't establish a connection:

- in the "cfgdemo" the board gets the IP after the first ping and then stops responding;

- in both "client" and "helloWorld" the board senses the LAN (Link Status: 100Mb/s Full Duplex on PHY1) but doesnt' get IP from DHCP.

I tryied an old example for ndk1.8 and it worked fine, so I suppose there isn't a network or board problem.

Can you help me to solve this? What am I doing wrong?

I have CCS 3.3.82, DSP/BIOS 5.33.04 and CGT 6.1.9.

  • 0
    Prodigy 30 points

    Hello vsMax,

    I have the same problem, do you find a resolution for it?

  • 0 in reply to Linne
    Prodigy 30 points

    So, I found the solution. After searching for new downloads I found that the actual download is different in size. After installing the new version the destination folder is C:\CCStudio_v3.3\ndk_2_0_0 and not C:\CCStudio_v3.3\ndk_2_0_0_0 like before. With this "new" version it works in a few seconds...

    Thanks TI for the obvious versioning! [:S]

     

  • 0 in reply to Linne
    Prodigy 75 points

    Sorry for the late answer, I've been quite busy recently and forgot to check the boards...

    After my post I contacted TI NDK support and detailed my problems: after some more mails the tech told me it was a bug in the Ethernet driver for the DM642 DSP (in the file dm642.c) and suggested how to correct it in the source file (just one line of code).

  • 0 in reply to vsMax
    TI__Mastermind 18130 points

    vsMax,

    Would you mind copying the fix you made here for future reference?

  • 0 in reply to TimHarron
    Prodigy 75 points

    TimHarron said:

    vsMax,

    Would you mind copying the fix you made here for future reference?

    Sure, the fix is the following:

    Change the line 355 in the Ethernet driver file dm642.c

    from: lenght = PBM_getBufferLen(hPkt);

    to: length = PBM_getValidLen(hPkt);

    Btw, I just checked the "new" version of the NDK and I discovered that the fix has already been applied. [;)]

    Hope it helps anyway.

  • 0 in reply to vsMax
    TI__Mastermind 18130 points

    Thanks for getting this out here. It's good to know what causes these issues even if fixed in a newer version. It's common for a development cycle to be locked into specific component versions.