Bug 5551

Summary: 3.10.9 Kernel hanging on fsl-image-gui when using U-Boot mainline (2013.10)
Product: [Build System, Metadata & Runtime] BSPs Reporter: Stuart <stuart.weaver>
Component: bsps-meta-fsl-armAssignee: Otavio Salvador <otavio>
Status: RESOLVED FIXED QA Contact: Alexandru Georgescu <alexandru.c.georgescu>
Severity: major    
Priority: Medium+ CC: alexandru.c.georgescu, sgw
Version: 1.5   
Target Milestone: 1.6   
Hardware: x86   
OS: x86_64   
Whiteboard:
OS type for building Yocto: --- Type of Regression: New (Never tested)
Verified: Documentation change: No (bug/feature does not impact docs)
Attachments:
Description Flags
dora boot log then master-next boot log
none
dora fsl-image-gui boot log with u-boot-imx none

Description Stuart 2013-11-18 12:36:29 UTC
Created attachment 1624 [details]
dora boot log then master-next boot log

Using dora and master-next branch. When building fsl-image-test, it builds and boots up on board fine. However, when building fsl-image-gui, it builds find but fails to fully boot. Provided are the boot logs for both the dora branch and master-next branch.

When using the original 3.0.35 kernel everything works fine, it is only when i use the 3.10.9 kernel that this occurs.
Comment 1 Otavio Salvador 2013-11-20 21:50:09 UTC
Hello,

Is it possible for you to try booting your board using the u-boot-imx version?

I would like to be sure it is possible to reproduce the issue with FSL U-Boot fork.

Regards,
Comment 2 Stuart 2013-11-21 17:33:25 UTC
Hi Otavio, 

I thought that it maybe using the u-boot-imx version already!

from the tmp/deploy/images/imx6qsabresd/ directory these are the files for u-boot:

 u-boot.imx -> u-boot-imx6qsabresd-v2013.10-r0.imx
 u-boot-imx6qsabresd.imx -> u-boot-imx6qsabresd-v2013.10-r0.imx
 u-boot-imx6qsabresd-v2013.10-r0.imx


Is this what is included in the .sdcard image? If not what's the best way of changing to the u-boot-imx? I've tried manually to put uboot, kernel and rootfs on manually but got to a stage of uboot saying "loading" with T's appearing afterwards (wrong loadaddr?). I've also tried changing the 

fsl-community-bsp/sources/meta-fsl-arm/classes/image_types_fsl.bbclass

to use .imx instead of .bin etc...

but after rebuilding it seems to output exactly the same as before. Am I forgetting to do something? Is there any detailed instructions out there to follow? 

Many Thanks,
Stu
Comment 3 Otavio Salvador 2013-11-21 17:35:30 UTC
You can do it setting the preferred provider for it, as:

PREFERRED_PROVIDER_u-boot_imx6qsabresd = "u-boot-imx"

in your local.conf.
Comment 4 Stuart 2013-11-22 11:39:49 UTC
Created attachment 1645 [details]
dora fsl-image-gui boot log with u-boot-imx
Comment 5 Stuart 2013-11-22 11:44:09 UTC
I added the line you suggested to the local.conf and rebuilt with

bitbake -c cleansstate fsl-image-gui
bitbake fsl-image-gui

and then put the .sdcard image on the sdcard and booted with no trouble!

everything seems to be in full working order :)

Many thanks for your help,
Stu

P.S. should I mark the bug as resolved? (fixed my issue but not the underlying problem with the default u-boot)
Comment 6 Stuart 2013-11-22 11:45:08 UTC
p.p.s added the working boot log for comparison.
Comment 7 Otavio Salvador 2014-04-19 00:35:52 UTC
This has been fixed with the update to U-Boot 2014.01.
Comment 8 Alexandru Georgescu 2014-09-22 10:47:31 UTC
(In reply to comment #6)
> p.p.s added the working boot log for comparison.

Hi Stuart, Otavio,

Is it possible that you can verify this bug and change the status to Verified? 
I can have a try but I don't think I have the right hardware in order to verify it...

Thanks,
Alex