With the previous Stretch release for the Dragonboard, I took it and created a custom rootfs. I had a series of scripts that would create the custom rootfs. I am updating those scripts to work with the latest Buster release but I am having issues with the board not booting correctly with the custom image.
I am taking the
linaro-buster-developer-dragonboard-410c-528.img.gz image then doing a
simg2img, resize on it before using
Qemu to customize it.
simg2img linaro-*.img martha-linaro-developer-dragonboard-410c.img.raw
resize2fs martha-linaro-developer-dragonboard-410c.img.raw 3G
After completing the customization, I change the image back to a sparse image with:
ext2simg martha-linaro-developer-dragonboard-410c.img.raw martha-linaro-developer-dragonboard-410c.img
The newly created image is not booting correctly on the DragonBoard. Suspiciously the sparse image has shrunk to smaller than the original image.
1.6G Sep 15 20:14 linaro-buster-developer-dragonboard-410c-528.img 3.0G Sep 15 21:00 martha-linaro-developer-dragonboard-410c.img.raw 1.5G Sep 15 21:37 martha-linaro-developer-dragonboard-410c.img
fastboot flash the
*.img.raw to the DragonBoard and that has booted correctly so I am confident that my customization is not the issue.
I have put the logs from the serial console in a gist:
good_boot.log is for martha-linaro-developer-dragonboard-410c.img.raw
bad_boot.log is for martha-linaro-developer-dragonboard-410c.img
I am struggling to see what the issue is as this worked previously. Anyone have any suggestions?