• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 644 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

tcpecho demo example does not work

Tanja Nowitzki
Prodigy 50 points

Hello,

I'm trying to run the tcpEcho_F28M35H52C1_CortexM example code from tirtos_c2000_2_00_01_23 on an "F28M35xx Iso controlCARD" (Release 1.0) including an F28M35H52C1 (rev. 0). I have to add that this is my first experience with ethernet (and posting a question in a forum).

The tcpEcho_readme.txt says that "when the stack
receives an IP address from the DHCP server, the IP address is written to the console."

All I get on the console is:

[Cortex_M3_0] Starting the TCP Echo example
System provider is set to SysMin. Halt the target and use ROV to view output.
Service Status: DHCPC    : Enabled  :          : 000
Service Status: DHCPC    : Enabled  : Running  : 000

After a few minutes, I also get a

Service Status: DHCPC    : Enabled  : Fault    : 002

What does this mean? The DHCP server should be working. At least, the "ipconfig \all" command in the command prompt window of my computer tells me, that a DHCP server is available over the LAN connection. When I take a look at the EMAC section of the ROV, it shows me the correct MAC-address and the rxCount and txSend are incremented.

I tried to debug the code and learned that the tcpHandler task is called only once. If I put a breakpoint inside the while{true} loop of the tcpHandler, the controller is stopped only once after a reset. After pressing the resume button, it just keeps running. Does this mean, that something is wrong with the init functions? Might this have something to do with the revision of the controller (0)?

Thanks in advance for your effort!

Regards,

Tanja

  • 0
    TI__Mastermind 30830 points
    What MAC address is being shown in ROV?
    Did you update it to "a valid and unique address" as mentioned in the readme?

    Alan
  • 0 in reply to Alan DeMars
    TI__Mastermind 30830 points
    Fault 002 indicates that the NDK was unable to obtain an IP address with DHCP.
    This is usually due to a bad physical connection to the network (ie are you mistakenly using (or not using) a crossover ethernet cable?).
    It can also be caused by the access point being configured to only recognize specific MAC addresses.

    To search for other users with similar problems, type "NDK fault 002" in the search window at the top of this page. These posts may give you clues.

    Alan
  • 0 in reply to Alan DeMars
    Prodigy 50 points
    Hi,
    thank you for your quick answer and sorry for my very late reply. As described in the readme.txt, I had entered the MAC-address indicated on the ControlCard and this address was also shown in the ROV. After a little research I can say that I don't use a crossover cable. When I connect the cable to my computer (and disable WLAN and the other end of the cable is connected to same point as when trying to run the example on Concerto), I get an IP-address and a DHCP-Server is indicated by "ipconfig \all" command in the command prompt window. Now I will investigate on your "NDK fault 002" hint. So thank you for that.

    Tanja