Hi Kevin, On Tue, Oct 11, 2016 at 2:18 PM, Kevin Fructuoso <[email protected]> wrote: > Hi Robert, > > I am running some power cycle testing on a rev C board with a debian image > dated to April 23rd, 2014. I am also seeing this error occur across multiple > boards. Do you know if this image should have resolved the issue? > > It is not preferred for us to update to a newer image if we can work around > it. Is there a way we can modify the u-boot and u-boot SPL files to detect > and address this issue? > > Is there a way to tell if this error has occurred without checking the uboot > log? Maybe like a missing device or improper value of a file?
What kernel version? uname -r The issue, the phy's reset line is connected to the am335x's reset line, so there's no way to manually reset the phy when it get's in this odd state.. So the workaround that we use in later kernel versions, we just the mdio/phy address we find, vs the one that's wired up.. Later am335x/am43xx/am57xx development board's have a dedicated gpio pin to reset the phy.. Regards, -- Robert Nelson https://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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYiMGc_z55P3p%3DCXksFFr6qoOvOwpqNge2b8taweqjPQZQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
