All of lore.kernel.org
 help / color / mirror / Atom feed
From: "piotr.lewicki" <piotr.lewicki@elfin.de>
To: Andrei Gherzan <andrei@gherzan.ro>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-raspberrypi][Question] How to build an hwup image for raspberrypi3
Date: Thu, 19 May 2016 17:26:15 +0200	[thread overview]
Message-ID: <573DDB17.5050007@elfin.de> (raw)
In-Reply-To: <20160519143914.GA3601@resin.home>

On 19.05.2016 16:39, Andrei Gherzan wrote:
> On Thu, May 19, 2016 at 02:15:22PM +0200, piotr.lewicki wrote:
>> Hello,
>> I'm trying to build a Yocto image for raspberrypi3.
>> I'm using only two layers:
>> - poky (krogoth: rev eff84a76acea1a0842194106a66684511f409842)
>> - meta-raspberrypi (master: rev 9912d38e97671704822d1aa05312a0439cb650d3)
>>
>> I have built it by cloning both layers from git (and changing poky branch),
>> then I sourced poky (source poky/oe-init-build-env), added meta-raspberrypi
>> layer in conf/bblayers.conf and in conf/local.conf changed MACHINE to
>> raspberrypi3.
>>
> I just tested the same revisions as you mentioned and the board boot for
> me. How do you test the board? Over serial?
>
> If you are using serial I suspecte you are not setting the serial
> console. if you are using tty1 (hdmi) you need to add the specific
> console argument to cmdline.
I'm using hdmi. Where can I find those console arguments?
>
>> Then I have built "rpi-hwup-image" using bitbake and dd'd it to an SD card.
>>
>> Unfortunately rpi-hwup-image does not work on raspberry pi 3.
>> Boot screen halts when 4 raspberry logos show up and that's it.
>>
>> On the other hand I have tried the same SD card with raspberry pi 2 and it
>> booted up (!?).
>>
>> Can you tell me if there is still support for meta-raspberrypi layer?
>> I found that this layer does not follow Yocto project naming convention for
>> branches (I think that the latest is "jethro", but nothing newer besides
>> "master").
>> Does this mean that there is no stable and up-to-date branch apart from
>> master?
>>
> What do you mean rpi is not following the yocto project naming
> convention? It does miss a branch for the last yocto release but there
> are already for the old ones.
Maybe I explained that wrong, but I've noticed that it's missing krogoth 
branch.
I think that if something like this occurs users are a little bit 
confused and have to choose between old branch (potentially outdated) 
and a master branch (potentially unstable).
>
>> Has anybody built a raspberrypi3 image?
>> Could you tell me which layers and which branches should I use?
>>
>>
>> Thanks,
>> Piotr Lewicki
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> --
> Andrei Gherzan
__

BR,
Piotr Lewicki


  reply	other threads:[~2016-05-19 15:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-19 12:15 [meta-raspberrypi][Question] How to build an hwup image for raspberrypi3 piotr.lewicki
2016-05-19 14:17 ` Khem Raj
2016-05-19 14:39 ` Andrei Gherzan
2016-05-19 15:26   ` piotr.lewicki [this message]
2016-05-19 15:27     ` Andrei Gherzan
2016-05-19 16:40       ` Khem Raj
2016-05-19 21:42         ` Andrei Gherzan

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=573DDB17.5050007@elfin.de \
    --to=piotr.lewicki@elfin.de \
    --cc=andrei@gherzan.ro \
    --cc=yocto@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.