On Thursday, February 5, 2015 at 11:16:55 AM UTC-7, [email protected] wrote:
> After I and my colleagues had fruitlessly tried many things, our hardware > developer came up with a working solution: delaying the PHY initialization > performed by the U-Boot we use (v2014.10, git checksum > c43fd23cf619856b0763a64a6a3bcf3663058c49). This ensured that U-Boot code > tried to access LAN8710A only after this chip had come out of reset. So, > inserting "udelay(1000000);" at the beginning of "board_eth_init()" > function in board/ti/am335x/board.c and recompiling U-Boot worked in our > experiments. > > Alex, I've compiled a boot-loader with the delay in the Ethernet initialization and have done some quick testing on it. I haven't seen any issues yet (where I normally would) but have only tested one board so far. To be exact, I've power cycled a BBB 20 times and confirmed that the Ethernet was working after each boot. Normally I would have seen at least a few Ethernet lockups after 20 resets on this board. There may be something to this. Regards, Bill -- 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.
