• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 436 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.

DP83867E: Reference code

Ivy Jin
Expert 4525 points
Part Number: DP83867E

Hi team,

My customer uses DP83867E in their new project, and now they have some issues, could you please help give some comments and suggestions?

The master control for this customer is ZYNQ7000, which is configured with the phy chip DP83867E  via RGMII (MDC, MDIO) , also can read registers. However, no data was received when the cable was plugged in. The Link LED do not light up at the beginning, and the link LED react after changing some configurations through the software, but the communication is still unsuccessful.

The customer is currently unsure what registers the needs to be configured. Could we provide the customer with an initialized reference code?

I have suggested the customer to refer the DP83867 Linux Driver code on the TI.com, but the customer said they do not base a Linux system.

Could you please give some direction to solve the problem？ Thank you very much!

Best regards,

Ivy

  • 0
    TI__Genius 17140 points

    Hi Ivy,

    For your first series of questions, I suggest your customer take a look at this troubleshooting guide for the DP83867: DP83867 Troubleshooting Guide (Rev. A)

    The Linux driver is plain text and I suggest they go through the code for an understanding of the structure of the code. Even if they are not using a Linux system, I believe it will prove useful.

    Please let me know if you need more information.

    Kind Regards,

    Joe

    All information in this correspondence and in any related correspondence is provided “as is” and “with all faults”, and is subject to TI’s Important Notice (http://www.ti.com/corp/docs/legal/important-notice.shtml)

  • 0 in reply to Joe Vanacore
    TI__Expert 4525 points

    Hi Joe,

    Thanks a lot for your kindly help! I will push the customer to check this troubleshooting guide. But I still have below questions, could you please help to give comments?

    1. Is the Link light (LED0) controlled by the hardware of the DP83867 or controlled by the software configured?

    2. How long has the DP83867 been powered up to complete the hardware configuration pins check(RX_D0,RX_D1,RX_CTRL)?

    3. Currently, after the customer has passed some debugging, the link LED turns on after plugging in the network cable, but address 0X0011 bit 11 reads out that Auto-Negotiation has not completed, and the bit 5 of address 0X0001 is correct. May I ask what is the cause of this?

    Thanks for your support!

    Regards,

    Ivy

  • 0 in reply to Ivy Jin
    TI__Genius 17140 points

    Hi Ivy,

    Below are my answers to your questions:

    1. Is the Link light (LED0) controlled by the hardware of the DP83867 or controlled by the software configured?

    Software configurable

    2. How long has the DP83867 been powered up to complete the hardware configuration pins check(RX_D0,RX_D1,RX_CTRL)?

    Power Up timing is 200ms and will determine when you can check the configuration pins.

    3. Currently, after the customer has passed some debugging, the link LED turns on after plugging in the network cable, but address 0X0011 bit 11 reads out that Auto-Negotiation has not completed, and the bit 5 of address 0X0001 is correct. May I ask what is the cause of this?

    link is not coming up 

    I suggest you take a look at this troubleshooting guide:https://www.ti.com/lit/pdf/snla246 

    I also advise you to ensure that your configurations are correct and read register 0x0001.

    Kind Regards,

    Joe

    All information in this correspondence and in any related correspondence is provided “as is” and “with all faults”, and is subject to TI’s Important Notice (http://www.ti.com/corp/docs/legal/important-notice.shtml)

  • 0 in reply to Joe Vanacore
    Prodigy 10 points

    hi，we have just done the test according to the  troubleshooting guide documentation,the reslut is:

    the data of address 0x0001 is 0x796d,

    the data of address 0x0004 is 0x0de1,

    the data of address 0x0005 is 0x41e1,

    the data of address 0x000A is 0x0000,

    the data of address 0x0010 is 0x5048,

    the data of address 0x0011 is 0x7f02,

    the status register1(0x000a) is wrong to read 0x0000, others registers is right to our application.please analyze the reasons,thank you!

  • 0 in reply to jack123
    TI__Genius 17140 points

    Hi,

    I will take a look into this and provide you feedback no later than the end of business Tuesday.

    Kind Regards,

    Joe

    All information in this correspondence and in any related correspondence is provided “as is” and “with all faults”, and is subject to TI’s Important Notice (http://www.ti.com/corp/docs/legal/important-notice.shtml)

  • +1 in reply to Joe Vanacore
    TI__Genius 17140 points

    Hi,

    I would like to know if you are able to do successful data transfer. This will help me better understand your issue.

    Kind Regards,

    Joe

    All information in this correspondence and in any related correspondence is provided “as is” and “with all faults”, and is subject to TI’s Important Notice (http://www.ti.com/corp/docs/legal/important-notice.shtml)

  • 0 in reply to Joe Vanacore
    TI__Expert 4525 points

    Hi Joe,

    The question has been resolved.

    Thanks for your support!

    Regards,

    Ivy

  • 0 in reply to Ivy Jin
    TI__Genius 17140 points

    Hi Ivy,

    I am glad to hear it! I will now close this post.

    Kind Regards,

    Joe

    All information in this correspondence and in any related correspondence is provided “as is” and “with all faults”, and is subject to TI’s Important Notice (http://www.ti.com/corp/docs/legal/important-notice.shtml)