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

DP83826E: It's not working properly, we can measure RX signals from PHY but not TX signals coming from microcontroller.

Matheus Ribeiro
Prodigy 10 points
Part Number: DP83826E

Tool/software:

Hello everyone,

We are developing a new ethernet application with NXP i.MX RT1176 and TI DP83826E, but we are facing a connection problem that we are unable to establish ethernet communication.

We are using DP83826 in basic mode and interfacing through RMII.

The link is stablished and we are able to see RX signals from PHY while we are pinging from a computer connected to the board. But we are unable to exchange messages between the board and the computer.

We are also able to read the registers from PHY (as shown in the image below) , but we can't figure out what the problem is.

I would really appreciate it if you could help me with some suggestions.

  • 0
    TI__Mastermind 24988 points

    Hi Matheus,

    PHY register configuration looks correct for RMII slave mode. Is RT1176 providing 50M reference clock into PHY's XI pin?

    The current test case is pinging from PC side, and traffic can be seen when probing "RX" line, but nothing is seen on "TX" line?

    In this case, the RT1176 is likely the root cause. Are you able to view traffic statistics on RT1176 to see if it received valid data?

    In Linux, I believe "ethtool <port>" should output statistics to see if MCU is receiving valid data.

    Thank you,

    Evan

  • 0 in reply to Evan Mayhew
    Prodigy 10 points

    Hi Evan!

    Thank you for your message.

    The problem was actually with the RT1176, specifically the pin clock configuration.

    We followed an application note from MCU that details the pins configuration for ethernet and found the issue in "Software Input On" which should be enabled.