From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dub0-omc3-s20.dub0.hotmail.com (dub0-omc3-s20.dub0.hotmail.com [157.55.2.29]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 8BF40E006CC for ; Fri, 17 May 2013 08:45:14 -0700 (PDT) Received: from DUB116-W130 ([157.55.2.8]) by dub0-omc3-s20.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 17 May 2013 08:45:13 -0700 X-TMN: [8sGAqtsmLYfSRjkbQ/D0cibp0ebyWgzufznRsk+GGyo=] X-Originating-Email: [djnass_18@hotmail.com] Message-ID: From: Thanassis Silis To: "meta-freescale@yoctoproject.org" Date: Fri, 17 May 2013 15:45:12 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 17 May 2013 15:45:13.0287 (UTC) FILETIME=[851AD570:01CE5315] Subject: trying to boot a bitbaked image in various ways X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 May 2013 15:45:14 -0000 Content-Type: multipart/alternative; boundary="_67b19cec-6488-40ef-a405-f9c9467c4726_" --_67b19cec-6488-40ef-a405-f9c9467c4726_ Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable Hi there=2C 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)=0A= copied the .sdcard image to an microSD card and tried to boot locally =0A= from the microSD. This fails as the uboot version on the board is the =0A= one that sabrelite shipped with =2C (2009.08 i think). How do I go about = =0A= 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 /sources/poky/ . ./oe-init-build-env cd build #done automatically at exit from above script =0A= runqemu ../../../build/tmp/deply/images/uImage-blabla.bin =0A= ../../../build/tmp/deply/images/fsl-image-test-blabla.ext3 ext3 the qemu start running=2C=20 =0A= nass@starland ~/yocto/sources/poky/build $ runqemu =0A= images/uImage-imx6qsabrelite.bin =0A= images/fsl-image-test-imx6qsabrelite-20130515000446.rootfs.ext3 ext3 =0A= Set MACHINE to [uImage-imx6qsabrelite.bin] based on kernel [images/uImage-i= mx6qsabrelite.bin] =0A= =0A= Continuing with the following parameters: =0A= KERNEL: [images/uImage-imx6qsabrelite.bin] =0A= ROOTFS: [images/fsl-image-test-imx6qsabrelite-20130515000446.rootfs.ext3] =0A= FSTYPE: [ext3] =0A= but halts after a while: =0A= There was an error running bitbake to determine TMPDIR =0A= Here is the output from 'bitbake -e': =0A= =0A= =20 Am I using the command wrongly? Thank you for your help on both matters. = --_67b19cec-6488-40ef-a405-f9c9467c4726_ Content-Type: text/html; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable
Hi there=2C 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 direct= ly from the sabrelite board ! This succeeded.
2)=0A= copied the .sdcard image to an microSD card and tried to boot locally =0A= from the microSD. This fails as the uboot version on the board is the =0A= one that sabrelite shipped with =2C (2009.08 i think). How do I go about = =0A= updating the uboot (.imx file) that has generated from bitbake process?
=

3) I started reading on yocto project and tried runqemu but it fail= s. Here is what I did:
 =3B =3B =3B =3B =3B =3B&= nbsp=3B cd <=3Byocto root>=3B/sources/poky/
 =3B =3B =3B=  =3B =3B =3B =3B . ./oe-init-build-env
 =3B =3B&= nbsp=3B =3B =3B =3B =3B cd build #done automatically at exi= t from above script
 =3B =3B =3B =3B =3B =3B&nbs= p=3B=0A= runqemu ../../../build/tmp/deply/images/uImage-blabla.bin =0A= ../../../build/tmp/deply/images/fsl-image-test-blabla.ext3 ext3

 =3B

the qemu= start running=2C



=0A= nass@starland ~/yocto/sources/poky/build $ runqemu =0A= images/uImage-imx6qsabrelite.bin =0A= images/fsl-image-test-imx6qsabrelite-20130515000446.rootfs.ext3 ext3
=0A= Set MACHINE to [uImage-imx6qsabrelite.bin] based on kernel [images/uImage-i= mx6qsabrelite.bin]
=0A=

 =3B

