What's the difference between the BBB-blank-eMMC-flasher and BBB-eMMC-flasher?

Hi, All,

I found the BBB-blank-eMMC-flasher uses bbb-blank-eeprom.conf and
configures the boards as "am335x-boneblack". But the BBB-eMMC-flasher
uses beaglebone.conf and configures the board as "am335x_evm".

I suppose the BBB should select "am335x-boneblack" as board type so
the image should be BBB-blank-eMMC-flasher-xxx.img.xz. But I found BBB
WiKi (http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB_Rev_C.2FBBG_.284GB_eMMC.29)
suggests BBB-eMMC-flasher-xxx.img.xz.

So what is the difference?

Thanks!
dlw

The blank is for oem’s on first bootup eeprom programing…

Regards,

Hi, All,

I found the BBB-blank-eMMC-flasher uses bbb-blank-eeprom.conf and
configures the boards as "am335x-boneblack". But the BBB-eMMC-flasher
uses beaglebone.conf and configures the board as "am335x_evm".

I suppose the BBB should select "am335x-boneblack" as board type so
the image should be BBB-blank-eMMC-flasher-xxx.img.xz. But I found BBB
WiKi
(Beagleboard:BeagleBoneBlack Debian - eLinux.org)
suggests BBB-eMMC-flasher-xxx.img.xz.

So what is the difference?

The blank is for oem's on first bootup eeprom programing..

Ok. So per my understanding, the "am335x_evm" is being used as the
board model for BBB-eMMC-flasher, right? I thought we should use
"am335x-boneblack". Anything I misunderstood in the image-builder
code?

Thanks!

So you want to throw the beaglebone white users under the bus?

am335x_evm supports all…

Regards,