• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 30 subscribers
  • Views 272 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.

TM4C1294KCPDT: Tiva C series

Yuvaraj V
Prodigy 100 points
Part Number: TM4C1294KCPDT

Hi,

    I am using TM4c1294KCPDT micro controller for my new project.

i am developed hardware for Ethernet communication application. Previously i am developed with same circuit its working.

But now its not working, but all other peripheral's are working good.

   I shared my hardware schematic below, Ethernet connection success for 1 sec and disconnect it, attached as video.

 

  • +1
    TI__Guru**** 191736 points

    Hi,

      Can you repeat the same issue on other boards or this is the only board that has this problem?

      Can you try a stock TivaWare Ethernet example? Can you repeat the same problem?

      Can you try a different Ethernet cable? Does it make a difference?

      Can you try a different computer? Does it make a difference?

      I will suggest you first confirm a LaunchPad running a stock TivaWare example is working using a good known Ethernet cable and computer on a proven network. Use this as a baseline for diagnosing your board so you can rule out any issues related to cable, computer and network. 

      Your schematic is not very readable but I think if you follow the TM4C129 system guideline then it should be fine. 

      If you prove that all other boards of the same design are working except this one suspected board then do a ABA swap test to confirm if the issue is MCU or a board level issue. 

    The A-B-A Swap Method is a simple cross check test, which can confirm the observed issue is not systemic.

    • A-B-A Swap Method
      (1) Remove the suspected component (A) from the original failing board.
      (2) Replace the suspected component (A) with a known good component (B) and check if the original board now works properly.
      (3) Mount the suspected component (A) to a known good board and see if the same failure occurs on the good board.

    Step 3 is important because it helps us to exclude any possibility that the issue is caused by a systemic issue or the interaction of multiple slightly bad components on a good board.

  • +1 in reply to Charles Tsai
    Prodigy 100 points

    Thanks for clarify.

    It's a hardware issue.