= =0A= Continuing with the following parameters:
=0A= KERNEL: [images/uImage-imx6qsabrelite.bin]
=0A= ROOTFS: [images/fsl-image-test-imx6qsabrelite-20130515000446.rootfs.ext3]=0A= FSTYPE: [ext3]
=0A=


but halts after a while:
=0A=

There was an error running bitbake to determine TMPDIR
=0A= Here is the output from 'bitbake -e':
=0A= <=3Bhuuuuge dump of exported variables and python code following>=3B=0A=

 =3B



Am I using the command wrongly?

 =3B

 =3B

Thank you for your = help on both matters.


= --_67b19cec-6488-40ef-a405-f9c9467c4726_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com [209.85.214.179]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 89FC8E014FD for ; Mon, 20 May 2013 11:33:01 -0700 (PDT) Received: by mail-ob0-f179.google.com with SMTP id wd20so5705720obb.38 for ; Mon, 20 May 2013 11:32:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4Azr1rty0B8iBOl9+fjqGrMepbN63jZuHUIpGVbGm9s=; b=bEUu18qPzEI/sDELIp7O/glkVFkOY/CSe6awg8dkMd5Pu2kl26KSOoq13bvTcB6Pmn QkXKqcchRbiJ+HMAgbwF9wSHD2oQNez4K/X+ZnWG1L6eyNOnYePVx1ir0KG4L0OxUxOO MFCrJi49NJ2eY3A0uz9oXzBtkXpP5iboBYaVyi0VjnOIqU6B2v15Fwb+kKToE0mCRc0Y jJLmqtH5Pldy2XIUGjsu1ddwTZZZB48YxmBMMY+siqjh4uQy94JMYBiIUkp1+UGbFSfB Vw2Acyb1v/dO9YNpn4WJnHGvENZZan2WQ27KIYIyfJyqWUf21dGf89fsgGTEPjHCdnMx 9cDA== MIME-Version: 1.0 X-Received: by 10.182.120.70 with SMTP id la6mr27433640obb.76.1369074777559; Mon, 20 May 2013 11:32:57 -0700 (PDT) Sender: otavio.salvador@gmail.com Received: by 10.182.89.226 with HTTP; Mon, 20 May 2013 11:32:57 -0700 (PDT) In-Reply-To: References: Date: Mon, 20 May 2013 15:32:57 -0300 X-Google-Sender-Auth: Rbe9bzuqTmQo5Tu_wF9t1rR1zl4 Message-ID: From: Otavio Salvador To: Thanassis Silis Cc: "meta-freescale@yoctoproject.org" Subject: Re: trying to boot a bitbaked image in various ways X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 May 2013 18:33:01 -0000 Content-Type: multipart/alternative; boundary=089e013a0768c99cc904dd2a8f08 --089e013a0768c99cc904dd2a8f08 Content-Type: text/plain; charset=ISO-8859-1 On Fri, May 17, 2013 at 12:45 PM, Thanassis Silis 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 /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 --089e013a0768c99cc904dd2a8f08 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Fri, May 17, 2013 at 12:45 PM, Thanassis Silis <djnass_18@h= otmail.com> wrote:
Hi there, I am trying to boot the image I create= d in several ways:
1) extracted the tar.bz2 image (with tar xjvf) and di= d an nfs boot directly from the sabrelite board ! This succeeded.

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

You should 'dd= ' the .sdcard file to your microSD card.
=A0
3) I started reading on yocto project and tried = runqemu but it fails. Here is what I did:
=A0=A0=A0=A0=A0=A0=A0 cd <y= octo root>/sources/poky/
=A0=A0=A0=A0=A0=A0=A0 . ./oe-init-build-env<= br>=A0=A0=A0=A0=A0=A0=A0 cd build #done automatically at exit from above sc= ript
=A0=A0=A0=A0=A0=A0=A0 runqemu ../../../build/tmp/deply/images/uImage-blabla.bin=20 ../../../build/tmp/deply/images/fsl-image-test-blabla.ext3 ext3

=A0

the qemu start runnin= g,

The image b= uilt for SabreLITE won't be compatible with QEMU so it is expected to f= ail.

Regards,=A0

