[meta-freescale] u-boot binary for daisy

[Ilya Smelykh]

Hi Eric,


2014-07-02 6:19 GMT+07:00 Eric Nelson <eric.nelson at boundarydevices.com>:

> Hello Ilya,
>
> On 07/01/2014 01:21 PM, Ilya Smelykh wrote:
> > Hi,
> >
> >  I'm using sabrelite and I've found that there is no u-boot binary since
> > some time in my deploy image directory building it for imx6qsabrelite
> > and nitrogen6x machine.
> >
> >  I've not found any luck to build u-boot-boundary or u-boot-imx recipe
> > for master or daisy branch, u-boot-boundary recipe has branch which
> > doesn't exists in daisy and master,
> > u-boot-imx fails to build because of error described
> > here https://community.freescale.com/thread/319716.
> >
> >  Is it well known bug or I missing something?
> >
>
> You should get a binary in tmp/deploy/nitrogen6x/:
>
> ~/yocto$ ls build-nitrogen6x/tmp/deploy/images/nitrogen6x/u-boot*
> build-nitrogen6x/tmp/deploy/images/nitrogen6x/u-boot.imx
> build-nitrogen6x/tmp/deploy/images/nitrogen6x/u-boot-nitrogen6x.imx
>
> build-nitrogen6x/tmp/deploy/images/nitrogen6x/u-boot-nitrogen6x-v2014.04+gitAUTOINC+6d00ef4bba-r0.imx
>
> Note that 6x_upgrade and u-boot.imx aren't copied to the
> SD card by default, since you need to be careful with this
> if you're running something other than a Quad-Core/1GiB
> configuration (the only SABRE Lite option, and the most
> popular Nitrogen6x option).
>
> Details of various images are here:
>         http://boundarydevices.com/u-boot-updates-for-i-mx6-single-core
>
> Also, unlike other machines, our boards don't require U-Boot
> to be on the SD card.
>
> Regards,
>
>
> Eric
>

Thanks for the reply.
I've checked clean build for nitrogen6x machine but still I can see that
there are no u-boot* files in my tmp/deploy/images/nitrogen6x/.

$ ls -1 tmp/deploy/images/nitrogen6x/
6x_bootscript-nitrogen6x
6x_bootscript-nitrogen6x-v2014.01+gitAUTOINC+aed9475361-r0
6x_upgrade-nitrogen6x
6x_upgrade-nitrogen6x-v2014.01+gitAUTOINC+aed9475361-r0
fsl-image-machine-test-nitrogen6x-20140702043154.rootfs.ext3
fsl-image-machine-test-nitrogen6x-20140702043154.rootfs.manifest
fsl-image-machine-test-nitrogen6x-20140702043154.rootfs.sdcard
fsl-image-machine-test-nitrogen6x-20140702043154.rootfs.tar.bz2
fsl-image-machine-test-nitrogen6x.ext3
fsl-image-machine-test-nitrogen6x.manifest
fsl-image-machine-test-nitrogen6x.sdcard
fsl-image-machine-test-nitrogen6x.tar.bz2
modules--3.10.17-r0-nitrogen6x-20140702032757.tgz
modules-nitrogen6x.tgz
README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt
uImage
uImage--3.10.17-r0-imx6dl-nitrogen6x-20140702032757.dtb
uImage--3.10.17-r0-imx6q-nitrogen6x-20140702032757.dtb
uImage--3.10.17-r0-imx6q-sabrelite-20140702032757.dtb
uImage--3.10.17-r0-nitrogen6x-20140702032757.bin
uImage-imx6dl-nitrogen6x.dtb
uImage-imx6q-nitrogen6x.dtb
uImage-imx6q-sabrelite.dtb
uImage-nitrogen6x.bin

I'm not sure, but could it be related to 3.10.17 kernel? Last time I built
u-boot the 3.0.35 kernel was used.

-- 

Best Regards,
Ilya.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20140702/97687298/attachment-0001.html>