Actions
Forum Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 33 subscribers
  • Views 1013 views
  • Users 0 members are here
Related

BeagleBone Black industrial Ethernet Not working

aja_traxens

Hi all,

 

I have a pair of BBB's industrial that I bought from element 14.

They are both RevC (PCB dev B6) boards from Element 14. I've been running debian on each of them.

The one board had been running a web server for about 2

months straight, but suddenly lost Ethernet capabilities one day.

Both the Ethernet LED's stay ON solid even when no cable is plugged in. I tried to

rule out software by loading up a couple different OS's and different kernel, i also tried to reset registry of PHY ETHERNET but none of them

can connect to my network. I even tried flashing an experimental version of debian from the beagleboard.org wiki but that did not work either.

When I boot into debian now I notice the ethernet lights blink for a bit then stop and stay on solid,

 

and I get messages from debug serial :

 

U-Boot SPL 2015.10-00001-g143c9ee (Nov 06 2015 - 15:27:19)

bad magic

U-Boot 2015.10-00001-g143c9ee (Nov 06 2015 - 15:27:19 -0600), Build: jenkins-github_Bootloader-Builder-274

 

       Watchdog enabled

I2C:   ready

DRAM:  512 MiB

Reset Source: Power-on reset has occurred.

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

Card did not respond to voltage select!

Card did not respond to voltage select!

gpio: pin 56 (gpio 56) value is 0

gpio: pin 55 (gpio 55) value is 0

gpio: pin 54 (gpio 54) value is 0

switch to partitions #0, OK

mmc1(part 0) 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 ...

gpio: pin 55 (gpio 55) value is 1

1913 bytes read in 15 ms (124 KiB/s)

Loaded environment from /boot/uEnv.txt

Checking if uname_r is set in /boot/uEnv.txt...

gpio: pin 56 (gpio 56) value is 1

Running uname_boot ...

loading /boot/vmlinuz-3.8.13-bone79 ...

5644336 bytes read in 328 ms (16.4 MiB/s)

loading /boot/dtbs/3.8.13-bone79/am335x-boneblack.dtb ...

26118 bytes read in 23 ms (1.1 MiB/s)

loading /boot/initrd.img-3.8.13-bone79 ...

2862929 bytes read in 175 ms (15.6 MiB/s)

debug: [console=ttyO0,115200n8 capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART4,BB-UART5 root=UUID=a17e1e1e-eae1-40f9-a7e9-6334384abba2 ro rootfstype=ext4 rootwait coherent_pool=1M quiet init=/lib/systemd/systemd cape_universal=enable] ...

debug: [bootz 0x82000000 0x88080000:2baf51 0x88000000] ...

Kernel image @ 0x82000000 [ 0x000000 - 0x562030 ]

## Flattened Device Tree blob at 88000000

   Booting using the fdt blob at 0x88000000

   Loading Ramdisk to 8fd45000, end 8fffff51 ... OK

   Loading Device Tree to 8fd3b000, end 8fd44605 ... OK

 

Starting kernel ...

 

Uncompressing Linux... done, booting the kernel.

[    0.372558] omap2_mbox_probe: platform not supported

[    0.528261] tps65217-bl tps65217-bl: no platform data provided

[    0.592249] bone-capemgr bone_capemgr.9: slot #0: No cape found

[    0.629355] bone-capemgr bone_capemgr.9: slot #1: No cape found

[    0.666463] bone-capemgr bone_capemgr.9: slot #2: No cape found

[    0.703572] bone-capemgr bone_capemgr.9: slot #3: No cape found

[    0.725335] bone-capemgr bone_capemgr.9: slot #5: BB-BONELT-HDMI conflict P8.37 (#10:BB-UART5)

[    0.734343] bone-capemgr bone_capemgr.9: slot #5: Failed verification

[    0.741077] bone-capemgr bone_capemgr.9: loader: failed to load slot-5 BB-BONELT-HDMI:00A0 (prio 1)

