summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKevin Hao <kexin.hao@windriver.com>2021-03-23 17:35:29 +0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2021-03-23 22:52:09 +0000
commit5de939f61c3d753fa7170e6e71ed31e1fe328d9a (patch)
tree14ba993cb745c00f66391db4167053eb9d01392b
parente42870e233a85bc0d55395ef110b7445dfe784f8 (diff)
downloadpoky-contrib-5de939f61c3d753fa7170e6e71ed31e1fe328d9a.tar.gz
poky-contrib-5de939f61c3d753fa7170e6e71ed31e1fe328d9a.tar.bz2
poky-contrib-5de939f61c3d753fa7170e6e71ed31e1fe328d9a.zip
meta-yocto-bsp: beaglebone: Set a fixed size for boot partition in WIC image
After the dosfstools has been updated to v4.2 by commit b522f24723e1 ("dosfstools: update 4.1 -> 4.2"), the commit b29eb5be67e9 ("mkfs.fat: Align total number of sectors to be multiple of sectors per track") in v4.2 has caused a regression in beagebone black board. The reason is that the real total sectors of the fat filesystem created by the mkdosfs may not be the same size as what we requested due to align with the sectors per track, this change seem no side effect to linux kernel, but it breaks the beaglebone black boot ROM and make it can't load the MLO. In order to fix this issue, we choose to set a fixed size for the boot partition to make sure that the total sectors always are aligned with the sectors per track. [Yocto #14306] (From meta-yocto rev: 0c679ac53b52e631a7c961872ce58f5cf74b8629) Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--meta-yocto-bsp/wic/beaglebone-yocto.wks2
1 files changed, 1 insertions, 1 deletions
diff --git a/meta-yocto-bsp/wic/beaglebone-yocto.wks b/meta-yocto-bsp/wic/beaglebone-yocto.wks
index 701ae0b3d4..7a28fb23dc 100644
--- a/meta-yocto-bsp/wic/beaglebone-yocto.wks
+++ b/meta-yocto-bsp/wic/beaglebone-yocto.wks
@@ -2,6 +2,6 @@
# long-description: Creates a partitioned SD card image for Beaglebone.
# Boot files are located in the first vfat partition.
-part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 4 --size 16 --sourceparams="loader=u-boot" --use-uuid
+part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 4 --fixed-size 32 --sourceparams="loader=u-boot" --use-uuid
part / --source rootfs --ondisk mmcblk0 --fstype=ext4 --label root --align 4 --use-uuid
bootloader --append="console=ttyS0,115200"