trying to boot a bitbaked image in various ways

trying to boot a bitbaked image in various ways

[Thanassis Silis]

[-- Attachment #1: Type: text/plain, Size: 1627 bytes --]

Hi there, I am trying to boot the image I created in several ways:
1) extracted the tar.bz2 image (with tar xjvf) and did an nfs boot directly from the sabrelite board ! This succeeded.
2)
 copied the .sdcard image to an microSD card and tried to boot locally 
from the microSD. This fails as the uboot version on the board is the 
one that sabrelite shipped with , (2009.08 i think). How do I go about 
updating the uboot (.imx file) that has generated from bitbake process?


3) I started reading on yocto project and tried runqemu but it fails. Here is what I did:
        cd <yocto root>/sources/poky/
        . ./oe-init-build-env
        cd build #done automatically at exit from above script
       
 runqemu ../../../build/tmp/deply/images/uImage-blabla.bin 
../../../build/tmp/deply/images/fsl-image-test-blabla.ext3 ext3
 the qemu start running, 




nass@starland ~/yocto/sources/poky/build $ runqemu 
images/uImage-imx6qsabrelite.bin 
images/fsl-image-test-imx6qsabrelite-20130515000446.rootfs.ext3 ext3

Set MACHINE to [uImage-imx6qsabrelite.bin] based on kernel [images/uImage-imx6qsabrelite.bin]

 
Continuing with the following parameters:

KERNEL: [images/uImage-imx6qsabrelite.bin]

ROOTFS: [images/fsl-image-test-imx6qsabrelite-20130515000446.rootfs.ext3]

FSTYPE: [ext3]



but halts after a while:



There was an error running bitbake to determine TMPDIR

Here is the output from 'bitbake -e':

<huuuuge dump of exported variables and python code following>

 

Am I using the command wrongly?
  Thank you for your help on both matters.


 		 	   		  

[-- Attachment #2: Type: text/html, Size: 2513 bytes --]

Re: trying to boot a bitbaked image in various ways

[Otavio Salvador]

[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]

On Fri, May 17, 2013 at 12:45 PM, Thanassis Silis <djnass_18@hotmail.com>wrote:

> Hi there, I am trying to boot the image I created in several ways:
> 1) extracted the tar.bz2 image (with tar xjvf) and did an nfs boot
> directly from the sabrelite board ! This succeeded.
>

Good.


> 2) copied the .sdcard image to an microSD card and tried to boot locally
> from the microSD. This fails as the uboot version on the board is the one
> that sabrelite shipped with , (2009.08 i think). How do I go about updating
> the uboot (.imx file) that has generated from bitbake process?
>

You should 'dd' the .sdcard file to your microSD card.


> 3) I started reading on yocto project and tried runqemu but it fails. Here
> is what I did:
>         cd <yocto root>/sources/poky/
>         . ./oe-init-build-env
>         cd build #done automatically at exit from above script
>         runqemu ../../../build/tmp/deply/images/uImage-blabla.bin
> ../../../build/tmp/deply/images/fsl-image-test-blabla.ext3 ext3
>
>
> the qemu start running,
>

The image built for SabreLITE won't be compatible with QEMU so it is
expected to fail.

Regards,

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

[-- Attachment #2: Type: text/html, Size: 2385 bytes --]

Re: trying to boot a bitbaked image in various ways

[Thanassis Silis]

[-- Attachment #1: Type: text/plain, Size: 2192 bytes --]

Hi there,
thank you for the reply.
well, considering (2) below, I have already 'dd' the .sdcard image. but the boot fails. I think the 2009.08 uboot image looks for a couple of files in the root folder of the target fs. The questions is though, how does one use this u-boot.imx image that has been bitbaked?

as for (3), I understand this kernel will fail as  the hardware is missing. But then again why does yocto have a command to even extract and run the .tar.bz2 images "for use with nfs or qemu" ? 
how can I run the specific rootfs i bitbaked through the emulator?

Thank you once again for your help!
Nass

Date: Mon, 20 May 2013 15:32:57 -0300
Subject: Re: [meta-freescale] trying to boot a bitbaked image in various ways
From: otavio@ossystems.com.br
To: djnass_18@hotmail.com
CC: meta-freescale@yoctoproject.org




On Fri, May 17, 2013 at 12:45 PM, Thanassis Silis <djnass_18@hotmail.com> wrote:




Hi there, I am trying to boot the image I created in several ways:
1) extracted the tar.bz2 image (with tar xjvf) and did an nfs boot directly from the sabrelite board ! This succeeded.


Good. 2)
 copied the .sdcard image to an microSD card and tried to boot locally 
