I pulled latest iMX Yocto & built image (core-image-full-cmdline).
Now, having used U-boot & Linux sufficiently previously on different boards, SoCs, I found some things changed, one such thing is it seems now (at least for iMX Yocto) U-boot is made to look for extlinux.
My question is : why do I need yet another stage of boot loader , while I could load/boot Linux just fine previously without any sys or ext linux?
Second question is : how would I disable this in my Yocto configuration, to possibly, avoid entirely this stage / do not use extlinux?
And finally, the default generated image from default Yocto config (community bsp , https://github.com/Freescale/fsl-community-bsp-platform) doesn't automatically generate a bootable/working image for me, the trace I get (sorry typing out partially as I don't have copyable outout):
Retreiving file: /boot/extlinux/../zImage
append: root=PARTUUID= rootwait rw console=ttymxc0,115200,...
Retrieving file: /boot/extlinux/../imx6-hummingboard2-emmc ..
Skipping Poky (Yocto Project Ref Distro) for failure
SRIPT FAILED: continuing...
And then it goes to other devs which I dont' need/ have anything on.
So, doenst work out-of-the-box. What's missing? Is append part any suspicious, missing actual PARTUUID..? What's needed to make it work(boot) straight as out of Yocto build.
The boot issue I manually (on target) fixed by 1) linking to one of available devtrees with name U-boot is looking for and; 2) adjusting find uuid command in U-boot to look at mmc 1 rather.