So, I got both phys to be recognized at boot:
debian@beaglebone:~$ dmesg | grep mdio
[1.323628] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6, bus
freq 100
[1.323645] davinci_mdio 4a101000.mdio: detected phy mask ffcf
[1.360081] libphy: 4a101000.mdio: probed
[
Our schematic had one more line set for the address than we thought and instead
of unsoldering something, we just changed the address in the devicetree, and
then it showed up. For our prototype we were using two dp83867 phys.I think the
second phy came up as a undefined phy device even when it
Ray,
Thanks for the detailed response. Greatly appreciated!
What was wrong with your schematic? And how did you get it to show up in
dmesg? I have triple checked our schematic, the board layout and the
resistors on the board itself. And, yes, the phy on address 4 is detected
and works find.
Also,
$ ifconfig is your best friend if you're not using it. Learn it's other
functions like ifup and ifdown too. You can reset a phy without rebooting.
Right now, it sounds like if you used $ ifconfig you'd get eth0 but no eth1,
. other than USB and loopback (lo).
On Thursday,
Correct me if I'm wrong, but what your saying is only one Ethernet PHY works
and the other one doesn't (based on seeing in your dmesg only 4 came active)?
Did you connect both to an unmanaged switch and still only seen 4?
If so, it sounds like one of two things:1. The one designated as address
We are using a supported phy. The Atheros, just like on the TI EVM. The
only differences between our board and the TI EVM are that we are using an
oscillator to clock both phys instead of a crystal per phy and we have them
wired to be MDIO addresses 4 & 5 instead of 0 & 1.
I appreciate any
I think I can help if interested. I just finished supporting a custom project
that used Bone Debian. The board used two ethernet PHYs. Setting everything up
can be a pain. I can share what I did, but the actual PHYs just happened to
have configuration stuff already installed so adding to a
Also, we found that it was useful for custom board issues to consult both
beagleboard.org and TI-E2E, but for the latter, it was necessary to switch
to the TI-SDK builds as TI didn't support beagleboard/Debian builds at the
time..
FYI,
On Tuesday, January 12, 2021 at 12:43:08 PM UTC-5
I have a 3 year old BB-X15 with a dual PHY at home. I haven't touched
Linux for a couple of years, but am trying to pick it back up on a hobby
basis. We were working on a custom board with a dual PHY, but that effort
was put on hold a couple of year's ago. Message me if you need me to try
I meant dmesg | grep mdio. Here is output.
beaglebone:~$ dmesg | grep mdio
[1.319622] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6, bus
freq 100
[1.319638] davinci_mdio 4a101000.mdio: detected phy mask ffef
[1.338962] libphy: 4a101000.mdio: probed
[1.338993]
10 matches
Mail list logo
