• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 34 subscribers
  • Views 204 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.

DP83867IS: Not linking

Adam Daluga
Expert 6385 points
Part Number: DP83867IS

Hello,

We are developing software for a new project that uses 3x DP83867ISRGZ. Things are generally going well, we can link and communicate when connected to a switch or PC NIC. However, we recently tried directly connecting a DP83867 port from each of two different units, and they don’t link. Any ideas? We are connected back the MAC via SGMII and using Linux as the OS.Thanks!

Best,
Adam

  • 0
    TI__Genius 16030 points

    Hi Adam,

    Are all 867s in auto-neg mode? I hope the pairs you want to link-up are not in the unrelated forced modes.

    If you can give the register programming or the strap settings of the 867s you are trying to link-up, I can debug further.

    --

    Regards,

    Vikram 

  • 0 in reply to Vikram Sharma
    TI__Expert 6385 points

    Thanks.  We were able to get it working yesterday – apparently our flavor of linux doesn’t enable auto-mdix by default.

     

    Hope you are safe and healthy wherever you are at.

  • 0 in reply to Adam Daluga
    Prodigy 10 points

    I have been running into nearly the same problem on our custom board.  I can link to a switch or a PC but when I wrap to DP83867ERGZ parts to each-other, they get caught into a A/N infinite loop.  Register 0x11 shows that the parts are constantly switching MDIX (0x0302) vs MDI (0x0002) connections and never finish the link.

    I thought that by default MDIX was supposed to be on for these parts.  Register 0x10 is set to 0x5848 by default on my board which implies automatic crossover.  Register 0x6e indicates 0x0801 which indicates that Auto-mdi/mdix detection is enabled by default.

    The only thing that I can find in the registers that looks weird is that the 0x31 register shows we are in TST_MODE (0x10B0) even though we have RX_CTRL pin strapped to mode 3.

    Merely causing the phy to reset, clears the link issue (set bit 15 of reg 0 to 1).  I can even do this on power up to ONE of the PHYs before any link is tried and then the will link on the first try.