• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 233 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.

AM3358: Cannot config LAN PHY register under U-boot

Weis Wang
Prodigy 10 points
Part Number: AM3358

HI Ti team

I need to config LAN PHY register under U-boot.

But some error occurred  

=>
=> mii device
MII devices: 'ethernet@4a100000'
Current device: 'ethernet@4a100000'
=> mii info
=> mii read 0 0
Error reading from the PHY addr=00 reg=00
=>

It seem can read the mii device 'ethernet@4a100000'

But can not list the mii device detail by mii info command and also cannot read PHY register by mii read command  

Is there any setting missing?

and also fail by mdio command

=>
=> mdio list
ethernet@4a100000:
=> mdio read 0 0
0 is not a known ethernet
Reading from bus ethernet@4a100000
PHY at address 0:
Error 

  • 0
    TI__Mastermind 40080 points

    Hi,

    Which TI SDK version are you using? Is this a custom board or a TI EVM that you are using?  

    While not directly applicable I am able to see these commands complete successfully on an AM62x TI EVM.

    Best Regards,

    Schuyler

  • 0 in reply to Schuyler Patton
    Prodigy 10 points

    Hi Schuyler,
    TI SDK version is 08.02.00 and it is a custom board.

    Are there any settings that need to be confirmed?

  • 0 in reply to Weis Wang
    TI__Mastermind 40080 points

    Hi,

    There are some DTS entries that are needed to support the CPSW. Do you have the AM335x EVM?

    Could please post the lines printed by u-boot on the console prior to booting to the kernel.

    I will assume for the moment that the custom board U-Boot port was started with one of the TI EVMs for the AM355x.  Since the mdio list command is not working one possible differences is that PHY address is not correct. Please verify in the board dts file that the PHY address matches what is set on the board.  

    Another debug step might be to let the board boot into Linux which is assuming that boot sequence is not relying on u-boot to setup boot media. The Linux boot log should indicate if it finds it finds PHYs and their addresses. This again assumes that the Linux DTS file for the board has ethernet enabled.

    Best Regards,

    Schuyler