BeagleBone Black Board ID EEPROM contents confusion

Hello all,

Has the Board ID EEPROM contents changed from what is shown in the System Reference Manual?

I just got some new BeagleBone Black boards from Mouser. I put an image of what I have been using on them and when they boot I see this:

U-Boot 2018.01-00002-g9aa111a004 (Jan 20 2018 - 12:45:29 -0600), Build: jenkins-github_Bootloader-Builder-32

CPU : AM335X-GP rev 2.1
I2C: ready
DRAM: 512 MiB
No match for driver ‘omap_hsmmc’
No match for driver ‘omap_hsmmc’
Some drivers were not found
Reset Source: Power-on reset has occurred.
Using default environment

Board: BeagleBone Black
not set. Validating first E-fuse MAC
BeagleBone Black:
Model: SeeedStudio BeagleBone Green:
BeagleBone: cape eeprom: i2c_probe: 0x54:
BeagleBone: cape eeprom: i2c_probe: 0x55:
BeagleBone: cape eeprom: i2c_probe: 0x56:
BeagleBone: cape eeprom: i2c_probe: 0x57:
Net: eth0: MII MODE
cpsw, usb_ether
Press SPACE to abort autoboot in 2 seconds

For some reason U-Boot thinks the model is a SeeedStudio BeagleBone Green.

I then checked the eeprom:

=> run eeprom_dump
Setting bus to 0
0000: aa 55 33 ee 41 33 33 35 42 4e 4c 54 42 42 47 31 .U3.A335BNLTBBG1
0010: 34 30 31 00 02 00 00 00 08 51 0d 00 ff ff ff ff 401…Q…

This doesn’t look like what is shown in the System Reference Manual.

Has the EEPROM format changed?

Before I put this image on the board I tried an older Debian 7.11 image I use (based off Debian Image 2016-06-15). With that image the HDMI was not working, probably because the Green board does not have HDMI. That’s when I put the image above on the board an discovered the Model issue.

Any help with this would be appreciated.


Nope, a few BBB's escaped GHI with a bad eeprom programmed..

GND TP4 (between Ethernet and barrel plug) then run this "one" command as root:

Hi Robert,

I was able to reprogram the boards and they appear to work ok now.

BTW, I’m doing this with an older Debian 7.11 image on the boards. This image has an older kernel so I had to change the ‘dd’ command a bit. I created a script to do it that also allows me to “fix” the serial number part in the EEPROM.

$ cat /etc/dogtag Debian Image 2016-06-15

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.11 (wheezy)
Release: 7.11
Codename: wheezy

$ uname -a
Linux beaglebone 3.8.13-bone80 #1 SMP Wed Jun 15 17:03:55 UTC 2016 armv7l GNU/Linux

$ cat

Fix the board ID EEPROM


echo “EEPROM is currently:”
sudo hd -v -n 64 ${EEPROM}

if [ -n “$1” ]; then
echo -ne “\xaa\x55\x33\xee” > ${EEPROM_FILE}
echo -n “A335BNLT” >> ${EEPROM_FILE}
echo -n $1 >> ${EEPROM_FILE}

echo “Writing:”

sudo dd if=${EEPROM_FILE} of=${EEPROM}

echo “EEPROM is now:”
sudo hd -v -n 64 ${EEPROM}

Do you know if this is a common problem?

We have had a number of boards that we noticed the serial number did not match the bar code on the board. Sometimes the ASCII serial number is just short (i.e. instead of ‘1827BBBG1473’ it will be ‘473’ with non-ASCII data for the last 8 bytes). Other times the entire serial number will be non-ASCII for all 12 bytes. Those boards have booted ok so the Model number part was probably ok but it appears that the manufacture has a issue programming the EEPROMs correctly.

Big pointer to this issue. I used to get BeagleBone Black boards that had ‘BBBK’ in the serial number not they all seem to be ‘BBBG’.