from the microSD. This fails as the uboot version on the board is the 
one that sabrelite shipped with , (2009.08 i think). How do I go about 
updating the uboot (.imx file) that has generated from bitbake process?

You should 'dd' the .sdcard file to your microSD card. 
3) I started reading on yocto project and tried runqemu but it fails. Here is what I did:
        cd <yocto root>/sources/poky/
        . ./oe-init-build-env
        cd build #done automatically at exit from above script

       
 runqemu ../../../build/tmp/deply/images/uImage-blabla.bin 
../../../build/tmp/deply/images/fsl-image-test-blabla.ext3 ext3
 the qemu start running, 

The image built for SabreLITE won't be compatible with QEMU so it is expected to fail.

Regards, 
-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br

Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

 		 	   		  

[-- Attachment #2: Type: text/html, Size: 3718 bytes --]

Re: trying to boot a bitbaked image in various ways

[Otavio Salvador]

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

On Mon, May 20, 2013 at 7:44 PM, Thanassis Silis <djnass_18@hotmail.com>wrote:

> Hi there,
> thank you for the reply.
> well, considering (2) below, I have already 'dd' the .sdcard image. but
> the boot fails. I think the 2009.08 uboot image looks for a couple of files
> in the root folder of the target fs. The questions is though, how does one
> use this u-boot.imx image that has been bitbaked?
>

Checking by it in Google lead me to
http://boundarydevices.com/i-mx-6dq-u-boot-updates/ so I think you can take
a look there and upgrade it.


> as for (3), I understand this kernel will fail as  the hardware is
> missing. But then again why does yocto have a command to even extract and
> run the .tar.bz2 images "for use with nfs or qemu" ?
> how can I run the specific rootfs i bitbaked through the emulator?
>

It usually is done using the desired qemu machine for building (qemuarm,
for example). You can do other tricks like building kernel only for it and
use another rootfs but I don't know if it is worth the hassle.

Regards,

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

[-- Attachment #2: Type: text/html, Size: 2191 bytes --]

Re: trying to boot a bitbaked image in various ways

[Eric Nelson]

Thanks Otavio,

On 05/20/2013 07:07 PM, Otavio Salvador wrote:
>
> On Mon, May 20, 2013 at 7:44 PM, Thanassis Silis <djnass_18@hotmail.com
> <mailto:djnass_18@hotmail.com>> wrote:
>
>     Hi there,
>     thank you for the reply.
>     well, considering (2) below, I have already 'dd' the .sdcard image.
>     but the boot fails. I think the 2009.08 uboot image looks for a
>     couple of files in the root folder of the target fs. The questions
>     is though, how does one use this u-boot.imx image that has been
>     bitbaked?
>
> Checking by it in Google lead me to
> http://boundarydevices.com/i-mx-6dq-u-boot-updates/ so I think you can
> take a look there and upgrade it.

The Yocto image also has an upgrade script (6x_upgrade) which can be
run from the U-Boot prompt through the 'upgradeu' command:

	U-Boot > run upgradeu

The next question I'd ask is "why are you upgrading"? There are
some valid reasons, especially if you're running something that
pre-dates 2013-02-12, but I wouldn't make a practice of doing it
during each Yocto release.

We expect relatively infrequent updates to the boot loader,
and everything that's shipped in the past few months should
be adequate for most uses.

We do have some updates for boot speed upcoming (which enable
cache), but those haven't been pushed to the meta-freescale
project.

If you're running on a Solo or Dual-Lite processor, you'll also
risk bricking your board. We haven't put any instructions into
Yocto to differentiate between the models, and it probably
doesn't belong in this project.

Regards,


Eric

Re: trying to boot a bitbaked image in various ways

[Otavio Salvador]

[-- Attachment #1: Type: text/plain, Size: 2119 bytes --]

On Mon, May 20, 2013 at 11:18 PM, Eric Nelson <
eric.nelson@boundarydevices.com> wrote:

> Thanks Otavio,
>
>
> On 05/20/2013 07:07 PM, Otavio Salvador wrote:
>
>>
>> On Mon, May 20, 2013 at 7:44 PM, Thanassis Silis <djnass_18@hotmail.com
>> <mailto:djnass_18@hotmail.com>**> wrote:
>>
>>     Hi there,
>>     thank you for the reply.
>>     well, considering (2) below, I have already 'dd' the .sdcard image.
>>     but the boot fails. I think the 2009.08 uboot image looks for a
>>     couple of files in the root folder of the target fs. The questions
>>     is though, how does one use this u-boot.imx image that has been
>>     bitbaked?
>>
>> Checking by it in Google lead me to
>> http://boundarydevices.com/i-**mx-6dq-u-boot-updates/<http://boundarydevices.com/i-mx-6dq-u-boot-updates/>so I think you can
>> take a look there and upgrade it.
>>
>
> The Yocto image also has an upgrade script (6x_upgrade) which can be
> run from the U-Boot prompt through the 'upgradeu' command:
>
>         U-Boot > run upgradeu
>
> The next question I'd ask is "why are you upgrading"? There are
> some valid reasons, especially if you're running something that
> pre-dates 2013-02-12, but I wouldn't make a practice of doing it
> during each Yocto release.
>
> We expect relatively infrequent updates to the boot loader,
> and everything that's shipped in the past few months should
> be adequate for most uses.
>
> We do have some updates for boot speed upcoming (which enable
> cache), but those haven't been pushed to the meta-freescale
> project.
>
> If you're running on a Solo or Dual-Lite processor, you'll also
> risk bricking your board. We haven't put any instructions into
> Yocto to differentiate between the models, and it probably
> doesn't belong in this project.
>

I will try to think how to support this; I'd like to avoid a machine
definition just for it.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750

[-- Attachment #2: Type: text/html, Size: 3091 bytes --]

Re: trying to boot a bitbaked image in various ways

[Thanassis Silis]

[-- Attachment #1: Type: text/plain, Size: 3120 bytes --]

Hello everyone,
excuse my late reply, but I was caught up in something else and couldn't deal with this.

However, it is now clear that at least as far as  sabrelite board is concerned, it is best to avoid using the yocto generated uboot.imx bootloader binary. I have the imx6q with 1GB ram model. 

I also presume that the yocto image does not boot with the uboot-2009.08, because the yocto image creates 2 partitions on the sdcard - a uboot (sd?1) and a rootfs (sd?2) partition, whereas the original sdcard contained everything in the sd?1 (unique) partition.

Looks like an update to a fresher uboot from boundary git is in order, however I will first try to create an sdcard image from the yocto image .tar.bz2 so as to postpone the update a little longer.

Thank you for your help.
Nass

Date: Mon, 20 May 2013 23:25:17 -0300
Subject: Re: [meta-freescale] trying to boot a bitbaked image in various ways
From: otavio@ossystems.com.br
To: eric.nelson@boundarydevices.com
CC: djnass_18@hotmail.com; meta-freescale@yoctoproject.org




On Mon, May 20, 2013 at 11:18 PM, Eric Nelson <eric.nelson@boundarydevices.com> wrote:

Thanks Otavio,



On 05/20/2013 07:07 PM, Otavio Salvador wrote:




On Mon, May 20, 2013 at 7:44 PM, Thanassis Silis <djnass_18@hotmail.com

<mailto:djnass_18@hotmail.com>> wrote:



    Hi there,

    thank you for the reply.

    well, considering (2) below, I have already 'dd' the .sdcard image.

    but the boot fails. I think the 2009.08 uboot image looks for a

    couple of files in the root folder of the target fs. The questions

    is though, how does one use this u-boot.imx image that has been

    bitbaked?



Checking by it in Google lead me to

http://boundarydevices.com/i-mx-6dq-u-boot-updates/ so I think you can

take a look there and upgrade it.




The Yocto image also has an upgrade script (6x_upgrade) which can be

run from the U-Boot prompt through the 'upgradeu' command:



        U-Boot > run upgradeu



The next question I'd ask is "why are you upgrading"? There are

some valid reasons, especially if you're running something that

pre-dates 2013-02-12, but I wouldn't make a practice of doing it

during each Yocto release.



We expect relatively infrequent updates to the boot loader,

and everything that's shipped in the past few months should

be adequate for most uses.



We do have some updates for boot speed upcoming (which enable

cache), but those haven't been pushed to the meta-freescale

project.



If you're running on a Solo or Dual-Lite processor, you'll also

risk bricking your board. We haven't put any instructions into

Yocto to differentiate between the models, and it probably

doesn't belong in this project.

I will try to think how to support this; I'd like to avoid a machine definition just for it. 
-- 
Otavio Salvador                             O.S. Systems

http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


 		 	   		  

[-- Attachment #2: Type: text/html, Size: 4575 bytes --]