• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 486 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.

DP83848K: How to validate autoneg protocol

Seb O
Intellectual 515 points
Part Number: DP83848K

Dear,

I've a autoneg issue with my product. Sometime the autoneg fails.

I've already check the link pulse characteristic and it fits the Ethernet compliance test.

I would like to "spy" and decode in live the FPL frame transfers between my product and another product and I don't know what tool to use. How does Ethernet IC manufacturer validate their IC are conform to the autoneg protocol? What tools (HW and SW) do they use?

Regards,

Sébastien

  • 0
    TI__Mastermind 18425 points

    Hi Sébastien,

    There are registers in the PHY that store the link ability that is advertised by the link partner. You can read these registers to see what link partner ability is received at DP83848K receiver during the auto-negotiation process. You will need to know what are the settings enabled at link partner and compare it to the ability received at DP83848K to see if there is a mis-match.

    If you want to check the actual signals being sent and received during auto-negotiation process, then you will need a Oscilloscope and differential probe. The probe should be rated for atleast 1GHz operation. You will also need some kind of "sniffer" assembly that allows you to connect the differential probe between DP83848K and link partner without breaking the connection between them. Then you can capture the waveform on the scope and analyze it.

    -Regards

    Aniruddha

  • 0 in reply to Aniruddha Khadye
    Intellectual 515 points

    Hi Aniruddha

    My needs concerns the 2nd case "check the actual signals being sent and received during auto-negotiation process" because the autoneg register of ethernet phy only give the final result. A scope is not suitable because it requires a huge memory and resolution to acquire all the traffic between the ethernet phy and its link partner.

    You don't use third party tool to analyse the autoneg process to validate your chip design, don't you?


    Sébastien

  • 0 in reply to Seb O
    TI__Mastermind 18425 points

    Hi Sebastien,

    For validating certain parts of the autonegotiation process, we have it tested at a 3rd party lab, UNH, to make sure that the autonegotaition process meets the IEEE requirement. DP83848 has been successfully tested at UNH to make sure that autonegotation happens as per spec. 

    -Regards

    Aniruddha