If a changed ID is a problem, why does the network work after changing that ID manually in U-Boot and then rebooting, as I described here <https://groups.google.com/d/msg/beagleboard/9mctrG26Mc8/PK6bxAszAkoJ>?
Alex On Friday, February 13, 2015 at 8:45:08 PM UTC+1, RobertCNelson wrote: > > On Fri, Feb 13, 2015 at 11:58 AM, John Zhang > <[email protected] <javascript:>> wrote: > > Hi Alex, > > > > I added this delay 1 second idea on the u-boot version v2015.01 and did > the > > power on / off test on BBB. I did 263 board boot up. Among them 254 > times > > Ethernet interface successfully started up. The other 9 times the u-boot > > just could not detect Phy. Below is the u-boot log comparison between a > > successful boot and a (Ethernet) bad boot - > > > > Successful one: > > > > U-Boot 2015.01-dirty (Feb 13 2015 - 00:46:39) > > > > Watchdog enabled > > I2C: ready > > DRAM: 512 MiB > > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 > > Using default environment > > > > Net: <ethaddr> not set. Validating first E-fuse MAC > > cpsw > > Hit any key to stop autoboot: 0 > > gpio: pin 53 (gpio 53) value is 1 > > switch to partitions #0, OK > > mmc0 is current device > > gpio: pin 54 (gpio 54) value is 1 > > Checking for: /uEnv.txt ... > > Checking for: /boot.scr ... > > Checking for: /boot/boot.scr ... > > Checking for: /boot/uEnv.txt ... > > ...... > > > > > > Bad boot: > > > > U-Boot 2015.01-dirty (Feb 13 2015 - 00:46:39) > > > > Watchdog enabled > > I2C: ready > > DRAM: 512 MiB > > MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1 > > Using default environment > > > > Net: <ethaddr> not set. Validating first E-fuse MAC > > Phy 0 not found > > cpsw > > Hit any key to stop autoboot: 0 > > gpio: pin 53 (gpio 53) value is 1 > > switch to partitions #0, OK > > mmc0 is current device > > gpio: pin 54 (gpio 54) value is 1 > > Checking for: /uEnv.txt ... > > Checking for: /boot.scr ... > > Checking for: /boot/boot.scr ... > > Checking for: /boot/uEnv.txt ... > > ...... > > > > > > > > Note the "Phy 0 not found" line shown in the bad log. > > > > So unfortunately this idea does not work here. The Ethernet failure rate > is > > about the same with or without this 1-second delay added or not. The > hunt > > has to go on... > > It's id changed those 9 times, look at the kernel patch and port it to > the cpsw driver in u-boot: > > > https://github.com/RobertCNelson/linux-dev/blob/master/patches/beaglebone/phy/0003-cpsw-search-for-phy.patch > > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > -- 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.
