Ethernet not working on BBB

Hi, good morning!

I have a BBB where I have had a software working properly until recently (1 or 2 days ago). I don’t know what happend to the BeagleBone Black because it was installed in one of our clients and suddenly the BBB stopped working.

The BBB is plugged to a POE device which powers the BBB and that has been working for some months. Adding to that, the BBB has plugged a USB3.0 hub with some audio usb cards (4). That has been working correctly.

Now, the problem is we cannot start the network interface. I mean, I can’t assign a Network Address. DHCP does not works too. And I don’t know why. I tried with:

systemctl status networking.service

But no luck. The output of the previous command is:

root@beaglebone:/home/debian# systemctl status networking.service
● networking.service - Raise network interfaces
Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
Active: active (exited) since Fri 2023-11-24 10:02:07 UTC; 6s ago
Docs: man:interfaces(5)
Process: 1802 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=0/SUCCESS)
Main PID: 1802 (code=exited, status=0/SUCCESS)
Tasks: 1 (limit: 1026)
Memory: 1.0M
CGroup: /system.slice/networking.service
└─1827 /sbin/dhclient -4 -v -i -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -I -df /var/lib/dhcp/dhclient6.eth0.leases eth0

Nov 24 10:02:04 beaglebone ifup[1802]: — 10.0.1.254 ping statistics —
Nov 24 10:02:04 beaglebone ifup[1802]: 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
Nov 24 10:02:04 beaglebone dhclient[1827]: Trying recorded lease 10.0.2.158
Nov 24 10:02:04 beaglebone ifup[1802]: Trying recorded lease 10.0.2.158
Nov 24 10:02:07 beaglebone ifup[1802]: PING 10.0.1.254 (10.0.1.254) 56(84) bytes of data.
Nov 24 10:02:07 beaglebone ifup[1802]: — 10.0.1.254 ping statistics —
Nov 24 10:02:07 beaglebone ifup[1802]: 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
Nov 24 10:02:07 beaglebone dhclient[1827]: No working leases in persistent database - sleeping.
Nov 24 10:02:07 beaglebone ifup[1802]: No working leases in persistent database - sleeping.
Nov 24 10:02:07 beaglebone systemd[1]: Started Raise network interfaces.
root@beaglebone:/home/debian#

The output of the ip command is:
root@beaglebone:/home/debian# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: can0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen 10
link/can
3: can1: <NOARP,ECHO> mtu 16 qdisc noop state DOWN group default qlen 10
link/can
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 34:84:e4:fe:be:ab brd ff:ff:ff:ff:ff:ff
inet6 fe80::3684:e4ff:fefe:beab/64 scope link
valid_lft forever preferred_lft forever
5: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 34:84:e4:fe:be:ad brd ff:ff:ff:ff:ff:ff
inet 192.168.7.2/24 brd 192.168.7.255 scope global usb0
valid_lft forever preferred_lft forever
inet6 fe80::3684:e4ff:fefe:bead/64 scope link
valid_lft forever preferred_lft forever
6: usb1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 34:84:e4:fe:be:b1 brd ff:ff:ff:ff:ff:ff
inet 192.168.6.2/24 brd 192.168.6.255 scope global usb1
valid_lft forever preferred_lft forever
inet6 fe80::3684:e4ff:fefe:beb1/64 scope link
valid_lft forever preferred_lft forever
root@beaglebone:/home/debian#

As you can see it seems that the Networking service is not working correctly.

Please, can anyone help me with this problem?

NOTE: The version of the software is updated to the last version of debian.

I forget to mention that, even if I set the IP address manually with ip or ifconfig, then, there is no ping to other hosts in the same network.

I attach the output of the dmesg command in a file so you can verify if everything is working correctly.

dmesg.txt (23,2 KB)

Thank you so much in advance for your time.

If you need more info, please, let me know about it.

Can you provide more details on this device.

Also, what image are you using?

The model is: KAT-POE-0525 (Amazon.com)

Thank you so much for your answer!
Best regards!

Not what you want to hear, but it might be your problem. All of the SoC’s require clean and stable power that can hold up to the instantaneous current demands when all the cores light up.

Connect your board to a clean power source and a standard ethernet connection and see what happens.

If networking software was not working properly you would not even see the IP6 address or the IP4 address. I would suspect something physical at this point.

I did that, but it didn’t work anyway.

I think the same, but the problem is I don’t know what happened. We have at least 2600 devices in production with the same hardware and I wouldn’t like this to happen again.

NOTE: I tried to connect the BBB to my pc throught the USB wire but I had the same problem. If I use DHCP, then, the BBB does not get the IP Address. If I use static configuration. I can see the eth0 with the IP Address, but, there is no ping to other hosts.

Thank you so much anyway.

What image are you using?

I’m using debian.

debian@beaglebone:~$ uname -a
Linux beaglebone 4.19.94-ti-r42 #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020 armv7l GNU/Linux
debian@beaglebone:~$ cat /etc/debian_version
10.13

I can’t upgrade because there is no network. I tried to reflash several times but no luck!

Use the RPI imager (raspberry pi imager), scroll down to custom and select your image and burn it onto an SD card. The latest BBB image works fine. https://rcn-ee.com/rootfs/release/2023-10-07/bullseye-minimal-armhf/am335x-debian-11.8-minimal-armhf-2023-10-07-2gb.img.xz

before you upgrade, have you tried swapping that poe unit out? Wonder if it somehow got damaged…

Regards,