EEPROM id strings between BBW and BBB?

GoogleGroups
1

more nitpicky pedantry ... i was under the impression that if one
wanted to identify the model of beaglebone, one could read the EEPROM
and, near the beginning, one would find the ID string of "A335BONE"
for the original BBW and "A335BNLT" for the newer BBB, correct?

  so, first, that means that it would *not* be sufficient to simply
read "A335" to claim that the board was specifically a BBB, would it?

  and, second, i chanced across element 14's BBB SRM here:

http://www.farnell.com/datasheets/1818802.pdf

where in table 6 on p. 58, the EEPROM contents list (allegedly for the
*BBB*), the board name in ASCII of "A335BONE", which is for the BBW,
no? so that table seems incorrect.

  or am i just misunderstanding the EEPROM contents?

rday

2

Looks like a direct copy & paste from the BeagleBone White..

This is the "bootstrap" firmware used on all BBB's at CircuitCo during
the board's first bringup..

https://github.com/RobertCNelson/boot-scripts/blob/master/device/bone/bbb-eeprom.dump

Regards,

3

... which means that, for what it's worth, element 14's alleged BBB
SRM is wrong in at least the contents of that table -- a minor point,
perhaps, unless you're using that info to verify the precise board
model (BBB versus BBW) from the EEPROM.

  BTW, robert, the only reason i noticed that was i was reading your
flasher script and in the function check_eeprom() was the check:

  eeprom_header=$(hexdump -e '8/1 "%c"' ${eeprom} -s 5 -n 3)
  if [ "x${eeprom_header}" = "x335" ] ; then
          message="Valid BBB EEPROM header found" ; broadcast

and i vaguely remembered that the matching "335" would only verify a
beaglebone, not necessarily a BBB, even though the very next line
claims to have found a valid "BBB" EEPROM header (although,
admittedly, that flasher script would never be run on a BBW).

  back to reading ...

rday