• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 1916 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: Custom Board does not get IP address from DHCP

Prachi Patil
Expert 1840 points
Part Number: TM4C1294NCPDT

I have a custom board designed by me based on TM4C1294NCPDT. The Ethernet section of the board is based on the Launchpad design. The Ethernet differential output pins are connected to a Pulse Jack with integrated magnetics. The RBIAS pin is grounded through a 4.87Kohm, 1% resistor. An arbitrary MAC address (86-40-EF-3B-C9-A8) is programmed into the MCU using the Flash Programmer per TI documentation as well as the thread https://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/p/476635/1717385#1717385.
However, when I load the  TCP echo example from the TI-RTOS, the MCU does not seem to get the TCP/IP address from the DHCP server in my network. The application shows DHCP messages on the console and waits infinitely for the IP address. Sometimes I get error messages while waiting to get IP address from DHCP like...


The same TCP echo example executes perfectly on a TM4C129 Launchpad. In fact, the complete IoT example I am working on, executes as expected on the Launchpad.

I have traced the custom design schematic end to end for any issues. But I could not get any help from that.
I have used Wireshark to inspect the packets moving out and into the Ethernet port but has not helped in diagnosing the issue.

Any inputs that will help in resolving the issue are appreciated.

Thanks.

  • 0
    TI__Guru**** 182656 points

    Hi,

     I tried your arbitrary MAC address on my launchPad and then use a TivaWare Ethernet example as well as the TI-RTOS echo example and they are working for me. So we can rule out the MAC address.  What doe wireshark show on your side?   I will suggest you to focus on the hardware from your custom board vs the launchpad perspective. Hopefully, other forum contributors will be able chime in and suggest different ideas for you as to what things to check as I'm not an Ethernet expert.

     What transformer did you use on your board? As stated in the user's guide and also in the datasheet, HX1198FNL/HX1188FNL are preferred

  • 0 in reply to Charles Tsai
    Expert 1840 points

    Hello Charles,

    Thanks for your reply.

    Charles Tsai said:
    What doe wireshark show on your side?

    I connected a Launchpad  which has MAC(00-1A-B6-03-27-66) and dumped TCP echo code on it and observed how the DHCP Discover and request packets get captured. I found that when it gets the IP address  and printed in the console then only the  DHCP traffic get captured in wireshark before that it does not show any traffic under  DHCP filter....the DHCP discover and request  packets can be seen in snippet..this is in case of tm4c129 Launchpad.

    But now incase of my custom board it does not get any IP address so it does now show any activity under DHCP filter..not even the DHCP discover packet. 

    Another issue I'm facing with my custom board is that  while waiting to get IP after DHCP enabled messages appear in console, it shows following message in console after 15-20 seconds when I run the code.

    I could not understand why such debug port error occurs and I also want know about  this error CORTEX_M4_0: Error: Timed out while waiting for target powerup/polling a hardware resource. 

    I think before my custom board would send out a discovery broadcast it gets above error.

    Charles Tsai said:
    What transformer did you use on your board?

    I have used : Pulse jack J3011G21DNL(10/100Base-TX surface mount RJ45 single port (1x1) Tab-UP/DOWN with integrated magnetics) which has integrated transformer in it as..

    I hope hardware/Ethernet  expert from TI would help me in diagnosing the above issue.

    Thanks.