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.
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,
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
You can do it setting the preferred provider for it, as: PREFERRED_PROVIDER_u-boot_imx6qsabresd = "u-boot-imx" in your local.conf.
Created attachment 1645 [details] dora fsl-image-gui boot log with u-boot-imx
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)
p.p.s added the working boot log for comparison.
This has been fixed with the update to U-Boot 2014.01.
(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