how to use and the new oemflasher builds

I’ve read through the posts for the past few weeks, but don’t see this as a topic discussed yet. I downloaded the new oemflasher image I see on

This is what I tried:

unxz --verbose debian-8.6-oemflasher-armhf-2016-10-31.tar.xz

tar -xf debian-8.6-oemflasher-armhf-2016-10-31.tar

cd debian-8.6-oemflasher-armhf-2016-10-31/

sudo ./ --mmc /dev/sde --bbgw-flasher -dtb bbb-blank-eeprom

Unfortunately, this did not produce a microsd image that works on my BBGW. During the installation, the serial console on my BBGW reported this error:

chroot: failed to run command ‘/usr/bin/bb-wl18xx-wlan0’: No such file or directory
Traceback (last called is first):
_copy_rootfs() in /opt/scripts/tools/eMMC/
prepare_drive() in /opt/scripts/tools/eMMC/
main() in /opt/scripts/tools/eMMC/
The command chroot /tmp/rootfs/ /usr/bin/bb-wl18xx-wlan0 exited with exit code 127.

So, the oemflasher takes a "few" more components:

For example, for Seeed to setup their master microSD to flash a large
number bbgw's they'd run:

tar xf debian-8.6-oemflasher-armhf-2016-10-31.tar.xz
cd ./debian-8.6-oemflasher-armhf-2016-10-31

unxz bone-debian-8.6-seeed-gcp-iot-armhf-2016-10-20-4gb.img.xz


sudo ./ --img-8gb master.img \
--dtb beaglebone \
--oem-flasher \
--oem-flasher-script \
--oem-flasher-img bone-debian-8.6-seeed-gcp-iot-armhf-2016-10-20-4gb.img \
--oem-flasher-eeprom bbgw-eeprom.dump \

However for you, just grab:



However for you, just grab:

Perfect. I had misunderstood the purpose of the flasher image -- I thought
it was the new way to distribute the most recent builds. I'll stick to the
.img.xz images going forward.

Thanks again, Robert.