Re: [yocto] yocto 1.6 - beaglebone black - cape manager

[Diego Sueiro]

TakTak,

On Wed, Sep 10, 2014 at 1:39 PM, TakkTakk  wrote:

> yocto buit with INSANE_SKIP_${PN} += "installed-vs-shipped" with no error.
> then i copied:
> cp MLO /media/boot/MLO
> cp u-boot-beaglebone.img /media/boot/u-boot.img
> sudo tar -xvf core-image-base-beaglebone.tar.gz -C /media/root/
>
> then, inserted microSD card to Beaglebone Black and bbb not boot. 4
> led lit steadily and nothing happens. I have cable hdmi connected to
> monitor.
>
> then i did
> $ cp uImage /media/boot
> $ mkdir /media/boot/dtbs
> $ cp uImage-am335x-boneblack.dtb /media/boot/dtbs/am335x-boneblack.dtb
>
> $ cp uEnv.txt /media/boot
>
> uEnv.txt from here
> http://www.embarcados.com.br/beaglebone-black-yocto/ but i changed
> zImage to uImage and still I can not boot the SD Card on the Beagle.
> All four LEDs stay lit steadily.
> What am i doing wrong?
>

Do you have another image installed on eMMC? If yes try to power up the
board with sdcard inserted and the switch S2 pressed (near sdcard slot).


Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br


/*long live rock 'n roll*/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto 1.6 - beaglebone black - cape manager

[TakkTakk]

Yes I have ubuntu on eMMC, when i don't press S2 ubuntu will be boot.
When i press switch S2 yocto don't boot and LED USR0 , USR1, USR2,
USR3 stay lit steadily.
I boot yocto 1.6 (but without layer meta-beagleboard) on sdcard and
everything was ok.

2014-09-11 11:19 GMT+02:00 Diego Sueiro :
> TakTak,
>
> On Wed, Sep 10, 2014 at 1:39 PM, TakkTakk  wrote:
>>
>> yocto buit with INSANE_SKIP_${PN} += "installed-vs-shipped" with no error.
>> then i copied:
>> cp MLO /media/boot/MLO
>> cp u-boot-beaglebone.img /media/boot/u-boot.img
>> sudo tar -xvf core-image-base-beaglebone.tar.gz -C /media/root/
>>
>> then, inserted microSD card to Beaglebone Black and bbb not boot. 4
>> led lit steadily and nothing happens. I have cable hdmi connected to
>> monitor.
>>
>> then i did
>> $ cp uImage /media/boot
>> $ mkdir /media/boot/dtbs
>> $ cp uImage-am335x-boneblack.dtb /media/boot/dtbs/am335x-boneblack.dtb
>>
>> $ cp uEnv.txt /media/boot
>>
>> uEnv.txt from here
>> http://www.embarcados.com.br/beaglebone-black-yocto/ but i changed
>> zImage to uImage and still I can not boot the SD Card on the Beagle.
>> All four LEDs stay lit steadily.
>> What am i doing wrong?
>
>
> Do you have another image installed on eMMC? If yes try to power up the
> board with sdcard inserted and the switch S2 pressed (near sdcard slot).
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
>
> /*long live rock 'n roll*/
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Feed URIs not inserted to /etc/opkg

[Matthias Gwerder]

Hi all,

I’m using ipk packages and runtime package management.

When migrating from dora to daisy, I noticed that the package feed
URIs are not being configured any more in the do_rootfs_ipk task. The
final /etc/opkg directory in the target root fs contains a basic
opkg.conf, but no local-ARCH-feed.conf files any more.

According to the documentation, it should be sufficient to append
“package-management” to IMAGE_FEATURES and define the
FEED_DEPLOYDIR_BASE_URI in local.conf.

I am referring to the following documentation:
http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#var-FEED_DEPLOYDIR_BASE_URI
http://www.yoctoproject.org/docs/1.7/dev-manual/dev-manual.html#using-runtime-package-management

Am I missing some changes there? Or has anyone else seen the same behavior?

(I also noticed there is an IPK_FEED_URIS variable in the reference
manual, but defining that one did not help either.)

Matthias
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] EXTERNALSRC

[Nemicolopterus Crypticus]

Ah - thank you! It's very clear now. Yes I think the formatting will make
it more clear. Examples also help :)

Something's still not working the way I'm expecting, though. According to
this

:
"...this class expects the source code to support recipe builds that use
the B

variable
to point to the directory in which the OpenEmbedded build system places the
generated objects built from the recipes."

In my recipe, I have not set EXTERNALSRC_BUILD, so B is the default output
directory I'm expecting.  However, I'm still seeing generated objects show
up in my source tree.  Since I'm using automake, I see aclocal.m4,
autom4te.cache, and other automake artifacts.  Is there any way to get
these to show up in my build tree after they've been generated and used by
autotools?

Alternatively, is there an easy way to remove particular newly-created
artifacts from the source tree?


On Tue, Sep 9, 2014 at 10:10 PM, Nicolas Dechesne <
nicolas.deche...@linaro.org> wrote:

