Allow choosing FAT boot filesystem type

[hlapp]

Rather than hardcoding the codeblock for creating two partitions to be always bypassed, make that the default, and allow optionally choosing with a command line option (--boot_fstype={fat,ext4}).

[RobertCNelson]

Hi @hlapp so the "eewiki" script is hardcoded to ext4, since it's designed to run with this microSD setup:

https://eewiki.net/display/linuxonarm/BeagleBone+Black

Based on your 2 pull requests, you actually want to be using:

https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v3.sh

It reads "/boot/SOC.sh" for all customization's

Regards,

[hlapp]

Hi @hlapp so the "eewiki" script is hardcoded to ext4, since it's designed to run with this microSD setup:

https://eewiki.net/display/linuxonarm/BeagleBone+Black

I see. I've seen the script mentioned on the Google group as the script to use to flash the eMMC from a running microSD. I can try to pull up that post again, if that post (or my understanding of it) was in error.

Either way, the change in this pull request doesn't alter its behavior at all if the script is called as it always was, namely with no arguments. Also, see below.

Based on your 2 pull requests, you actually want to be using:

https://github.com/RobertCNelson/boot-scripts/blob/master/tools/eMMC/init-eMMC-flasher-v3.sh

I did try this first, by uncommenting the corresponding line in /boot/uEnv.txt as recommended in the FAQ and then rebooting:

#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

This resulted in an eMMC flash that aborted half-way and left the eMMC "bricked" (non-bootable). This is the image I had booted on the SD card: bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz (listed under "Older Debian images"). I couldn't find a log of this on the SD card anywhere, so I can't tell where it went wrong. So the "eewiki" script seemed the only choice left (and it would not work either without making the changes in #16).

Furthermore, my understanding is that the init-eMMC-flasher-v3.sh script is meant to be run as init, from boot, only. Is that not true? Even in the absence of the above failure, my original use-case was customizing a stock image while booted from the microSD, and then flashing the result to several BBBs. Is that meant to be served by the init-eMMC-flasher-v3.sh as well?

Having said all that, the flash I currently run is using the the single ext4 rootfs flash, and I understand if you don't want the FAT-type bootfs option to remain (but then why not just delete that part from the script - it's otherwise code that cannot be reached).

UPDATE: corrected the image I was using.

[jadonk]

@hlapp should this pull request be closed without a merge?