Bug 14306

Summary: [3.3 M3 rc1] beaglebone poky-alt wic image can not bootup
Product: [Build System, Metadata & Runtime] BSPs Reporter: Yi Zhao <yi.zhao>
Component: bsps-meta-yoctoAssignee: Kevin Hao <kexin.hao>
Status: VERIFIED FIXED QA Contact: Yi Zhao <yi.zhao>
Severity: normal    
Priority: High CC: randy.macleod, richard.purdie, sangeeta.jain, twoerner, yi.zhao
Version: 3.3   
Target Milestone: 3.3 M4   
Hardware: BeagleBone   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: Regression (Used to work)
Verified: Documentation change: No (bug/feature does not impact docs)

Description Yi Zhao 2021-03-17 08:53:55 UTC 
Image location: https://autobuilder.yocto.io/pub/releases/yocto-3.3_M3.rc1/machines/beaglebone-yocto-alt/

Git rev: master/9fbbf40317743beacd8ac9d3f602765ed9d9fa6f

Steps:
1. Download core-image-sato-sdk poky-alt wic image: https://autobuilder.yocto.io/pub/releases/yocto-3.3_M3.rc1/machines/beaglebone-yocto-alt/core-image-sato-sdk-beaglebone-yocto.wic

2. dd the wic image to MMC card

3. Inert the MMC and power up the board


The system can not boot up. There is no bootloader (u-boot) message on the screen.

I had checked the sha256sum with the wic image.
I also built a wic image with poky-alt config, it also can not boot up.

The poky (sysvinit) wic image works well. And I tried to deploy the poky-alt rootfs tarball to the board manually. It also worked.
Comment 1 Randy MacLeod 2021-03-18 14:49:23 UTC 
Kevin, will you be able to start looking at this in the next few days? - Randy
Comment 2 Kevin Hao 2021-03-19 04:27:36 UTC 
Yes, I took a look at it, but found nothing wrong there. I need to dig a bit more into it.
Comment 3 Richard Purdie 2021-03-23 12:06:43 UTC 
I think there is a patch on the mailing list for this, thanks Kevin!
Comment 4 Kevin Hao 2021-03-25 05:31:36 UTC 
5de939f61c3d meta-yocto-bsp: beaglebone: Set a fixed size for boot partition in WIC image
Comment 5 Yi Zhao 2021-03-25 05:41:50 UTC 
Verified on 3.3 M3 rc2.
Git rev: master/ea455ca8671d3bc2a1097989bfaabe92f3ca37ab
Comment 6 Trevor Woerner 2021-03-26 17:53:07 UTC 
Thank you!

I stumbled upon a problem a couple days ago with the pocketbeagle, turns out the same fix presented here fixes the issue there as well :-)