All of lore.kernel.org
 help / color / mirror / Atom feed
From: wojciech.st@tutanota.com
To: Khem Raj <raj.khem@gmail.com>
Cc: <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] #raspberrypi
Date: Tue, 17 Dec 2019 13:19:11 +0100 (CET)	[thread overview]
Message-ID: <LwIn2xV--g-1@tutanota.com> (raw)
In-Reply-To: <CAMKF1sqYnuJ_QY6uyw1jTrVwni=oeOECrtx7LJVvVFnEq3xsFA@mail.gmail.com-LwHB5UB----1>

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

Hi Khem

Replacing 
IMAGE_INSTALL += "i2c-tools vim"
withIMAGE_INSTALL_append = " i2c-tools vim"

in my local.conf solve the problem.

More than half of the sources were rebuild.

Thanks a lot.

Now I found also the info in the manual "Using IMAGE_INSTALL with the += operator from the /conf/local.conf file or from within                    an image recipe is not recommended as it can cause ordering                    issues."

Regards,

Wojciech 
-- 
 Securely sent with Tutanota. Get your own encrypted, ad-free mailbox: 
 https://tutanota.com


Dec 17, 2019, 05:48 by raj.khem@gmail.com:

> On Mon, Dec 16, 2019 at 1:56 PM <wojciech.st@tutanota.com> wrote:
>
>>
>> Problem with rootfs boot on my raspberrypi.
>>
>> Hi
>> I am building simple image for my raspbery pi 3 A+ and connect to the pi via USB-UART converter and see the following in the console
>> ...
>> [ 2.071459] Run /bin/init as init process
>> [ 2.076507] Run /bin/sh as init process
>> sh: cannot set terminal process group (-1): Inappropriate ioctl for device
>> sh: no job control in this shell
>> sh-4.4#
>>
>>
>>
>> I build with the "bitbake core-image-base" and tried to run it on rpi 3A+, 3B, 3B+ and the problem is always the same it cannot switch to the rootfs on the sd card it seem like it stack at initramfs or some middle ground.
>>
>> I burn the *.rpi-sdimg image to SD card with dd from my Ubuntu16.04 host machine.
>> I tried with two branches thud and warrior and the problem is exactly the same.
>> The strange thing is that in this initramfs there are no tools like find grep modprobe etc. but I see my extra tools "i2c-tools vim"
>>
>> Here is my local.conf adjustments:
>> MACHINE ?= "raspberrypi3"
>> ENABLE_I2C = "1"
>> ENABLE_UART = "1"
>> IMAGE_INSTALL += "i2c-tools vim"
>>
>
> Can you turn this into
> IMAGE_INSTALL_append = " i2c-tools vim"
>
>>
>> and the bblayer.conf
>> BBLAYERS ?= " \
>>  /media/dave/Develop/yoctopi/warrior/sources/poky/meta \
>>  /media/dave/Develop/yoctopi/warrior/sources/poky/meta-poky \
>>  /media/dave/Develop/yoctopi/warrior/sources/poky/meta-yocto-bsp \
>>  /media/dave/Develop/yoctopi/warrior/sources/meta-openembedded/meta-oe \
>>  /media/dave/Develop/yoctopi/warrior/sources/meta-raspberrypi \
>>  "
>>
>> I tried also to build with the deprecated image "bitbake rpi-basic-image" but then I did not get my extra tools "i2c-tools vim".
>>
>> Anyone have any idea what can be wrong with my approach ?
>>
>> Regards,
>>
>> Wojciech
>>
>>
>> -=-=-=-=-=-=-=-=-=-=-=-
>> Links: You receive all messages sent to this group.
>>
>> View/Reply Online (#47702): https://lists.yoctoproject.org/g/yocto/message/47702
>> Mute This Topic: https://lists.yoctoproject.org/mt/68744766/1997914
>> Mute #raspberrypi: https://lists.yoctoproject.org/mk?hashtag=raspberrypi&subid=6692173
>> Group Owner: yocto+owner@lists.yoctoproject.org
>> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  [raj.khem@gmail.com]
>> -=-=-=-=-=-=-=-=-=-=-=-
>>


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

      parent reply	other threads:[~2019-12-17 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <W5UD.1576533409237003637.6umO@lists.yoctoproject.org>
2019-12-17  4:48 ` [yocto] #raspberrypi Khem Raj
2019-12-17  9:15   ` Stefano Babic
2019-12-17 16:00     ` Khem Raj
     [not found] ` <CAMKF1sqYnuJ_QY6uyw1jTrVwni=oeOECrtx7LJVvVFnEq3xsFA@mail.gmail.com-LwHB5UB----1>
2019-12-17 12:19   ` wojciech.st [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=LwIn2xV--g-1@tutanota.com \
    --to=wojciech.st@tutanota.com \
    --cc=raj.khem@gmail.com \
    --cc=yocto@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.