Sometimes the Ethernet port on a Beagle Bone Black does not work on power up. It takes either a physical reset button press or a power cycle to fix it. This problem affects all BBB’s and until now could only be solved with hardware hacks.
The final official word from TI on this problem:
This sucks. If you are thinking of using a Beagle Bone Black for anything important… then don’t. And don’t bother reading the rest of this article.
If you already are stuck with the Beagle Bone Black and wish that it worked right each and every time you turn it on, then read this article.
Here is a workaround that can guarantee that an unmodified Beagle Bone Black will have a working Ethernet port within a few minutes after power up.
Install this package on your BBB and it will always have a working Ethernet port when it powers up – although it might take a couple of minutes and a few automatic power cycles.
Most interesting thing I learned
Relay contacts weld on closing rather than opening. This makes perfect sense once someone explains it, but was not my intuition before I welded a pile of relays running the tests for this fix.
If you use Beagle Bone Blacks (BBBs), then I bet you can remember a few times when you plugged one in and waited a while for it to connect to the network. Eventually you gave up and power cycled it, chalking it up to maybe a loose network cable or DHCP server. Nope.
There is a design issue in the BBB that causes the Ethernet PHY chip to sometimes power up in an undefined state where it can not make a valid link.
This problem affects every single unit I have ever tested, and I’ve tested at least 100 of them. The chances that the problem will happen varies from board to board, and is also dependent which power connector you use…
|Barel Jack||3.68%||(Only one unit tested)|
|Vcc Header Pins||16.18%||3.89%-42.43%|
So USB is the best, but even on USB it is still possible to see thew problem almost 5% of the time. The header pins are by for the worst case, with one board coming up without Ethernet a shocking 42% of the time! These results match the geist in the forums where people powering via capes seem to be the ones freaking out while USB people try to convince them the problem is not so bad.
Just write a BASH script to PING and REBOOT when necessary?
If only it were so easy.
Doing a software reset on the PHY chip does not get it back to a defined state. There is no way to get the chip back unless you do a hardware reset on it, and on the BBB the hardware reset line of the PHY is tied to the hardware reset line of the ARM chip. Yuck.
What you can do
- If you are thinking of using a BBB for something, don’t. You do not want to live in an ecosystem where a deal-breaker problem like this could happen at all, and not be fixed several years and board revs later.
- If you are making a rev on the BBB, fix the reset circuit. Add a Schmidt trigger to the output of the reset button and/or switch the RESET line of the PHY from the master reset to a GPIO.
- If you have access to the hardware, use a custom cape or wire jumper to connect the header reset pin to a GPIO pin so you can make the board reset itself under software control.
- Use the software only workaround below.
How it works
If we look closely at the schematics, we see that the PHY reset line is connected directly to the reset button.
This is part of the cause of the problem, but also gives us a path to the workaround. This line is also connected to the
nRESETIN_OUT pin of the ARM.
As it’s name hints, this line can be used as both an in and an out, so if we can get this line to go low then we can reset the PHY chip!
It might be as easy as just resetting the ARM… but there is a damn debouncing cap on the reset line (also a cause to the base issue) so we need that reset line to go low for a very long time.
There is a register that sets how long it will go low…
…but the longest we can set it to is not nearly long enough. We need a way to make that reset line stay down for hundreds of milliseconds.
The RESET line does go low if we power down the ARM, but if we power down then we are dead in the water so that does not help since we would need someone to push the power button to turn us back on. Luckily there is a a crazy way to make this chip turn itself on!
Detecting when the PHY needs to be reset
After analyzing the PHY register contents from thousands of boots, , I found one bit that is always
1 when the Ethernet is dead and
0 when the Ethernet came up ok.
Follow the instructions in the readme to install the package. It pulls in the
bbbrtc and the
phyreg utilities that it needs and then installs a little script called
chkphy that runs at startup from
init.d. This script checks the magic bit, and if the Ethernet is dead then it initiates a power cycle using
bbbrtc. It pauses for 30 seconds before running to (1) let Linux finish mucking with the rtc before we try to use it, and (2) give you a chance to stop the process in case something goes wrong so you don’t end up in an infinite restart cycle.
There is also a directory in the repo called
testing that has the scripts I used for testing this problem and fix.
All testing was done using a Raspberry Pi as the master controller. The Pi was connected to this handly device…
..to be able to power cycle the BBBs, which were plugged into a power strip.
For the BBB’s powered via the header, I used a Meanwell RSP-200-5 to generate the 5 VDC.
Raw test data is here…
The 7 columns represent the 7 boards under test, each row represents one power cycle. The number in the cell is the number of 30-second time periods it took for the board to reply to a ping (0=board never replied after 20 tries, so assumed dead).
Look in the
testing directory of the above repo for the scripts that turn the power on and off and look for the pings. There is also a little
c program called
pingb that pings a bunch of addresses periodically.
Why bother checking the magic bit when you could just use
ping test to see if the Ethernet is working?
The bit tells you directly if the Ethernet is dead. Using a
PING test, you might end up power cycling over and over again if, say, the network cable got unplugged or the ping target is not reachable.
Why bother checking the magic bit when you could just use Yona’s test script?
Yona invented the reset-pin-to-GPIO hack that was the least invasive and most effective workaround available. Here is his test…
# Wait until eth0 is either initialized or failed to initialize while ! dmesg | grep 'net eth0: phy found'; do echo 'Waiting for eth0...' sleep 1 if dmesg | egrep -i 'mdio:03 not found'; then echo "NO" >>/var/tmp/test.txt sync exit fi done
This script script is very good and catches almost every time the Ethernet is dead, but it is not perfect. Depending on the board, as many as 2.5% of dead Ethernet powerups will pass this test.
After more than 10,000 test cycles, I have yet to see a case where the magic bit test did not correctly detect a dead Ethernet port.
You are depending on a hard coded value in an undocumented reserved bit! For shame! For Shame!
I 100% agree, but desperate times call for desperate measures. I’ve tested 100+ boards, and this bit works on all of them all the time. You should test any board you plan to use this fix on. Please let me know if you ever find one that breaks it.
BTW, Microchip has responded with a tiny bit of color on this bit…
“I was able to find that Bit 13 is called CO_CLK_FREQ and has to do with the internal clock generation. The factory indicated that this is likely a NASR bit, as this condition where it is 1 is needed initially after a hardware reset until the defaults and configuration straps are programmed, then it would return to 0 either after the initial configuration was done or after a hardware reset with the first write/read to a register.”
So seems like this
1 is indicating that the PHY was unable to complete initial initialization, which is consistent with the port not working.
What is the big deal? Just push the damn reset button if the Ethernet port is not working.
You can’t always reach the reset button if, say, the board is inside a machine or on the side of a building. Considering the BBB is touted for use as a headless industrial computer, these are places they can be found.
What is the big deal? Just power cycle the board if the Ethernet is not working.
You can’t always power cycle, especially if the board is inside some other piece of equipment, or is in a remote location, or is part of a system that you need to always power up into a working state even if unattended.
In my case, the laws of statistics made power cycling completely impractical. I have an installation with 72 BBB’s on the side of a building. Each BBB powers up with no Ethernet on average about 10% of the time. This means each time you turn the assembly on, there is only about a 1/1920 chance that all the Ethernet ports will work. It takes about 2 minutes to power cycle the system, so on average it would take about 32 hours of cycling to get the system to power up with all BBB’s working.
There is a kernel patch that fixes this
There is a kernel patch that fixes a related problem (the PHY comes up with the wrong address, but otherwise functional) caused by the same design issue, but it does not help in the failure mode we are addressing here where the PHY will never link.
What about 4.x kernels?
Check out this comment.