Hi Gerald, I saw your comment in response to the question about another revision to the BBB. There is a long standing issue with the BBB reset related to the Ethernet PHY not coming out of reset properly. In order to work around the problem you need to hack the board and drive the Ethernet PHY with a GPIO to ensure the proper reset timing for the PHY.
Is there any plan by CircuitCo to make a revision to address this issue? Its a rather tricky hack to do because you have to drill out one of the via's to do it properly and that takes a special laser to do it. Here is another link to a post on the TI forum that also discusses this issue and I have seen it discussed here as well. I am not aware of any software revision that has addressed this but perhaps there has been a software fix? Phy Address Issue beaglebone U-boot - Sitara Processors Forum - Sitara™ Processors - TI E2E Community <https://e2e.ti.com/support/arm/sitara_arm/f/791/t/366351> Thank you, Steve On Sunday, June 14, 2015 at 6:31:58 PM UTC-6, John Reeve wrote: > > Hi All, > > I have a pair of BBB's that I bought from Canada Robotix. They are both > Rev C boards from Element 14. I've been running debian on a micro SD card > on each of them. The one board had been running a web server for about 2 > months straight, but suddenly lost Ethernet capabilities one day. Both the > Ethernet LED's stay ON solid even when no cable is plugged in. I tried to > rule out software by loading up a couple different OS's but none of them > can connect to my network. I even tried flashing an experimental version of > debian from the beagleboard.org wiki but that did not work either. When I > boot into debian now I notice the ethernet lights blink for a bit then stop > and stay on solid, and I get messages from dmesg like: > > root@beaglebone:/var/lib/cloud9# dmesg | grep phy > [ 0.000000] Booting Linux on physical CPU 0x0 > [ 2.715169] 47401300.usb-phy supply vcc not found, using dummy regulator > [ 2.830812] 47401b00.usb-phy supply vcc not found, using dummy regulator > [ 3.392979] davinci_mdio 4a101000.mdio: detected phy mask fffffffe > [ 3.399823] libphy: 4a101000.mdio: probed > [ 3.399859] davinci_mdio 4a101000.mdio: phy[0]: device > 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 > [ 13.783697] net eth0: phy found : id is : 0x7c0f1 > [ 13.783894] libphy: PHY 4a101000.mdio:01 not found > [ 13.788720] net eth0: phy 4a101000.mdio:01 not found on slave 1 > [ 16.863473] libphy: 4a101000.mdio:00 - Link is Up - 100/Full > [ 46.943180] libphy: 4a101000.mdio:00 - Link is Down > [ 71.703444] libphy: 4a101000.mdio:00 - Link is Up - 100/Full > [ 79.783276] libphy: 4a101000.mdio:00 - Link is Down > [ 111.023649] libphy: 4a101000.mdio:00 - Link is Up - 100/Full > [ 233.103186] libphy: 4a101000.mdio:00 - Link is Down > [ 369.103554] libphy: 4a101000.mdio:00 - Link is Up - 100/Full > [ 385.183238] libphy: 4a101000.mdio:00 - Link is Down > etc...... etc.... > > Does anyone have experience with this type of problem? > Other info: > root@beaglebone:/var/lib/cloud9# uname -a > Linux beaglebone 3.14.43-ti-r67 #1 SMP PREEMPT Thu Jun 4 20:37:18 UTC 2015 > armv7l GNU/Linux > > Everything else seems to work. > > Thanks! > > -John > > . > -- 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/4ad554f4-4cb9-440e-974f-120eb55266a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
