Actions
Forum Thread Details
  • Replies 6 replies
  • Subscribers 348 subscribers
  • Views 1376 views
  • Users 0 members are here
Related

Talking to the PHY with MDIO/MDC

andyy

Hey, I have a problem with the Phys of the AES-FMC-NETW1-G module. The Phys are not responding to enquirys at the MDIO/MDC interface.

 

The boards are: AES-ZU-PCIECC-G - AES-ZU3EG-1-SOM-I-G - AES-FMC-NETW1-G.

 

Attached you can see that the Phy 1 is not responding:

image

 

Actually I do not know exactly how I can go one. Normally the Phy should speak to me at address 0x01. Some ideas/hints/help for me? Do I need to enable the MDIO/MDC interface at the board?

Parents

  • Hi Andyy,

     

    You have mentioned you are using the Avnet UltraZed-EG SOM with PCIe Carrier and NETW1 FMC module, but you haven't mentioned what Vivado hw project and, presumably, what PetaLinux BSP you are using.

     

    Though each Ethernet PHY on the NETW1 FMC has its own MDIO interface, these MDIO interfaces also have to be enabled, along with the associated GEM interface, in the ZU+ Processing System (PS) in Vivado.  For example:

    2072.contentimage_192210.png

     

    By default in the BSP that Avnet posts online for the UltraZed-EG + PCIe Carrier only enables one GEM + MDIO interface.  If you need to enable more GEM + MDIO interfaces you will need to open included Vivado project in the BSP and update the PS configuration to match your needs.

     

    The schematics for the NETW1 FMC can be found here:

    http://www.ultrazed.org/product/network-fmc-module

     

    The PetaLinux BSPs for the UltraZed-EG can be found here:

    https://www.element14.com/community/community/designcenter/zedboardcommunity/ultrazed/ultrazed-eg#e14tab2

     

    --Tom

  • in reply to narrucmot

    Hello Tom,

     

    both of the Phys are connected directly to an industrial ethernet real time IP core. Actually there is no GEM involved even the one of the carrier card. There is no Linux. I have run a bare metal driver application at R5.0. The data exchange via real time channel is working. The both Phys are connecting and they transmit/receive data correctly. I need to talk to the management interface for getting the link state and speed...
    Thank you I have the schematics. I'll see the pullup resistor at MDIO line and I was using this for measuring with the probe. I also have the datasheets of the Phy. I can't see anything concerning an init routine.

Reply
  • in reply to narrucmot

    Hello Tom,

     

    both of the Phys are connected directly to an industrial ethernet real time IP core. Actually there is no GEM involved even the one of the carrier card. There is no Linux. I have run a bare metal driver application at R5.0. The data exchange via real time channel is working. The both Phys are connecting and they transmit/receive data correctly. I need to talk to the management interface for getting the link state and speed...
    Thank you I have the schematics. I'll see the pullup resistor at MDIO line and I was using this for measuring with the probe. I also have the datasheets of the Phy. I can't see anything concerning an init routine.

Children