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.

working ethernet phy with AM335x

Hi,

  In the "AM335x General Purpose EVM Board" they're using AR8031-AL1A ethernet phy and ethernet works fine in RGMII mode. Great!

I'm creating my own design and getting a lot of influence from the GPEVM reference design which saves a lot of headaches. Ideally I'd like to use the same PHY-- the AR8031-AL1A but unfortunately it doesn't seem to be freely available. No serious component dealer sells them. So I either need to find some stable source of the AR8031-AL1A PHY or I need to use a different one. That leads to two questions:

1) Does anyone know a good supplier of AR8031-AL1A? Where can we buy these PHYs?

2) Has anyone successfully replaced the "AR8031-AL1A" with anything else? Would you let me know what you used and how? What speed did you achieve and how stable was the connection?

I've read a few posts about people using KSZ9021RL PHY but I don't know how successful they've been and surely there's hidden gotchas that I'd like to know.

Thanks

  • Hi Arturs,

    We too have the similar issue.

    Did you find any option for RGMII interface? Any information would be of great help.

    Even we tried to get the data sheet of AR8031 but no help.

     

    Regards,

    Raja.

  • Hi Raja,
                  Unfortunately this thread is pretty much empty and there's not much info elsewhere in TI's e2e so I guess people just don't know. I've decided to bite the bullet and try hard experimenting with KSZ9021RL which is available in RS components. Also I'll try to get AVNET to give me a quote and minimum order quantity for AR8031 and RTL8211E... they may be able to supply if I'm lucky.

    Either way that's a little bit further in the future as now I'm concentrating on getting the scehmatics and board layout done-- there's lots of other things to think about too.

    Let me know if you get anywhere with PHYs.

    Thanks,
    Arturs

  • Hi,

    I would like to follow up on whether you have had any luck in obtaining the original phy, or using an alternative?

    Regards,

    Jakob

  • All,

    Are you guys particular about GigaBit? If not, you can try LAN8710 which is already used on AM335x BeagleBone. Its also easily available with Digikey.

    http://www.smsc.com/index.php?pid=59&tid=149

    If you are looking for Gigabit also then you can use LAN8810. 

    http://www.smsc.com/index.php?tid=149&pid=340

  • Hi,
           Sorry for replying late but yeah, in the end we used a ready made board "PhyCORE-AM335x" which has LAN8710 connected to RMII1 interface. Works great.

  • Can you describe how you hooked the LAN8710 to the AM335? Some of the pins are giving me trouble trying to figure out where to put them. The RMII1_RXERR, COL, CRS_DV pins are basically the ones that I cannot figure out where to hook to the ARM. 

  • You will have to set up correctly your pinmux settings but in my case:

    RMII1_TXERR goes to ball J15,
    COL to ball H16
    and CRS_DV goes to ball H17

    Please see datasheet 

    datasheet said:
    http://www.ti.com/lit/ds/sprs717d/sprs717d.pdf

     

    for ball labels and functionality and a lot else.

  • Joseph,

    BeagleBone uses LAN8710 in conjunction with AM335x.

    http://beagleboard.org/static/beaglebone/latest/Docs/Hardware/BONE_SCH.pdf

    This schematic should provide you with all you need to implement the SMSC PHY. 

  • DK,

    I started my schematic off the BeagleBone, but I am using a Critical Link SOM. I'm working with them to figure out how to hook up the LAN8710. Looks like some of the pins that I am having issues figuring out where to connect, are used internally on the SOM. 

    Thanks. 

    -Joe

  • Understood. I took a look at the available documentation on their website and (as you mentioned) it looks like they have implemented many of the interface options in FPGA.

    Post back here if you run into issues.