-- Otavio Salvador =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 O= .S. Systems
ht= tp://www.ossystems.com.br =A0 =A0 =A0 =A0http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854 =A0 =A0 =A0 =A0 =A0 =A0Mobile: +1 (347) 903-9750=
--089e013a0768c99cc904dd2a8f08-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dub0-omc1-s14.dub0.hotmail.com (dub0-omc1-s14.dub0.hotmail.com [157.55.0.213]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 1CAC7E01491 for ; Mon, 20 May 2013 15:44:27 -0700 (PDT) Received: from DUB116-W14 ([157.55.0.237]) by dub0-omc1-s14.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 20 May 2013 15:44:26 -0700 X-TMN: [G1nAt7e6/tyrRfQlynK57jyT8uIhAbgn] X-Originating-Email: [djnass_18@hotmail.com] Message-ID: From: Thanassis Silis To: Otavio Salvador Date: Mon, 20 May 2013 22:44:26 +0000 Importance: Normal In-Reply-To: References: , MIME-Version: 1.0 X-OriginalArrivalTime: 20 May 2013 22:44:26.0305 (UTC) FILETIME=[94B60B10:01CE55AB] Cc: "meta-freescale@yoctoproject.org" Subject: Re: trying to boot a bitbaked image in various ways X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 May 2013 22:44:28 -0000 Content-Type: multipart/alternative; boundary="_7bbae004-4232-4abd-816d-f998ad250664_" --_7bbae004-4232-4abd-816d-f998ad250664_ Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable Hi there=2C thank you for the reply. well=2C considering (2) below=2C I have already 'dd' the .sdcard image. but= the boot fails. I think the 2009.08 uboot image looks for a couple of file= s in the root folder of the target fs. The questions is though=2C how does = one use this u-boot.imx image that has been bitbaked? as for (3)=2C I understand this kernel will fail as the hardware is missin= g. But then again why does yocto have a command to even extract and run the= .tar.bz2 images "for use with nfs or qemu" ?=20 how can I run the specific rootfs i bitbaked through the emulator? Thank you once again for your help! Nass Date: Mon=2C 20 May 2013 15:32:57 -0300 Subject: Re: [meta-freescale] trying to boot a bitbaked image in various wa= ys From: otavio@ossystems.com.br To: djnass_18@hotmail.com CC: meta-freescale@yoctoproject.org On Fri=2C May 17=2C 2013 at 12:45 PM=2C Thanassis Silis wrote: =0A= =0A= =0A= =0A= Hi there=2C 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. =0A= Good. 2)=0A= copied the .sdcard image to an microSD card and tried to boot locally =0A= from the microSD. This fails as the uboot version on the board is the =0A= one that sabrelite shipped with =2C (2009.08 i think). How do I go about = =0A= updating the uboot (.imx file) that has generated from bitbake process? You should 'dd' the .sdcard file to your microSD card. =0A= 3) I started reading on yocto project and tried runqemu but it fails. Here = is what I did: cd /sources/poky/ . ./oe-init-build-env cd build #done automatically at exit from above script =0A= =0A= runqemu ../../../build/tmp/deply/images/uImage-blabla.bin =0A= ../../../build/tmp/deply/images/fsl-image-test-blabla.ext3 ext3 the qemu start running=2C=20 The image built for SabreLITE won't be compatible with QEMU so it is expect= ed to fail.=0A= Regards=2C=20 --=20 Otavio Salvador O.S. Systems http://www.ossystems.com.br http://projetos.ossystems.com.br =0A= Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 =0A= = --_7bbae004-4232-4abd-816d-f998ad250664_ Content-Type: text/html; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable
Hi there=2C
thank you for the= reply.
well=2C considering (2) below=2C I have already 'dd' the .sdcard= image. but the boot fails. I think the 2009.08 uboot image looks for a cou= ple of files in the root folder of the target fs. The questions is though= =2C how does one use this u-boot.imx image that has been bitbaked?

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

Thank you once again= for your help!
Nass

Date: Mon=2C 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: djna= ss_18@hotmail.com
CC: meta-freescale@yoctoproject.org




On Fri=2C May 17=2C 2013 at 12:45 PM=2C Thanassis Silis <=3Bdjnass_1= 8@hotmail.com>=3B wrote:
=0A=
=0A= =0A= =0A=
Hi there=2C I am trying to boot the image I crea= ted in several ways:
1) extracted the tar.bz2 image (with tar xjvf) and = did an nfs boot directly from the sabrelite board ! This succeeded.
=0A=

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

