Size and name of FAT partition

The Debian images include a fat partition for sharing drivers and documentation. Is there a way to increase the size of this partition? We would like to use the FAT partition to deploy our applications within the product.

I already tried using GParted to move the root partition and increasing the FAT partition. Booting still worked. However, GParted was not able to resize the FAT partition.

Renaming the partition is possible with GParted. However, for some reason after flashing the image to the eMMC the name of the partition is BEAGLEBONE again. Any idea how to solve that?

Regards
Alexander

The Debian images include a fat partition for sharing drivers and documentation. Is there a way to increase the size of this partition? We would like to use the FAT partition to deploy our applications within the product.

This is simpler at image creation time. Because the EXT partition follows the FAT partition, you need to move that EXT partition after you reduce its size, before you increase the size of the FAT partition.

I already tried using GParted to move the root partition and increasing the FAT partition. Booting still worked. However, GParted was not able to resize the FAT partition.

Please give the steps you took, what you expected and the results.

Renaming the partition is possible with GParted. However, for some reason after flashing the image to the eMMC the name of the partition is BEAGLEBONE again. Any idea how to solve that?

The flashing process redoes the partitions. You’d need to change the flashing image or method.

Hi Alexander,

This will take a few tweaks, give me a day or so

The Debian images include a fat partition for sharing drivers and
documentation. Is there a way to increase the size of this partition? We
would like to use the FAT partition to deploy our applications within the
product.

I already tried using GParted to move the root partition and increasing the
FAT partition. Booting still worked. However, GParted was not able to resize
the FAT partition.

fat is hardcoded to 96Mb when "--beagleboard.org-production" is passed
to setup_sdcard.sh

https://github.com/RobertCNelson/omap-image-builder/blob/master/tools/setup_sdcard.sh#L463

this value is copied (thru /boot/SOC.sh) and used by the flasher script:

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

So we just need an override for boot size...

Renaming the partition is possible with GParted. However, for some reason
after flashing the image to the eMMC the name of the partition is BEAGLEBONE
again. Any idea how to solve that?

For the partition name, well this is hard coded in the flasher:

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

for setup_sdcard.sh we have the label option: "--boot_label" i just
need to pass it thru /boot/SOC.sh and pass it to the flasher..

https://github.com/RobertCNelson/omap-image-builder/blob/master/tools/setup_sdcard.sh#L1297

Regards,

As temporary workaround it should work to modify the values in /opt/scripts/tools/init-eMMC-flasher.sh right?

I just tried changing conf_boot_endmb to 512 in the flasher script. However, it does not change the size of the partition when attached to a computer over USB. Is the value used anywhere else?

Regards
Alexander

Hi Alexander,

I added the "boot/rootfs_label's" yeterday, so you have to do a git
pull on /opt/scripts/ to get those changes.

The flasher reads "/boot/SOC.sh" for partition info:

For a single partition:

boot_fstype=ext4
conf_boot_startmb=1
conf_boot_endmb=
sfdisk_fstype=0x83

For a dual partition: (fat boot, ext4 rootfs)

boot_fstype=fat
conf_boot_startmb=1
conf_boot_endmb=96
sfdisk_fstype=0xE

So for you:

boot_fstype=fat
conf_boot_startmb=1
conf_boot_endmb=512
sfdisk_fstype=0xE

boot_label=BOOTLABEL
rootfs_label=ROOTFSLABEL

I should also add an override for "ext4"... now that i think about it..

Regards,

Thank you very much. It works for me.