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: SGMII Not UP with DP83867

Part Number: DP83867E
Other Parts Discussed in Thread: USB-2-MDIO

Hi,

We are using DP83867 PHY with an external Host with MAC and LAN9514 over USB to the processor. The high-level block diagram of connection is shown below.

We don't have MDIO control from HOST MAC side; the plan is to bring SGMII interface just by using hardware straps available on DP83867 chip. The DUT setup when connected to a HOST MAC controller and pinged, doesn't receive any packets and IP address is not getting detected.

We have checked clock which is 25MHz and also tried by changing the PHY_ADD to 1100 previously we had PHY_ADD 0001.

When probed hardware straps, the default straps are proper only when DP83867 PHY is in reset. Once the chip is out of reset, hardware straps values are changed. Please let us know how to overcome this.

  • Hi Kiran,

    Ping is a higher layer function and depends on other factors as well. Can you confirm that the PHY is establishing link? Are there link indication LEDs on link partner or on DP83867 system?

    Datasheet recommends 2 decoupling capacitors on each power pin of the PHY. Are they located on separate section of the schematics?
    Are there coupling capacitors on the SGMII_SIN and SGMII_SIP traces?
    Can you use a external system to connect to the MDIO-MDC traces on your DP83867 system? I see that MDIO-MDC traces are also route to GPIO on your design. We offer a software tool USB-2-MDIO (www.ti.com/.../usb-2-mdio) which run on an MSP430 launchpad. By connecting GPIO pins of MSP430 launchpad to DP83867 you can read/write registers. Register access would be helpful for such debug.

    -Regards,
    Aniruddha
  • I will be closing this thread due to inactivity. Please open a new thread if this topic is still unresolved.

    -Regards,
    Aniruddha
  • Hi Aniruddha,

    Sorry for the delay in response. The delay was because we found some improvement in our testing. We were required to write to the one of register of HOST MAC. probably to enable from HOST side as We are not using the original bootloader for the HOST system. we are getting the original bootloader from our customer soon, once we get it will test with same and let you know the status.

    -Regards,
    Kiran
  • Hi Kiran,

    No worries. While you are working on getting more information from your customer, i will keep this thread 'Closed'. Whenever, you are ready please open a new post with more information and include a link to this thread.

    -Regards,
    Aniruddha