When looking at the dump of a BBBlackRevC eeprom, I can see the header, board,version, and serial. However, as the eeprom on newly received BBBWireless was mis-programmed, some of this information is lacking. The Black’s label on P8 gives the 12-byte serial, but the Wireless gives, what I may naively be assuming, is a 16-byte serial number.
I am curious if the serializing conventions have changed for the Wireless boards, departing from that described in Table 7 of the SRM.
Anyway, if any new owners of a BeagleBone Black Wireless board could post their eeprom contents here, I will be much appreciative. Mine was purchased from Mouser last week right from the get-go of their being available there.
Couple questions - Briefly, what did I just do? Should I see some change in contents of eeprom? Later, where would I find board S/N to ID the board for output to spreadsheet during data collection (i.e. which board is reporting which data)?
From the label I have a BWA5, which explains for me the serializing, in re Rev#.
I also cat eeprom | hexdump -C at the usual location and returns same output as prior to steps taken moments ago. Perhaps I am not getting a good connxn at DGND-TP1? In that folder appeared several new dirs & links…something happened.
When looking at the dump of a BBBlackRevC eeprom, I can see the header, board,version, and serial. However, as the eeprom on newly received BBBWireless was mis-programmed, some of this information is lacking. The Black’s label on P8 gives the 12-byte serial, but the Wireless gives, what I may naively be assuming, is a 16-byte serial number.
The first 4 are the board revision. The last 12 are the serial number, same as before.
Just wanted to say thanks for the helpful advice in this thread. I’ve just got one of the BBB Wireless boards and flashed it to the latest Debian IoT image. I’d spent a while trying to figure out why my custom overlay wasn’t working (took a bit to figure out uboot given all the info on the web is still talking about cape manager), so I decided to distract myself by figuring out why the wifi wasn’t working. Turns out my eeprom was fubar’d too! I got mine from Digi-key so it looks like a fairly common issue.
Anyway problem now solved and wifi working! Turns out my custom cape is also now loading, although I only figured that out by looking at the pin configuration. dmesg doesn’t seem to have any useful information about cape loading, and I haven’t come across an easy way like the old “cat $SLOTS” approach to figure out what overlays are loaded.