Can I add in what I'm seeing on a A5C board.
When the board boots either with or without an ethernet cable connected I
don't get any lights on the ethernet socket. Whereas my older Beaglebone
(white version) lights the orange ethernet LED almost immediately after
power is applied.
I can plug in different cables and different switches into the ethernet
port and no go. These cables and switches work fine with the BB white.
Appropriate dmesg lines are always the same:
[ 0.762015] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[ 0.762046] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[ 0.763087] libphy: 4a101000.mdio: probed
[ 0.763120] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00,
driver SMSC LAN8710/LAN8720
[ 0.763468] cpsw 4a100000.ethernet: NAPI disabled
[ 5.682733] gadget: using random self ethernet address
[ 5.888585] net eth0: initializing cpsw version 1.12 (0)
[ 5.890892] net eth0: phy found : id is : 0x7c0f1
[ 5.891109] libphy: PHY 4a101000.mdio:01 not found
[ 5.896181] net eth0: phy 4a101000.mdio:01 not found on slave 1
[ 5.960077] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Now here comes the crazy part. The *only* way I've managed to get the
ethernet lights to come on is to plug in an ethernet cable directly from
the BB white to this BB Black (sometimes this doesn't work first time).
Then both the orange and green lights come on and stay on on the Black.
Then I get:
[ 17.528196] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
[ 17.528261] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
If I set an IPv4 address manually I can't ping between the boards tho. Even
tho ifconfig is showing some packets flying around:
eth0 Link encap:Ethernet HWaddr C4:ED:BA:7B:EB:F7
inet addr:192.168.5.199 Bcast:192.168.5.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:41 errors:0 dropped:0 overruns:0 frame:0
TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13493 (13.1 KiB) TX bytes:30970 (30.2 KiB)
Interrupt:56
Craziness does not stop there. About 50% of the time I can then unplug the
ethernet cable from the BB Black and the ethernet lights (on the now empty
port) stay lit. I can then plug a cable in between the BB Black and a
switch and see activity on the green LED (orange LED is still lit). But
still can't actually get any packets out of it. When I do this no new
dmesg's appear.
Is this faulty or some symptom similar to what else is in this post?
I have tried computer USB power, 1A external DC power and a 2.1A USB power
supply. This was observed with the original eMMC software version and I
have since flashed it to 2013-09-04 version with no difference.
regards,
Damon.
--
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/groups/opt_out.
