> On Tue, May 19, 2015 at 3:56 PM, Robert Nelson <[email protected] <javascript:>> wrote:
> > > We "assume" phy_mask to be 100% correct. Maybe we should just force > > the dt value of phy_id always into phy_mask? > > I really need to find a board that 'never' boots with 0xfffffffe.. > Back when I had this problem people who received a phymask of fffffffe (like when my board worked) booted successfully, those with fffffffb (like when my board failed) - failed. The reply to my forum post back then said: --- They phymask comes from a hardware register read by the davinci_mdio driver, which gets passed to the linux phy libraries. The problem is that the cpsw driver gets the value from device tree, which is hardcoded to address 0. Usually the values are the same (address 0), but sometimes the phy gets registered to a different address, usually in my case address 2. You calculate the address using the phymask. If you changed the phymask than, you pointing back to address 0, so that wouldn't help you. --- Can the phy move to address 2? Lots of failing boards look for it there, but do any find it there? >> Humm, that is odd, it corrected for [phy mask fffffffb] with [4a101000.mdio:02] Indeed, when my board found fffffffb, it looked for address 2, just like the recent post. But back then it would never find a working phy there... --> Except for one time, when I was testing an RCN modified mmcboot in uenv.txt (the image that booted was on the uSD, so this must show a power-up with the button held): --- U-Boot 2013.10-00249-g15c5cdf (Nov 17 2013 - 16:35:11) ... [ 0.000000] Linux version 3.8.13-bone30 (root@imx6q-sabrelite-1gb-1) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #1 SMP Thu Nov 14 11:19:20 UTC 2013 ... [ 2.467130] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6 [ 2.473591] davinci_mdio 4a101000.mdio: detected phy mask fffffffb [ 2.481082] libphy: 4a101000.mdio: probed [ 2.485347] davinci_mdio 4a101000.mdio: phy[2]: device 4a101000.mdio:02, driver SMSC LAN8710/LAN8720 [ 2.495182] Detected MACID = 90:59:af:4d:71:eb ... [ 6.246797] libphy: PHY 4a101000.mdio:00 not found [ 6.251852] net eth0: phy 4a101000.mdio:00 not found on slave 0 [ 6.258081] libphy: PHY 4a101000.mdio:01 not found [ 6.263119] net eth0: phy 4a101000.mdio:01 not found on slave 1 ... Welcome to Ubuntu 12.04.4 LTS (GNU/Linux 3.8.13-bone30 armv7l) --- All the other logs I archived of that same board with the same boot files show fffffffe or failure, but that one disproves my original theory. Since I installed bone-ubuntu-14.04-console-2014-06-05-2gb.img I've never seen a problem. The same board just works. BTW: Messages that follow the initial detect/probe later in the boot, like [ 6.258081] libphy: PHY 4a101000.mdio:01 not found [ 6.263119] net eth0: phy 4a101000.mdio:01 not found on slave 1 are not really errors - the phy at 00 could have a second slave at the next address, but never does. These messages just repeat over and over to clutter the logs. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
