How to build an hwup image for raspberrypi3

meta-raspberrypi piotr.lewicki 3 participants 7 messages May 19, 2016

Share & tools

piotr.lewicki

author

2016-05-19 12:15 UTC #0 lore raw

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.

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?

Has anybody built a raspberrypi3 image?
Could you tell me which layers and which branches should I use?

Thanks,
Piotr Lewicki

Khem Raj

2016-05-19 14:17 UTC #1 lore raw

Quoted 11 lines · piotr.lewicki

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.

Quoted 7 lines

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 (!?).

set

ENABLE_UART = "1"

in local.conf

Quoted 19 lines

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?
Has anybody built a raspberrypi3 image?
Could you tell me which layers and which branches should I use?
Thanks,
Piotr Lewicki
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Andrei Gherzan

2016-05-19 14:39 UTC #2 lore raw

In reply to piotr.lewicki

Quoted 11 lines · piotr.lewicki

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.

Quoted 8 lines

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 (!?).

Quoted 7 lines

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.

Quoted 11 lines

Has anybody built a raspberrypi3 image?
Could you tell me which layers and which branches should I use?
Thanks,
Piotr Lewicki
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

--
Andrei Gherzan

piotr.lewicki

author

2016-05-19 15:26 UTC #3 lore raw

Quoted 12 lines · Andrei Gherzan

Quoted 11 lines · piotr.lewicki
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.

Quoted 6 lines

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?

Quoted 16 lines

Quoted 9 lines
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 (!?).
Quoted 7 lines
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?

Quoted 3 lines

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).

Quoted 12 lines

Quoted 5 lines
Has anybody built a raspberrypi3 image?
Could you tell me which layers and which branches should I use?
Quoted 7 lines
Thanks,
Piotr Lewicki
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 2 lines

--
Andrei Gherzan

BR,
Piotr Lewicki

Andrei Gherzan

2016-05-19 15:28 UTC #4 lore raw

Quoted 13 lines · piotr.lewicki

Quoted 12 lines · Andrei Gherzan
Quoted 11 lines · piotr.lewicki
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.

Quoted 7 lines

Quoted 6 lines
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?

Boot partition, cmdline.txt.

Quoted 16 lines

Quoted 16 lines
Quoted 16 lines
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?

Quoted 8 lines

Quoted 3 lines
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).

Correct. I'll release krogoth too soon. Thanks.

Quoted 12 lines

Quoted 12 lines
Quoted 12 lines
Has anybody built a raspberrypi3 image?
Could you tell me which layers and which branches should I use?
Thanks,
Piotr Lewicki
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Quoted 6 lines

Quoted 2 lines
--
Andrei Gherzan
__
BR,
Piotr Lewicki

--
Andrei Gherzan

Khem Raj

2016-05-19 16:40 UTC #5 lore raw

Quoted 46 lines · Andrei Gherzan

Quoted 13 lines · piotr.lewicki
Quoted 12 lines · Andrei Gherzan
Quoted 11 lines · piotr.lewicki
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.
Quoted 7 lines
Quoted 6 lines
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?
Boot partition, cmdline.txt.
Quoted 19 lines
Quoted 19 lines
Quoted 9 lines
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 (!?).
Quoted 7 lines
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.

Quoted 7 lines

Quoted 5 lines
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).
Correct. I'll release krogoth too soon. Thanks.

I would suggest to delay branching until we really diverge from krogoth in incompatible ways just makes it easier to maintain.

Andrei Gherzan

2016-05-19 21:42 UTC #6 lore raw

Quoted 52 lines · Khem Raj

Quoted 52 lines · Andrei Gherzan
Quoted 13 lines · piotr.lewicki
Quoted 12 lines · Andrei Gherzan
Quoted 11 lines · piotr.lewicki
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.
Quoted 7 lines
Quoted 6 lines
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?
Boot partition, cmdline.txt.
Quoted 24 lines
Quoted 16 lines
Quoted 9 lines
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 (!?).
Quoted 7 lines
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?
Quoted 3 lines
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).

Quoted 5 lines

Quoted 1 line
Correct. I'll release krogoth too soon. Thanks.
I would suggest to delay branching until we really diverge from krogoth in incompatible ways just makes it easier to maintain.

Indeed. Sounds like a good idea.

--
Andrei Gherzan