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.

DP83867CS: No output compliance test waveform

Part Number: DP83867CS
Other Parts Discussed in Thread: USB-2-MDIO, , MSP-EXP430F5529LP

Hi team,

My customer is using USB-2-MDIO tool to debug DP83867CS.

He's trying to output compliance test waveform by following the instruction on SNLA23A appendix B.

However, there was no output.

Read and write looks successful. 

Could you please advise me how to debug this?

Regards,

Itoh

  • Hi Itoh-san,

    Upon startup, before programming the device into the test mode, is the customer able to observe the FLP signals?

    Thank you,

    Nikhil

  • Hi Nikhil-san,

    No, customer was not able to observe FLP signals.

    Is the procedure below correct?

    1. Connect SMI bus to MSP-EXP430F5529LP
    2. Turn the power of DP83867CS on and release the reset.
    3. Power ON of MSP-EXP430F5529LP (power ON by USB bus power)
    4. Start the USB2MDIO software, and then COM open.
    5. Find PHY ID
    6. Recognize PHY ID0.
    7. No FLP signal output

    Also can you please let me know why you ask us to check FLP signals?

    Regards,

    Itoh

  • Hi Itoh-san,

    Upon power-up, the PHY should output the FLPs on the MDI pins. This is the signal send to the link partner during auto-negotiation. While probing the MDI pins, if you program the device into the different test modes, you will notice the FLP waveform changes into the test mode waveform. If the device is sending out FLPs upon start-up it is looking for a link partner. Not seeing FLPs is an issue that would lead to not seeing the compliance waveform..

    Can you provide a register dump of the following register:

    0x0

    0x1

    0x2

    0x3

    0x11

    0x6e (extended register)

    Thank you,

    Nikhil

  • Hi Nikhil-san,

    Thank you for explanation. Here's the register dump.

    0x0: 1940

    0x1: 7949

    0x2: 2000

    0x3: A231

    0x11: 0302

    0x6e (extended register): 0800

    0x6F: 0106

    Regards,

    Itoh

  • Hi Nikhil-san,

    The customer found the cause. register 0x0000 was PWDN#.

    He confirmed  compliance test waveform. Let me close this thread.

    Regards,

    Itoh