[yocto] Fwd: Need help for building kernel image with embeddedinitramfs.cpio

Andrea Adami andrea.adami at gmail.com
Wed May 9 11:41:08 PDT 2012


I've realized my answer was not sent to the list.

I'll do it now, being the subject may be of interest.

Andrea


---------- Forwarded message ----------
From: Andrea Adami <andrea.adami at gmail.com>
Date: Thu, May 3, 2012 at 6:24 PM
Subject: Re: [yocto] Need help for building kernel image with
embeddedinitramfs.cpio
To: giovanni.pavoni at exorint.it


On Thu, May 3, 2012 at 6:00 PM,  <giovanni.pavoni at exorint.it> wrote:
> Thanks for your suggestion. I have not yet tried with kernel modules
> but the whole build sequence appears fine and the output is running.
>
> I am hitting a problem thought with step 3
>
> I have this layout (meta-mylayer is parallel to meta-yocto):
>
> meta-mylayer/conf/machine/mymachine.conf
> meta-mylayer/recipes-kernel/linux/linux.inc
> meta-mylayer/recipes-kernel/linux/linux_2.6.37.bb
> meta-mylayer/recipes-kernel/linux/linux_2.6.37/mymachine/defconfig
>
> linux.inc inherit from kernel and I am setting
> PREFERRED_PROVIDER_virtual/kernel = "linux"
> PREFERRED_VERSION_linux ?= "2.6.37"
> in mymachine.conf.
>
> This builds and deploys a uImage-mymachine-"stamp1".bin fine for mymachine.
>
> I added a kernel recipe in my recipe-kernel layer
> like this:
>
> meta-mylayer/recipes-kernel/linux/linuxramfs_2.6.37.bb
> meta-mylayer/recipes-kernel/linux/linuxramfs_2.6.37/mymachine/defconfig
>
> in linuxramfs_2.6.37/mymachine/defconfig I patched all options for ramfs
> (source / compression etc)
> and tweaked linuxramfs_2.6.37.bb as per your indication (starting from the
> linux_2.6.37.bb
> I had up and running).
>
> Problems:
>
> 1. when I run "bitbake linuxramfs" I get
> "ERROR: Multiple .bb files are due to be built which each provide
> virtual/kernel"
>
> I am seeing multiple reference on the net about this error but I am not
> understanding
> how to handle. Both linuxramfs_2.6.37.bb and linux_2.6.37.bb are providing
> virtual/kernel.
>
this can be solved adding  PROVIDES = ""
(see the kexecboot kernels linked above)

> 2. "bitbake linuxramfs" deploys a uImage-mymachine-"stamp2".bin
> To overwrite this in a way I get a uImage-ramfs-mymachine-"stampxxx".bin
> (so that I can easily identify it against a normal uImage - only kernel)
> what do_* task should I reimplement in my linuxramfs_2.6.37.bb recipe?
>
KERNEL_IMAGE_BASE_NAME
KERNEL_IMAGE_SYMLINK_NAME

see:
http://cgit.openembedded.org/meta-openembedded/tree/meta-initramfs/recipes-kernel/linux/linux-yocto-tiny-kexecboot_3.2.bb

> Thanks in advance for your attention
>
YW

Cheers

Andrea (from Verona)

> Giovanni Pavoni
> R&D Department
>
> Exor International S.p.A.
> Via Monte Fiorino,9
> I-37057 San Giovanni Lupatoto (VR)
> Phone:+390458774839 - Fax:+390458779023
>
> giovanni.pavoni at exorint.it - www.exorint.net - www.exorint.it
>
>
> ATTENZIONE: Privacy Policy – D.Lgs. 196/2003
>  Le informazioni contenute in questo messaggio di posta elettronica sono di
> carattere privato e confidenziale ed esclusivamente rivolte al destinatario
> sopra indicato. Nel caso aveste ricevuto questo messaggio di posta
> elettronica per errore, vi comunichiamo che ai sensi del suddetto decreto è
> vietato l’uso, la diffusione, distribuzione o riproduzione da parte di ogni
> altra persona. Siete pregati di segnalarlo immediatamente rispondendo al
> mittente e di distruggere quanto ricevuto (compresi i file allegati) senza
> farne copia o leggerne il contenuto.
>
> This e-mail transmission contains information that is confidential and may
> be privileged. It is intended only for the addressee(s) named above. If you
> receive this e-mail in error, please do not read, copy or disseminate it in
> any manner. If you are not the intended recipient, any disclosure, copying,
> distribution or use of the contents of this information is prohibited.
> Please reply to the message immediately by informing the sender that the
> message was misdirected. After replying, please erase it from your computer
> system. Your assistance in correcting this error is appreciated.
>



More information about the yocto mailing list