Closed dgesswein closed 1 year ago
This appears to be a hardware problem with the beaglebone.
This isn't a good solution but gives information. https://wp.josh.com/2018/06/04/a-software-only-solution-to-the-vexing-beagle-bone-black-phy-issue/)
More https://github.com/beagleboard/beaglebone-black/issues/4
A user was having issues with the Ethernet not working for most power on's. It was caused by this issue. After removing the termination resistors it went back to only occasionally failing.
Looks like a new C3 revision of the beaglebone black is coming out which can have a software fix to work around the issue. Issue may eventually be fixed. If the fix is in uboot it won't be too hard to update my image when board and fix are available. Info in beagleboard link above.
Fix is out for newer kernels https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/commit/3e76460430d957b567637051fc53a9c7722a9c3c
Hopefully Robert will push this change into v5.10 so it will get picked up by the changes in #40 (automatically, on make install
).
I handled the PR; this is now in the v5.10.x-ti-unified
branch used by the Debian bullseye image I built and am testing.
Seems to be fixed with new OS and new revision of BeagleBone Black. http://www.pdp8online.com/mfm/revb/software.shtml .
Annoying that they fixed it by adding GPIO to allow additional resets instead of fixing the reset circuit.
I have 4 emulators I purchased in 2016. I admit I have not updated the os in quite a while. Partially because the networking on 3 of them has gotten very unreliable so I have not been able to backup the disk files for some time. A couple of questions. Can I use the usb port to make a network connection from a linux computer? Also, will the older boards work with a new BBG C3 so I can just replace the BBG and update the os to get the network 'fix' to work?
My understanding (correct me if I'm wrong, David):
Sometimes when the board boots the Ethernet lights go out and don't come back on so the Ethernet port is not functional. If you hit the power button to turn off and back on normally it will work the next boot. I was able to reproduce with a board not attached to my emulator so think it is related to OS image running. I have a report that not having the emulator connected to the host system reduces the occurrence. Wasn't able to get DMA working with newer OS image so upgrading image is waiting for more time.