[    0.750901] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN conflict P8.37 (#10:BB-UART5)

[    0.759986] bone-capemgr bone_capemgr.9: slot #6: Failed verification

[    0.766714] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 BB-BONELT-HDMIN:00A0 (prio 2)

[    0.781882] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' failed

[    0.844481] pinctrl-single 44e10800.pinmux: pin 44e10854 already requested by 44e10800.pinmux; cannot claim for gpio-leds.8

[    0.856160] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status -22

[    0.863435] pinctrl-single 44e10800.pinmux: could not request pin 21 on device pinctrl-single

Loading, please wait...

systemd-fsck[214]: rootfs : propre, 110769/230144 fichiers, 732331/919296 blocs

 

The IP Address for usb0 is: 192.168.7.2

beaglebone login: [   26.334848] libphy: PHY 4a101000.mdio:01 not found

[   26.339946] net eth0: phy 4a101000.mdio:01 not found on slave 1

[   33.491278] libphy: PHY 4a101000.mdio:01 not found

[   33.496357] net eth0: phy 4a101000.mdio:01 not found on slave 1

[   35.532342] libphy: PHY 4a101000.mdio:01 not found

[   35.537437] net eth0: phy 4a101000.mdio:01 not found on slave 1

[  101.919103] libphy: PHY 4a101000.mdio:01 not found

[  101.924188] net eth0: phy 4a101000.mdio:01 not found on slave 1

 

 

and I get messages from SSHl :

 

root@beaglebone:/# dmesg | grep phy

[    0.000000] Booting Linux on physical CPU 0x0

[    0.932459] davinci_mdio 4a101000.mdio: detected phy mask fffffffe

[    0.939661] libphy: 4a101000.mdio: probed

[    0.939690] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720

[   26.344899] net eth0: phy found : id is : 0x7c0f1

[   26.344936] libphy: PHY 4a101000.mdio:01 not found

[   26.350020] net eth0: phy 4a101000.mdio:01 not found on slave 1

[   29.423297] libphy: 4a101000.mdio:00 - Link is Up - 100/Full

[   33.487617] net eth0: phy found : id is : 0x7c0f1

[   33.487654] libphy: PHY 4a101000.mdio:01 not found

[   33.492734] net eth0: phy 4a101000.mdio:01 not found on slave 1

[   35.526800] net eth0: phy found : id is : 0x7c0f1

[   35.526839] libphy: PHY 4a101000.mdio:01 not found

[   35.531951] net eth0: phy 4a101000.mdio:01 not found on slave 1

[   37.532827] libphy: 4a101000.mdio:00 - Link is Up - 100/Full

[  101.966213] net eth0: phy found : id is : 0x7c0f1

[  101.966243] libphy: PHY 4a101000.mdio:01 not found

[  101.971297] net eth0: phy 4a101000.mdio:01 not found on slave 1

[  103.974133] libphy: 4a101000.mdio:00 - Link is Up - 100/Full

 

 

Does anyone have experience with this type of problem?

Are they any solutions to this issue?

 

Other info:

root@beaglebone:/# uname -a

Linux beaglebone 3.8.13-bone79 #1 SMP Tue Oct 13 20:44:55 UTC 2015 armv7l GNU/Linux

 

Everything else seems to work.

 

Thanks!

 

Ahmed

  • 0

    Hi,

     

    Did you resolve this issue?  We have been using BBB for a while now and experienced a similar issue.  To our knowledge, there is a design flaw with the BBB reset logic that affects the ethernet PHY reset.  The work around we derived involved cutting the reset trace on the PCB to the ethernet PHY and wiring it to a GPIO pin.

     

    I would like to know if anyone else has come across another "non invasive" solution to this problem?

     

    Regards,
    Steve

  • 0

    Hello,

     

    I am also experiencing the same issue with an apparently dead Ethernet port on my Beaglebone Black. I have loaded up new versions of Debian, ifconfig eth0 down, ifconfig eth0 up, dhclient eth0, multiple reset button presses and connmanctl work. Nothing seems to help. I haven't started probing the Beaglebone or replacing the U14 chip.

     

    What is the hardware fix for the ethernet PHY reset?

     

    Any help would be appreciated,

    Oliver

  • 0

    I just ran into this issue with a KnC Miner Jupiter from October 2013, which uses a revision A5C BBB board. Just dusted it off for a Bitcoin-related project and it was working fine for a few hours, then Ethernet cut out in the middle of an SSH session.

     

    Now the ethernet port is behaving exactly as described by the OP:

    • On power-on, if the ethernet cable is connected to the port:
      • When power is applied, 50% of the time, the orange light on the RJ45 port will light up and the green light will flash briefly. Then it turns off for 2 secs, comes back on, and flashes a few more times before going solid.
      • When power is applied, 50% of the time, the lights don't turn on until after the blue user LEDs blink. Once the blue user LEDs blink, the RJ45 lights come on and stay on, steady.

    • On power-on, if no ethernet cable is connected to the port:
      • When power is applied, 50% of the time, the green light on the RJ45 port will partially light up for about 100ms and then turn off.
      • When power is applied, 50% of the time, no lights on the RJ45 port light up at all, even after the blue user LEDs blink.

    • After power-on, if an RJ45 cable is plugged into the port, both the green and orange lights on the RJ45 port turn on and stay on steady.
    • After power-on, if an RJ45 cable is removed from the port, both the green and orange lights on the RJ45 port stay on despite there being no connection.
    • When an RJ45 cable is connected, the device on the other end (PC, switch, etc) reports that the cable is disconnected.
    • The behavior of the device is the same no matter how it receives power -- the KnC Miner has a power supply that delivers power via pins, and I've also removed the board from the miner and tried it with an external 5v wall wart. No change in behavior.

     

    I've even tried turning off link negotiation on the device on the other end of the cable -- setting it to 10 Mbps, 100 Mbps, and half or full-duplex. Still nothing.

     

    It seems as though the PHY is toast.