You should 'dd' the .sdc= ard file to your microSD card.
 =3B
=0A=
3) I started reading on yocto project and tried = runqemu but it fails. Here is what I did:
 =3B =3B =3B = =3B =3B =3B =3B cd <=3Byocto root>=3B/sources/poky/
&nbs= p=3B =3B =3B =3B =3B =3B =3B . ./oe-init-build-env<= br> =3B =3B =3B =3B =3B =3B =3B cd build #done = automatically at exit from above script
=0A=  =3B =3B =3B =3B =3B =3B =3B=0A= runqemu ../../../build/tmp/deply/images/uImage-blabla.bin =0A= ../../../build/tmp/deply/images/fsl-image-test-blabla.ext3 ext3

 =3B

the qemu = start running=2C

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

Regards=2C =3B

--
Ota= vio Salvador  =3B  =3B  =3B  =3B  =3B  =3B  =3B=  =3B  =3B  =3B  =3B  =3B  =3B  =3B O.S. System= s
http://www.o= ssystems.com.br  =3B  =3B  =3B  =3Bhttp://projetos.ossystems.com.br=
=0A= Mobile: +55 (53) 9981-7854  =3B  =3B  =3B  =3B  =3B &nb= sp=3BMobile: +1 (347) 903-9750
=0A=
= --_7bbae004-4232-4abd-816d-f998ad250664_-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id C6DB0E01515 for ; Mon, 20 May 2013 19:07:56 -0700 (PDT) Received: by mail-ob0-f172.google.com with SMTP id tb18so125047obb.17 for ; Mon, 20 May 2013 19:07:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=SzI3RlkF+r46byYdBn0FOkg3MyFF3+aYnYfoxn8Kajo=; b=BCwXTjFRDqm1z3pGiC9A6vH7jyWDb4ShJ/dPiNpHdlJb4TWSTf0Va+80FGrm2I9d8w 7hkdcgUlccXu1szsvByb9/fRRGfiQtApLV6QbvDpi85BL7R5mNVsLi8hJqkR77Owaj7U 3JUgdXRCwvgYsJRvlDormR1s15lPX+pVTJMw7Ridx8lK9/jNph2+6mRnsRCpSmEDJ/6r JtkYMe7WAJe3IrK3HG1sdzNCzK/oD7JvmoUvuwg+Ag6PKxZ0N/Ns+OauOdAw4gqVviV7 Blz5y5vFHh3P5SIpG8zKCE+0jtHT+SwrxoJjV4YHSJ9FsRzxHw8yU8SA+trWhVJy1040 ibtA== MIME-Version: 1.0 X-Received: by 10.60.133.240 with SMTP id pf16mr172354oeb.28.1369102075896; Mon, 20 May 2013 19:07:55 -0700 (PDT) Sender: otavio.salvador@gmail.com Received: by 10.182.89.226 with HTTP; Mon, 20 May 2013 19:07:55 -0700 (PDT) In-Reply-To: References: Date: Mon, 20 May 2013 23:07:55 -0300 X-Google-Sender-Auth: AfdOyZpnKlTTZaC6Mvfj9raBfKk Message-ID: From: Otavio Salvador To: Thanassis Silis Cc: "meta-freescale@yoctoproject.org" Subject: Re: trying to boot a bitbaked image in various ways X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 May 2013 02:07:57 -0000 Content-Type: multipart/alternative; boundary=047d7b471d9ce5300c04dd30eacb --047d7b471d9ce5300c04dd30eacb Content-Type: text/plain; charset=ISO-8859-1 On Mon, May 20, 2013 at 7:44 PM, Thanassis Silis 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 --047d7b471d9ce5300c04dd30eacb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



On Mon, May 20, 2013 at 7:44 PM, Thanassis Silis = <djnass_18@ho= tmail.com> wrote:
Hi there,
thank you for the reply.
well, consid= ering (2) below, I have already 'dd' the .sdcard image. but the boo= t 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 th= is u-boot.imx image that has been bitbaked?

Checking by it in Google= lead me to=A0http://boundarydevices.com/i-mx-6dq-u-boot-updates/=A0so I think you= can take a look there and upgrade it.
=A0
as for (3), I understa= nd this kernel will fail as=A0 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= 9;t know if it is worth the hassle.

