• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 182 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.

AM6548: Using PHY/ping/TFTP in U-Boot

Akm Islam
Prodigy 235 points
Part Number: AM6548
Other Parts Discussed in Thread: DP83869

Tool/software:

Hi,

I am using the AM6548 with a new PHY transceiver. The IDK evaluation design uses the DP83867 PHY, but I am using a design with a DP83869. When I run the MDIO list command in U-Boot, I see that it is a generic PHY, rather than a DP83867 in the IDK U-Boot. 

I can get the IDK to ping to a TFTP server I have set up, but I cannot get the custom design using the DP83869 to ping or TFTP. I believe I would have to rebuild my own version of U-Boot to support drivers for this new PHY.

Is my understanding correct? If so, how can I go about doing this?

Thanks.

  • 0
    TI__Mastermind 40370 points

    Hi,

    The PHYs do have specific drivers but basic connectivity should work. The drivers are needed for what is known as extended mode, or clause 45 registers.

    Could you post what the console looks like as you try to ping? Also please include the mdio list command. Has Ethernet connectivity been proven on this board with Linux?

    Best Regards,

    Schuyler

  • 0 in reply to Schuyler Patton
    Prodigy 235 points 

    => ping 10.10.61.172
link up on port 1, speed 1000, full duplex
Using cpsw_nuss@046000000 device

ARP Retry count exceeded; starting again
ping failed; host 10.10.61.172 is not alive
=>

    This is the U-Boot output when trying to ping. Note that the ethernet PHY works in VxWorks and Linux.

    => mdio list
cpsw_nuss@046000000:
0 - Generic PHY <--> cpsw_nuss@046000000
=>

    This is the mdio list command. It sees the PHY as a generic PHY, rather than a TI PHY.