Bug 9176 - Default u-boot script is not able boot from eMMC on BeagleBone Black
Summary: Default u-boot script is not able boot from eMMC on BeagleBone Black
Status: RESOLVED WONTFIX
Alias: None
Product: BSPs
Classification: Build System, Metadata & Runtime
Component: bsps-meta-yocto (show other bugs)
Version: unspecified
Hardware: BeagleBone arm
: Medium normal
Target Milestone: 2.2
Assignee: Kevin Hao
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-02-26 14:15 UTC by Jussi Laako
Modified: 2016-11-01 01:14 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
u-boot patch (1.23 KB, patch)
2016-02-26 14:15 UTC, Jussi Laako 		no flags Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jussi Laako 2016-02-26 14:15:33 UTC 
Created attachment 3005 [details]
u-boot patch

Default u-boot boot script on BeagleBone Black maps rootfs using partition UUID, but the function for the UUID lookup doesn't look at eMMC at all. As a result, when booting from eMMC kernel panics since it cannot find the rootfs.

Attached patch fixes the problem and prioritizes boot from microSD over eMMC.
Comment 1 Saul Wold 2016-02-26 22:39:51 UTC 
Since you developed the patch, please submit it to poky@yoctoproject.org for 
inclusion in master
Comment 2 Jussi Laako 2016-02-29 15:28:17 UTC 
Patch posted to the mailinglist.
Comment 4 Saul Wold 2016-05-13 21:42:05 UTC 
Please note, I assigned this back to Jussi since the patch itself (the 0001-...patch file)needs a Upstream-Status: tag added to it.  This is a requirement for Yocto Project patches.

I replied to this and re-assigned it back to Jussi since he is the contributor.
Comment 5 Jussi Laako 2016-05-24 11:39:39 UTC 
I don't have time to deal with this, please do what ever you consider necessary to fix this. My patch is just an example how this could be fixed.
Comment 6 Saul Wold 2016-05-25 14:46:10 UTC 
Kevin, can you please take a look at this patch and updated it as required and submit it to oe-core.  Thx
Comment 7 Kevin Hao 2016-11-01 01:14:51 UTC 
A patch [1] has been made to try to fix this issue in yocto. But it was not picked by the maintainer. I also don't think that this is a bug that we have to fix.

[1] - https://lists.yoctoproject.org/pipermail/poky/2016-June/010563.html