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

USB-2-MDIO: MSP-EXP430G2, DP83822EVM: PHY ID is not available

Jwun
Prodigy 80 points

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

Good afternoon,

I am trying to run USB-2-MDIO using the MSP-EXP430G2 Launchpad and the DP83822EVM board.  I've made the connections from the Launchpad to the EVM as per the USB-2-MDIO User's Guide ( www.ti.com/.../snlu197.pdf ).  On the EVM I have jumpers on J6 in the AVD INT position, the CT INT position, and the VDDIO INT position; the J2 jumper is in the 25MHz position; the J10 jumper is in the PU position; the J11 jumper is in the PU position.  The MDIO pin of J14 of the EVM is connected to the P1.5 pin of the Launchpad.  The MDC pin of J14 of the EVM is connected to the P1.4 pin of the Launchpad.  GND of the EVM, GND of the Launchpad, and the GND1 turret of the EVM are connected to Ground of the power supply.  The power supply is supplying 5V to the V+1 turret of the EVM.  A Cat 5E cable is connected from J12 of the EVM to a link partner.

The AVD_LED of the EVM is lit.  The VDDIO_LED of the EVM is lit.  D4 (the link LED) of the EVM is lit.

The drivers are installed and the software successfully flashed onto the Launchpad.  LED1 and LED2 of the Launchpad are fully illuminated and not blinking.  The jumpers on J3 of the Launchpad are as per USB-2-MDIO User's Guide.

The Launchpad is connected to a computer via the USB cable that came with the Launchpad.  LED0 of the Launchpad is lit.  "MSP430 Application UART" shows up on the computer's device manager.  USB-2-MDIO will open, and the baud rate and UART com port can be selected.  Port can be opened, and Port Status reads "* HW Connected *"



However, when I run File > "Find PHY ID", all 32 PHY IDs show as "NOT available."  Attempts to select a PHY ID and read registers or run scripts result in timeout errors.

I have tried using different cables connected to J12 of the EVM, and I have also tried leaving the other end of these cables disconnected from the link partner; still, all PHY IDs are not available.

Any idea what the problem might be?

Thank you!


  • 0
    TI__Mastermind 18425 points
    Hi Jwun,

    Can you verify connectivity on MDIO and MDC pins between MSP430 and DP83822 using a multimeter continuity tester?
    Can you connect the MSP430 ground pin to pin 22 or pin 24 of J14 connector and try again?

    -Regards,
    Aniruddha
  • 0 in reply to Aniruddha Khadye
    Prodigy 80 points

    Good morning Aniruddha, thank you for your reply.


    Connectivity tests show that
    -the connection between pin MDC of the DP83822 and pin P1.4 of the Launchpad is good
    -the connection between pin MDIO of the DP83822 and pin P1.5 of the Launchpad is good

    I tried GND of J6 on the Launchpad connected to pin 22 of J14 on the DP83822; still, all PHY IDs are not available.
    I also tried GND of J6 on the Launchpad connected to pin 24 of J14 on the DP83822; still, all PHY IDs are not available.

  • 0
    Prodigy 80 points

    I disconnected the Power Supply completely, and instead connected the VCC pin of the Launchpad to the V+1 Turret of the DP83822, and the GND pin of the Launchpad to the GND1 Turret of the DP83822. (There is 3.5V present at the VCC pin.)

    PHY ID 1 is now available (and no other PHY ID is available), and I seem to be able to write to and read from registers. I am going to try this configuration from here on out, but if this is wrong, please let me know.