> On Wed, Sep 10, 2014 at 7:07 AM, Rifenbark, Scott M
>  wrote:
> > I should have used a formatting tag in the manual source to indicate
> "myrecipe" as user input.  Without the formatting, it implies that
> "myrecipe" is literal when it is not.  I guess the example is not
> technically wrong if the recipe is actually named "myrecipe".  I like your
> added information about setting it in the recipe.  I will add that as well.
>
> ah. ok. i see!
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Specified toolchain directory does not contain a toolchain generated with meta-ide-support.

[Nemicolopterus Crypticus]

I'm trying to set up the development environment following these
instructions:http://www.yoctoproject.org/docs/1.6/adt-manual/adt-manual.html#adt-prepare


I'm currently trying to use a toolchain from within the Build
directory, so I'm following these instructions:

http://www.yoctoproject.org/docs/1.6/adt-manual/adt-manual.html#using-the-toolchain-from-within-the-build-tree


I sourced the build environment script, and set MACHINE correctly,
then I did bitbake meta-ide-support.


But in Eclipse, when I try to point to the toolchain, I'm seeing this
error: Specified toolchain directory does not contain a toolchain
generated with "bitbake meta-ide-support".

 I can see from this post
,
that this means Poky.Env.Script.Nonexist is true:


+Poky.Env.Script.Nonexist = Specified toolchain directory does not contain a
toolchain generated with meta-ide-support.


But the scripts appears to be there. Here are the contents of my
build/tmp directory:

/oe-core/build/tmp-eglibc$ ls
abi_version  cache  deploy
*environment-setup-cortexa8hf-vfp-neon-linux-gnueabi*  log  qa.log
saved_tmpdir  sstate-control  stamps  sysroots  work


Any pointers?
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Specified toolchain directory does not contain a toolchain generated with meta-ide-support.

[Bob Cochran]

On 09/11/2014 07:41 PM, Nemicolopterus Crypticus wrote:

I'm trying to set up the development environment following these instructions:
http://www.yoctoproject.org/docs/1.6/adt-manual/adt-manual.html#adt-prepare


I'm currently trying to use a toolchain from within the Build directory, so I'm 
following these instructions:

http://www.yoctoproject.org/docs/1.6/adt-manual/adt-manual.html#using-the-toolchain-from-within-the-build-tree


I sourced the build environment script, and set MACHINE correctly, then I 
didbitbake meta-ide-support.


But in Eclipse, when I try to point to the toolchain, I'm seeing this error:Specified 
toolchain directory does not contain a toolchain generated with "bitbake 
meta-ide-support".



I can see fromthis post  
, that 
this means Poky.Env.Script.Nonexist is true:


+Poky.Env.Script.Nonexist = Specified toolchain directory does not contain a
toolchain generated with meta-ide-support.


But the scripts appears to be there. Here are the contents of my build/tmp 
directory:

/oe-core/build/tmp-eglibc$ ls
abi_version  cache  deploy*environment-setup-cortexa8hf-vfp-neon-linux-gnueabi* 
  log  qa.log  saved_tmpdir  sstate-control  stamps  sysroots  work


Any pointers?


Just double checking that you are specifying the "toolchain root 
location" as your top level build directory (the one above 
/conf/local.conf - the directory where you run bitbake).


I'm just wondering since I think the label for this field is somewhat 
misleading.


Otherwise, on the surface it seems that you have what you need.

Bob











--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Release Candidate Build for yocto-1.7_M3.rc2 now available.

[Poky Build User]

A release candidate build for yocto-1.7_M3.rc2 is now available at:

 
http://autobuilder.yoctoproject.org/pub/releases/yocto-1.7_M3.rc2


Please begin QA on this build as soon as possible.


Build hash information: 
meta-intel : 200ebb54f46f364e7eb1738c5e993374f03f407d 
meta-fsl-arm : dad75d7e653f9575e959b17478ff2a0df5bf09dc 
meta-minnow : 238a45e9da8bbfff7a6af220b48c11cabd31e01c 
meta-qt3 : 3016129d90b7ac8517a5227d819f10ad417b5b45 
meta-fsl-ppc : 478f29c3e97760f2ff443227950ce21d9510a280 
poky : 429802fe6691c8a70ec9735c0db4c6a4e1e1b038 


This is an automated message from
The Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder
Email: elizabeth.flana...@intel.com 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Populate /var/lib/opkg/status

[Dag Björklund]

On 10.09.2014 14:50, Burton, Ross wrote:

On 10 September 2014 12:20, Dag Björklund  wrote:

How do I populate /var/lib/opkg/status so that all .ipk packages that Yocto
has installed for me are seen if I e.g. say 'opkg list-installed'?

The IMAGE_FEATURE "package-management" controls whether images have
this data preserved, so you probably need to add that to your image.

Ross
Thanks, found this in the documentation now as well. Unfortunately I 
don't see a difference.
Should I find a /var/lib/opkg/status file after adding the feature and 
building?


Dag

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto