Hello guys,
So my hardware people found out the problem, I forgot to mention that the
problem only happened when the beagleboard was in our custom cape, so they
run some tests and the problem was in our board there was some delay when
powering the board sometimes and this cause the problem and they were using
the 3.3 pin of the beaglebone as well. I hope that this information help
someone.
On Tuesday, May 19, 2015 at 5:56:44 PM UTC-3, RobertCNelson wrote:
>
> On Tue, May 19, 2015 at 3:48 PM, Fernando Derkoski <bri...@gmail.com
> <javascript:>> wrote:
> > Hi, first thank you for the response, here is the output where the
> network
> > did not work:
> >
> > root@beaglebone:~# dmesg | grep mdio
> > [ 1.040419] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
> > [ 1.040439] davinci_mdio 4a101000.mdio: detected phy mask fffffffb
> > [ 1.047217] libphy: 4a101000.mdio: probed
> > [ 1.047246] davinci_mdio 4a101000.mdio: phy[2]: device
> 4a101000.mdio:02,
> > driver SMSC LAN8710/LAN8720
>
> Humm, that is odd, it corrected for [phy mask fffffffb] with
> [4a101000.mdio:02]
>
> But it should have been phy[4]... [4a101000.mdio:04]
>
> The math conversion in the phy search patch is:
>
> phy_mask = fffffffb
>
> for (i = 0; i < PHY_MAX_ADDR; i++) {
> if ((phy_mask & (1 << i)) == 0) {
> addr = (u32) i;
> break;
> }
> }
>
> 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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
