• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 31 subscribers
  • Views 876 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.

TM4C1294NCPDT DHCP

Gergely Bacso
Intellectual 545 points
Other Parts Discussed in Thread: TM4C1294NCPDT

Hi All,

I have TM4C1294NCPDT on a custom board connected to a PC through an Ethernet switch. The PC acts as DHCP server (I use _www.dhcpserver.de/  and it runs on a second NIC).

I've tried both the udpEcho and tcpEcho samples (unmodified versions).

On the first debug launch (I have no idea how I reproduced that), I get the following output:

[CORTEX_M4_0] ss in flash
Starting the TCP Echo example
System provider is set to SysMin. Halt the target to view any SysMin contents in ROV.
Service Status: DHCPC    : Enabled  :          : 000
Service Status: DHCPC    : Enabled  : Running  : 000
Network Added: If-1:192.168.0.3
Service Status: DHCPC    : Enabled  : Running  : 017

But on the upcoming debug sessions, only the following:

[CORTEX_M4_0] ss in flash
Starting the TCP Echo example
System provider is set to SysMin. Halt the target to view any SysMin contents in ROV.
Service Status: DHCPC    : Enabled  :          : 000
Service Status: DHCPC    : Enabled  : Running  : 000

The IP address is renewed at the DHCP server every time, but I could ping the device only during the first run.

Anyone have an idea what to check?
Thank you,
Gergely

  • 0
    TI__Guru 59540 points
    Hi Gregory,

    I am forwarding your question to one of our experts on this topic. They should be able to get back with you soon.
  • 0
    TI__Mastermind 22580 points

    Hello Gregory,

    Based on the error messages, it looks like the TCP/IP stack is getting stuck while trying to acquire the IP address. The fact that you got the IP address once suggests that there could be a timing issue. Wireshark could help in capturing the communication between your custom board and the PC. But before that simpler experiments like below could help in isolating the issue.

    • With the same example (tcpEcho), does your custom board acquire IP address consistently when a router is used as DHCP server instead of the PC?
    • On a TI development board, do you notice the same behavior (not acquiring IP address using the PC as a DHCP server)?

    Hope this helps!

    Sai

  • 0 in reply to Sai Reddy
    Intellectual 545 points

    Hello Sai,

    thank you for your response.

    I tested my device with a real router, and it mostly worked, but not always.
    I also tested the evaluation board and it worked both with DHCP server for Windows and the real router.

    I also did some analysis with WireShark (with the PC as DHCP server):

    With the evaluation board the communication was like:
    DHCP Discover --> DHCP Offer --> DHCP Request --> DHCP ACK

    But with my device it was only repeating:
    DHCP Discover --> DHCP Offer --> DHCP Discover --> DHCP Offer --> ...

    Do you have some idea what the problem could be? Or what to check next?

    Thank you,
    Gergely

    -------------------------------------

    I did some more testing and found that the behavior is absolutely hectic, sometimes there is not even a DHCP discover message.
    What I also noticed is that the MCU is heating on my board (but not on the evaluation board), so I tried the "hello" example, enhanced with an endless loop, and in this case the heating was very moderate.
    So maybe there is some problem with some output pins driven by the udpEcho sample and my board...

  • 0 in reply to Gergely Bacso
    Intellectual 545 points

    Hello Sai,

    the device finally gave up working... So I think it must be hardware fault caused probably by a design mistake.
    But this topic doesn't belong here, so I will start a new thread about it.

    Thank you for your response again, it helped me a lot in narrowing what the problem could be.

    Gergely

  • 0 in reply to Gergely Bacso
    TI__Mastermind 22580 points
    Hello Gergely,

    The fact that your board is getting heated (when the TI dev board is not, with the same binary) and that it does not work consistently with a router points to a board design issue.

    Good analysis! Glad that I was able to help!

    Thanks,
    Sai