Regards,=A0

-- Otavio Salvador =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 O= .S. Systems
ht= tp://www.ossystems.com.br =A0 =A0 =A0 =A0http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854 =A0 =A0 =A0 =A0 =A0 =A0Mobile: +1 (347) 903-9750=
--047d7b471d9ce5300c04dd30eacb-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f170.google.com (mail-pd0-f170.google.com [209.85.192.170]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 14339E01515 for ; Mon, 20 May 2013 19:18:41 -0700 (PDT) Received: by mail-pd0-f170.google.com with SMTP id x10so2656pdj.29 for ; Mon, 20 May 2013 19:18:40 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding :x-gm-message-state; bh=On1JJZfQZNclhjxXMvkv6x7fptMzkNab+nwv5nuuPYQ=; b=JPsH/CyHA8TQNaMtuW1O8m6FzkvQHOWoaDU0yoYF7AmZhz2B0ZzNUQ5Q9LKFI2H6lu a+LzRIzouwOCp4FP0JSVsXGpm7Y3lSAed32Ssstmk+cbS/lIhxAYnGWBsJ2cWJUNztOf pwbHuqDfSJsfjNGKmEkgF+/eLL7AyQiT19LwPRXKOCKEvkS/XVraXNP6QC6cVqr0lJoY k3CXjzbgBr5D5IpOgSMZ8ENAhjMjMoooiS61VPENx1H773/Qah5inWnsev3gWBFz1qtl Jr/UhHjFqjwp29g92kn7LJjFznTuQOhBllR4tmzi0IwdRR7+gaTAauyQwJmOWysi3C90 gsAg== X-Received: by 10.68.105.131 with SMTP id gm3mr284231pbb.168.1369102720651; Mon, 20 May 2013 19:18:40 -0700 (PDT) Received: from [192.168.1.8] (ip98-167-230-131.ph.ph.cox.net. [98.167.230.131]) by mx.google.com with ESMTPSA id wi6sm509872pbc.22.2013.05.20.19.18.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 May 2013 19:18:39 -0700 (PDT) Message-ID: <519AD97C.1090908@boundarydevices.com> Date: Mon, 20 May 2013 19:18:36 -0700 From: Eric Nelson User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: Otavio Salvador References: In-Reply-To: X-Gm-Message-State: ALoCoQmNliomknHc/6ChOGBM8G36/2kWxgRHgueePZZN+89qeWgyZxQw2WriboNwFCjQRVXAHpmo Cc: "meta-freescale@yoctoproject.org" Subject: Re: trying to boot a bitbaked image in various ways X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 May 2013 02:18:41 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thanks Otavio, On 05/20/2013 07:07 PM, Otavio Salvador wrote: > > On Mon, May 20, 2013 at 7:44 PM, Thanassis Silis > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id D6901E01515 for ; Mon, 20 May 2013 19:25:17 -0700 (PDT) Received: by mail-oa0-f44.google.com with SMTP id n12so148408oag.31 for ; Mon, 20 May 2013 19:25:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=dgWCkEX9YQ9nfotg8mRtODt3qlxYlwT0tl8wrgEPEnM=; b=e+h8k1nS3OPK+Uq4fTh6EpzkGTYBJQ92vg2nhLGZtXshGnCcYP4h199MPIe9bs5ZO1 tfEiZTIqVOmlmKQEx8jLwX+T9bPWlrOX/rF8Qz6Hn4wW4wMQcz2JkGHX2nQjY//mo2+e WMG+95CZP6bl2c5BoWXsZmFo2pwaAaFDisUdvVlgJUJZjwZopKKWf28Bx8nBAHFrG8Kj qOQ4ZP8ZKccmiERxGJWsResQlIAf2vlPkTIxGsHy0P/6SYvLSLXWU67dJf+Xaaqb+XS3 93+BeYtsOHY1i9kmtbbt6pV7N2i4DzWP2upoUCLuE0BD86Scl1D5p5yovTBfhbqI/FZx VczQ== MIME-Version: 1.0 X-Received: by 10.60.133.240 with SMTP id pf16mr198717oeb.28.1369103117310; Mon, 20 May 2013 19:25:17 -0700 (PDT) Sender: otavio.salvador@gmail.com Received: by 10.182.89.226 with HTTP; Mon, 20 May 2013 19:25:17 -0700 (PDT) In-Reply-To: <519AD97C.1090908@boundarydevices.com> References: <519AD97C.1090908@boundarydevices.com> Date: Mon, 20 May 2013 23:25:17 -0300 X-Google-Sender-Auth: EHRrb6xfPjCWQq6SY1OgM34_Y-Q Message-ID: From: Otavio Salvador To: Eric Nelson Cc: "meta-freescale@yoctoproject.org" Subject: Re: trying to boot a bitbaked image in various ways X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 May 2013 02:25:18 -0000 Content-Type: multipart/alternative; boundary=047d7b471d9cf7e21904dd3128e6 --047d7b471d9cf7e21904dd3128e6 Content-Type: text/plain; charset=ISO-8859-1 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 > **> 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 --047d7b471d9cf7e21904dd3128e6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable



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:djnas= s_18@hotmail.com>> wrote:

=A0 =A0 Hi there,
=A0 =A0 thank you for the reply.
=A0 =A0 well, considering (2) below, I have already 'dd' the .sdcar= d image.
=A0 =A0 but the boot fails. I think the 2009.08 uboot image looks for a
=A0 =A0 couple of files in the root folder of the target fs. The questions<= br> =A0 =A0 is though, how does one use this u-boot.imx image that has been
=A0 =A0 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:

=A0 =A0 =A0 =A0 U-Boot > run upgradeu

The next question I'd ask is "why are you upgrading"? There a= re
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.=A0

--
Otavio Salvado= r =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 O.S. Systems
http://www.ossyst= ems.com.br =A0 =A0 =A0 =A0http://projetos.ossystems.com.br
Mobile: +55 (53) = 9981-7854 =A0 =A0 =A0 =A0 =A0 =A0Mobile: +1 (347) 903-9750
--047d7b471d9cf7e21904dd3128e6-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dub0-omc1-s16.dub0.hotmail.com (dub0-omc1-s16.dub0.hotmail.com [157.55.0.215]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id CE8EDE01458 for ; Tue, 28 May 2013 06:45:44 -0700 (PDT) Received: from DUB116-W116 ([157.55.0.237]) by dub0-omc1-s16.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 28 May 2013 06:45:43 -0700 X-TMN: [7/eA5sCBBlTVcd7mYt5U8cHh0LhwXdN7kob+HQOqNFk=] X-Originating-Email: [djnass_18@hotmail.com] Message-ID: From: Thanassis Silis To: Otavio Salvador , Eric Nelson Date: Tue, 28 May 2013 13:45:43 +0000 Importance: Normal In-Reply-To: References: , , , , <519AD97C.1090908@boundarydevices.com>, MIME-Version: 1.0 X-OriginalArrivalTime: 28 May 2013 13:45:43.0053 (UTC) FILETIME=[A5DB33D0:01CE5BA9] Cc: "meta-freescale@yoctoproject.org" Subject: Re: trying to boot a bitbaked image in various ways X-BeenThere: meta-freescale@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Usage and development list for the meta-fsl-* layers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 May 2013 13:45:45 -0000 Content-Type: multipart/alternative; boundary="_66627529-1b51-4345-91fa-b60dd96868a3_" --_66627529-1b51-4345-91fa-b60dd96868a3_ Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable Hello everyone=2C excuse my late reply=2C but I was caught up in something else and couldn't = deal with this. However=2C it is now clear that at least as far as sabrelite board is conc= erned=2C it is best to avoid using the yocto generated uboot.imx bootloader= binary. I have the imx6q with 1GB ram model.=20 I also presume that the yocto image does not boot with the uboot-2009.08=2C= because the yocto image creates 2 partitions on the sdcard - a uboot (sd?1= ) and a rootfs (sd?2) partition=2C whereas the original sdcard contained ev= erything in the sd?1 (unique) partition. Looks like an update to a fresher uboot from boundary git is in order=2C ho= wever 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=2C 20 May 2013 23:25:17 -0300 Subject: Re: [meta-freescale] trying to boot a bitbaked image in various wa= ys From: otavio@ossystems.com.br To: eric.nelson@boundarydevices.com CC: djnass_18@hotmail.com=3B meta-freescale@yoctoproject.org On Mon=2C May 20=2C 2013 at 11:18 PM=2C Eric Nelson wrote: =0A= Thanks Otavio=2C =0A= =0A= On 05/20/2013 07:07 PM=2C Otavio Salvador wrote: =0A= =0A= =0A= On Mon=2C May 20=2C 2013 at 7:44 PM=2C Thanassis Silis > wrote: =0A= =0A= Hi there=2C =0A= thank you for the reply. =0A= well=2C considering (2) below=2C I have already 'dd' the .sdcard image. =0A= but the boot fails. I think the 2009.08 uboot image looks for a =0A= couple of files in the root folder of the target fs. The questions =0A= is though=2C how does one use this u-boot.imx image that has been =0A= bitbaked? =0A= =0A= Checking by it in Google lead me to =0A= http://boundarydevices.com/i-mx-6dq-u-boot-updates/ so I think you can =0A= take a look there and upgrade it. =0A= =0A= =0A= The Yocto image also has an upgrade script (6x_upgrade) which can be =0A= run from the U-Boot prompt through the 'upgradeu' command: =0A= =0A= U-Boot > run upgradeu =0A= =0A= The next question I'd ask is "why are you upgrading"? There are =0A= some valid reasons=2C especially if you're running something that =0A= pre-dates 2013-02-12=2C but I wouldn't make a practice of doing it =0A= during each Yocto release. =0A= =0A= We expect relatively infrequent updates to the boot loader=2C =0A= and everything that's shipped in the past few months should =0A= be adequate for most uses. =0A= =0A= We do have some updates for boot speed upcoming (which enable =0A= cache)=2C but those haven't been pushed to the meta-freescale =0A= project. =0A= =0A= If you're running on a Solo or Dual-Lite processor=2C you'll also =0A= risk bricking your board. We haven't put any instructions into =0A= Yocto to differentiate between the models=2C and it probably =0A= doesn't belong in this project. I will try to think how to support this=3B I'd like to avoid a machine defi= nition just for it.=20 --=20 Otavio Salvador O.S. Systems =0A= http://www.ossystems.com.br http://projetos.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 =0A= =0A= = --_66627529-1b51-4345-91fa-b60dd96868a3_ Content-Type: text/html; charset="iso-8859-7" Content-Transfer-Encoding: quoted-printable
Hello everyone=2C
excuse my l= ate reply=2C but I was caught up in something else and couldn't deal with t= his.

However=2C it is now clear that at least as far as =3B sabr= elite board is concerned=2C it is best to avoid using the yocto generated u= boot.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=2C b= ecause the yocto image creates 2 partitions on the sdcard - a uboot (sd?1) = and a rootfs (sd?2) partition=2C whereas the original sdcard contained ever= ything in the sd?1 (unique) partition.

Looks like an update to a fre= sher uboot from boundary git is in order=2C however I will first try to cre= ate an sdcard image from the yocto image .tar.bz2 so as to postpone the upd= ate a little longer.

Thank you for your help.
Nass

Date: Mon=2C 20 May 2013 23:25:17 -0300
Subject: R= e: [meta-freescale] trying to boot a bitbaked image in various ways
From= : otavio@ossystems.com.br
To: eric.nelson@boundarydevices.com
CC: djn= ass_18@hotmail.com=3B meta-freescale@yoctoproject.org




= On Mon=2C May 20=2C 2013 at 11:18 PM=2C Eric Nelson <= =3Beri= c.nelson@boundarydevices.com>=3B wrote:
=0A=
Thanks Otavio=2C

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

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

--
Otavio Salvador  = =3B  =3B  =3B  =3B  =3B  =3B  =3B  =3B  =3B=  =3B  =3B  =3B  =3B  =3B O.S. Systems
=0A= http://www.ossyst= ems.com.br  =3B  =3B  =3B  =3Bhttp://projetos.ossystems.com.br<= br>Mobile: +55 (53) 9981-7854  =3B  =3B  =3B  =3B  =3B =  =3BMobile: +1 (347) 903-9750
=0A= =0A=
= --_66627529-1b51-4345-91fa-b60dd96868a3_--