Date   

Re: Google GN support

Joel Winarske
 

I had to revisit this for Google Flutter LTS support as upstream (Google Flutter team) wasn't interested in providing tar.xz releases.

We have two working solutions for Flutter gclient as of today.

1. gclient fetcher.  This fetches the project using gclient and archives the whole source tree.  I call it the gclient snapshot solution.  Downside is initial fetch time due to archive time, but subsequent build times are good.  So only really useful if you don't switch versions often.

2. Pre-process project using python script and add cipd fetcher support to layer.  This script creates an inc file that gets included by a recipe.  Initial fetch time is about 2.5x build time, with similar build times to gclient fetcher; ~3 minutes, some sub 3 minutes.  The current approach before this method average build times were ~6 minutes.  So this approach improves build time, and provides LTS.  It factors out the use of gclient/depot_tools in the fetch process.

gclient_bitbake.py.  The script generates a do_run_hooks task using gn conditionals.

script output

cipd:// fetcher impl:

It currently only works out of the box for the flutter project, but I did use it to create a recipe for luci-go -> cipd.

I mocked up changes to support the v8 project; see gaps for generic support.  It does require dynamically compiling python code to manage conditionals, and needs a bit more work.  After which python_bitbake.py should work for any gclient based project.

gs:// fetcher (Google Storage) support is also planned.  So in cases which download google storage artifacts in hook, it would allow moving that to SRC_URI as gs:// element for LTS scenario.

If anyone finds this useful/interesting or they want to collaborate on improvements let me know.

I do think cipd:// fetcher support would be a good addition to oe-core.


Joel

On Tue, Oct 5, 2021 at 3:55 PM Joel Winarske via lists.yoctoproject.org <joel.winarske=gmail.com@...> wrote:

> look at meta-browser/meta-chromium as well.

The download archive (tar.xz) approach may be the easiest solution.  Then one would just need to make a versioned recipe for each LTS.

Thanks Khem!




Re: How to disable Bluetooth of Raspberry Pi from Yocto?

Khem Raj
 

On Wed, Mar 9, 2022 at 1:01 AM Sourabh Hegde <hrsourabh011@...> wrote:

Hello Tomasz,

Thanks for quick reply.

meta-raspberrypi provide recipe just for the `config.txt` file. I don't know which Yocto version you are usingbut on master it looks like this https://github.com/agherzan/meta-raspberrypi/blob/master/recipes-bsp/bootfiles/rpi-config_git.bb#L1You will need some bbappend in your custom recipe to extend config.txt wtih `dtoverlay=disable-bt`.

I forgot to mention, I am on "Honister" release. Yes, I added rpi_config_git.bbappend file

Did you try to hit an enter couple of times and then maybe log in?

Yes, I tried that, but it's not working. May be it's fails to respond for keyboard inputs.
can you check /boot/config.txt on target and see if this change is
persisting in your image or not

Regards,
Sourabh


Re: imx7d-pico with hardknott - I need help enabling remoteproc in device tree to show /linux/remoteproc.h file and modules in /sys/class/remoteproc

Khem Raj
 

On Wed, Mar 9, 2022 at 8:04 AM Neuber Sousa <neuberfran@...> wrote:

Hi,
I do this:$ mkdir tn-imx-yocto$ cd tn-imx-yocto$ repo init -u https://github.com/TechNexion/tn-imx-yocto-manifest.git -b hardknott_5.10.y-stable -m imx-5.10.72-2.2.0-2022Q1.xml$ repo sync -j8$ DISTRO=fsl-imx-x11 MACHINE=pico-imx7 BASEBOARD=pi source tn-setup-release.sh -b build-x11-pico-imx7$ bitbake core-image-base

I enable REMOTEPROC and RPMsg in kernel. I have imx_rpmgs_tty module. But I don't have remoteproc. Why?
how did you enable it? every BSP has sometimes its own way of adding knobs.



imx7d-pico with hardknott - I need help enabling remoteproc in device tree to show /linux/remoteproc.h file and modules in /sys/class/remoteproc

Neuber Sousa <neuberfran@...>
 

Hi,
I do this:$ mkdir tn-imx-yocto$ cd tn-imx-yocto$ repo init -u https://github.com/TechNexion/tn-imx-yocto-manifest.git -b hardknott_5.10.y-stable -m imx-5.10.72-2.2.0-2022Q1.xml$ repo sync -j8$ DISTRO=fsl-imx-x11 MACHINE=pico-imx7 BASEBOARD=pi source tn-setup-release.sh -b build-x11-pico-imx7$ bitbake core-image-base

I enable REMOTEPROC and RPMsg in kernel. I have imx_rpmgs_tty module. But I don't have remoteproc. Why? 


Re: Howto build packages for dependencies of an out of image recipe build.

Robert Joslyn
 

On Mar 9, 2022, at 4:59 AM, Daniel Squires <dan@...> wrote:

Just to be absolutely clear, here is the result of having run bitbake build-essential having first removed and thus started with a clean tmp dir.

dan@melon:/home/dan/workspace_ssd/kas/build$ find tmp/deploy/deb/
tmp/deploy/deb/
tmp/deploy/deb/all
tmp/deploy/deb/all/build-essential-ptest_1.0.0-r0.0_all.deb
tmp/deploy/deb/all/build-essential-dev_1.0.0-r0.0_all.deb
tmp/deploy/deb/all/build-essential_1.0.0-r0.0_all.deb
tmp/deploy/deb/all/build-essential-dbg_1.0.0-r0.0_all.deb
This is now expected behavior. I discovered it a few months ago in my package feed builds:
https://lists.yoctoproject.org/g/yocto/topic/88553371#55926

Bitbake no longer does recursive packaging tasks since they are not always needed. To get all the recursive packages, you need to run bitbake --runall build build-essential


Robert


Re: Howto build packages for dependencies of an out of image recipe build.

Daniel Squires
 

Just to be absolutely clear, here is the result of having run bitbake build-essential having first removed and thus started with a clean tmp dir.

dan@melon:/home/dan/workspace_ssd/kas/build$ find tmp/deploy/deb/
tmp/deploy/deb/
tmp/deploy/deb/all
tmp/deploy/deb/all/build-essential-ptest_1.0.0-r0.0_all.deb
tmp/deploy/deb/all/build-essential-dev_1.0.0-r0.0_all.deb
tmp/deploy/deb/all/build-essential_1.0.0-r0.0_all.deb
tmp/deploy/deb/all/build-essential-dbg_1.0.0-r0.0_all.deb


Activate ivi shell on core-image-weston

Edgar Mobile
 

Greetings,

can someone tell me if and how it is possible to activate the ivi shell as default shell in core-image-weston ?

Regards


Re: Howto build packages for dependencies of an out of image recipe build.

Daniel Squires
 

Yes, in RDPENDS, here's an example of an attempt at the equivalent of Ubuntu's build-essential package:

DESCRIPTION = "Informational list of build-essential pacakages"
 
inherit packagegroup
 
PACKAGES = "\
    ${PN} \
    "
 
RDEPENDS:${PN} = "\
    libc6-dev \
    g++ \
    gcc \
    make \
    "
 
INSANE_SKIP:${PN} = "dev-deps"


Re: Howto build packages for dependencies of an out of image recipe build.

Daniel Squires
 

Just want to add that it seems to run the do_package task but not the do_package_write_deb one for each of the dependencies.


Re: Howto build packages for dependencies of an out of image recipe build.

Bruce Ashfield
 

On Wed, Mar 9, 2022 at 5:24 AM Daniel Squires <dan@...> wrote:

We have our image and it is working as we need.
We have an apt repo setup and working so that we can install additional packages within a deployment of the image.
However when we manually bitbake additional packages (e.g bitbake my-optional-recipe) which we want to make available within this apt repository by default only the package for my-optional-recipe gets built, although all the dependencies of my-optional-recipe get built, none of them are packaged. how do we make sure all the dependencies have packages built?
Are the dependencies in the recipe as RDEPENDS ? If so, they will be
built and packaged. If they weren't, then image assembly and pretty
much any package feed would be non-functional.

Bruce


Best Regards

Dan


--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II


Re: [qa-build-notification] QA notification for completed autobuilder build (yocto-3.5_M3.rc1)

Teoh, Jay Shen
 

Hello All,

This is the full report for yocto-3.5_M3.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects.

No new issue found.


Thanks,
Jay

-----Original Message-----
From: qa-build-notification@... <qa-build-
notification@...> On Behalf Of Richard Purdie
Sent: Tuesday, 8 March, 2022 12:08 AM
To: <yocto@...> <yocto@...>
Cc: qa-build-notification <qa-build-notification@...>
Subject: [qa-build-notification] QA notification for completed autobuilder
build (yocto-3.5_M3.rc1)

A build flagged for QA (yocto-3.5_M3.rc1) was completed on the autobuilder
and is available at:


/srv/autobuilder/autobuilder.yocto.io/pub/releases/yocto-3.5_M3.rc1


Build hash information:

bitbake: 8055ec360507e6a678ee5c4018ec1ab7f5a9cce5
meta-agl: 9df7a40dd0b5e3ee1ed72e460dc99193eeb4bd6c
meta-arm: 643cf58a6988505dbd9243142496a3bc649efb1c
meta-aws: 214a5867b3b0d9ba54818aabb1711eadf4ba9eb3
meta-gplv2: 5c9f033892ae56c178616859a1245efd375e64bd
meta-intel: 6fba58adb3823cd7578062b0afa4938dd7206adb
meta-mingw: d49e803e4b8b62dc148c182af499e582e7684de4
meta-openembedded: a75b9a549563e09fca9a8c280f5731152913b651
oecore: 4caea2d32f177fbbe3887f37b6700b2b4996b2be
poky: afbdba9b12bc12638d82813d1cd31ec479971c4b



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...







[meta-zephyr][PATCH] zephyr-kernel: Add CVE_PRODUCT to fix cve-check lookup fail

Davide Gardenal
 

From: Davide Gardenal <davide.gardenal@...>

Add CVE_PRODUCT override to fix a lookup problem when performing cve-check,
if not setted it will search for the recipe name, that in this case depends
on the recipe used to build zephyr (eg. zephyr-philosophers)

Signed-off-by: Davide Gardenal <davide.gardenal@...>
---
.../recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc | 2 ++
1 file changed, 2 insertions(+)

diff --git a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
index e060a95..ea20a18 100644
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
@@ -1,6 +1,8 @@
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://LICENSE;md5=fa818a259cbed7ce8bc2a22d35a464fc"

+CVE_PRODUCT = "zephyr"
+
inherit cmake

# This file might be included from other places (like other layers) and not
--
2.32.0


Howto build packages for dependencies of an out of image recipe build.

Daniel Squires
 

We have our image and it is working as we need.
We have an apt repo setup and working so that we can install additional packages within a deployment of the image.
However when we manually bitbake additional packages (e.g bitbake my-optional-recipe) which we want to make available within this apt repository by default only the package for my-optional-recipe gets built, although all the dependencies of my-optional-recipe get built, none of them are packaged. how do we make sure all the dependencies have packages built?

Best Regards

Dan


Re: How to disable Bluetooth of Raspberry Pi from Yocto?

Sourabh Hegde
 

Hello Tomasz,

Thanks for quick reply.

meta-raspberrypi provide recipe just for the `config.txt` file. I don't know which Yocto version you are usingbut on master it looks like this https://github.com/agherzan/meta-raspberrypi/blob/master/recipes-bsp/bootfiles/rpi-config_git.bb#L1You will need some bbappend in your custom recipe to extend config.txt wtih `dtoverlay=disable-bt`.
I forgot to mention, I am on "Honister" release. Yes, I added rpi_config_git.bbappend file

Did you try to hit an enter couple of times and then maybe log in?
Yes, I tried that, but it's not working. May be it's fails to respond for keyboard inputs.

Regards,
Sourabh


Re: How to disable Bluetooth of Raspberry Pi from Yocto?

tomzy
 

Hello All,

Hi

I have a question regarding disabling bluetooth of my Raspberry Pi Compute Module 4. I know that we need to set "dtoverlay=disable-bt" in config.txt

But how to do it from Yocto? Should I include this in conf/local.conf?

meta-raspberrypi provide recipe just for the `config.txt` file. I don't know which Yocto version you are using
but on master it looks like this https://github.com/agherzan/meta-raspberrypi/blob/master/recipes-bsp/bootfiles/rpi-config_git.bb#L1
You will need some bbappend in your custom recipe to extend config.txt wtih `dtoverlay=disable-bt`.
E.g. the bbappend should have the following

```
do_deploy:append() {
  echo "dtoverlay=disable-bt" >> $CONFIG
}
```

While booting my serial console is stuck here:

OpenEmbedded nodistro.0 raspberrypi4-64 ttyS0

raspberrypi4-64 login: [   14.718847] Bluetooth: HCI UART driver ver 2.3
[   14.723478] Bluetooth: HCI UART protocol H4 registered
[   14.728877] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   14.735632] Bluetooth: HCI UART protocol Broadcom registered
[   14.985386] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   14.990829] Bluetooth: BNEP filters: protocol multicast
[   14.996781] Bluetooth: BNEP socket layer initialized
[   15.016364] NET: Registered protocol family 38
[   15.024632] audit: type=1334 audit(1646676238.549:6): prog-id=9 op=LOAD
[   15.031791] audit: type=1334 audit(1646676238.549:7): prog-id=10 op=LOAD
[   15.103792] Bluetooth: RFCOMM TTY layer initialized
[   15.108976] Bluetooth: RFCOMM socket layer initialized
[   15.114255] Bluetooth: RFCOMM ver 1.11

Can anyone please let me know whether disabling Bluetooth will solve this?

To be honest, it doesn't look like it hangs. There is a login prompt

```
raspberrypi4-64 login:
```
Did you try to hit an enter couple of times and then maybe log in?

Your help will be much appreciated.

Thanks in advance.

Greetings,

Tomasz Żyjewski
Embedded Systems Engineer
GPG: 5C495EA3EBEECA59
https://3mdeb.com | @3mdeb_com


How to disable Bluetooth of Raspberry Pi from Yocto?

Sourabh Hegde
 

Hello All,

I have a question regarding disabling bluetooth of my Raspberry Pi Compute Module 4. I know that we need to set "dtoverlay=disable-bt" in config.txt

But how to do it from Yocto? Should I include this in conf/local.conf?

While booting my serial console is stuck here:

OpenEmbedded nodistro.0 raspberrypi4-64 ttyS0

raspberrypi4-64 login: [   14.718847] Bluetooth: HCI UART driver ver 2.3
[   14.723478] Bluetooth: HCI UART protocol H4 registered
[   14.728877] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   14.735632] Bluetooth: HCI UART protocol Broadcom registered
[   14.985386] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   14.990829] Bluetooth: BNEP filters: protocol multicast
[   14.996781] Bluetooth: BNEP socket layer initialized
[   15.016364] NET: Registered protocol family 38
[   15.024632] audit: type=1334 audit(1646676238.549:6): prog-id=9 op=LOAD
[   15.031791] audit: type=1334 audit(1646676238.549:7): prog-id=10 op=LOAD
[   15.103792] Bluetooth: RFCOMM TTY layer initialized
[   15.108976] Bluetooth: RFCOMM socket layer initialized
[   15.114255] Bluetooth: RFCOMM ver 1.11

Can anyone please let me know whether disabling Bluetooth will solve this?

Your help will be much appreciated.

Thanks in advance.


Re: [meta-rockchip][PATCH] wic: add e2fsprogs dependency

Trevor Woerner
 

On Tue 2022-03-08 @ 12:04:15 PM, Trevor Woerner via lists.yoctoproject.org wrote:
Started seeing the following error in my builds:

ERROR: A native program mkfs.ext4 required to build the image was not found
Please make sure wic-tools have e2fsprogs-native in its DEPENDS

Signed-off-by: Trevor Woerner <twoerner@...>
---
conf/machine/include/rockchip-wic.inc | 1 +
1 file changed, 1 insertion(+)
Applied to meta-rockchip, master.


Re: suricata: enable lua support

Gary Huband
 

The problems is that the configure.ac file is hard coded for lua5.1.  See

https://forum.suricata.io/t/lua-5-4-3-and-suricata-undefined-reference-error/1906/5

I created a patch to change configure.ac to use lua5.3 (I'm using Zeus). But when I "bitbake suricata" I'm getting the same error because it's not updating the configure file.  Do I also have to fix the configure file or is there some way I can force a autoreconf?

Thanks

Gary


From: Khem Raj <raj.khem@...>
Sent: Saturday, March 5, 2022 2:55 AM
To: Gary Huband <Gary@...>
Cc: akuster808 <akuster808@...>; yocto@... <yocto@...>
Subject: Re: [yocto] suricata: enable lua support
 


On Fri, Mar 4, 2022 at 6:23 PM Gary Huband via lists.yoctoproject.org <gary=missionsecure.com@...> wrote:
The Suricata install site also says to install
liblua5.1-dev
Does this mean that Suricata needs lua 5.1 (which is very old)?? For Zeus the lua recipe is 5.3.5.

Do I need to create a recipe for lua 5.1?

seems so, lua5.1 is not ABI compatible with newer Lua, so if an app needs this version then
you will have to add it, perhaps see if you can just use internal version or something like that

Gary

From: akuster808 <akuster808@...>
Sent: Friday, March 4, 2022 7:52 PM
To: Gary Huband <Gary@...>; yocto@... <yocto@...>
Subject: Re: [yocto] suricata: enable lua support
 


On 3/4/22 15:02, Gary Huband via lists.yoctoproject.org wrote:
>
> Adding DEPENDS += "lua"  fixed that error.  I'm assuming that allows
> the configure to find lua.
>
> Now I'm getting a compile error
>

I added this to the recipe and it appears the liblua it  is looking for
does not exist.

PACKAGECONFIG[lua] = "--enable-lua
--with-liblua-includes=${STAGING_INCDIR}
--with-liblua-libraries==${STAGING_LIBDIR}, --disable-lua,lua, lua"

Error:

checking for luaL_openlibs in -llua5.1... no
|
|    ERROR!  liblua library not found, go get it
|    from https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Flua.org%2Findex.html&amp;data=04%7C01%7Cgary%40missionsecure.com%7C7f9815dcc0c142b6d92d08d9fe4262cb%7Cf0ca9611f13f4dc98e1b119172b8ec5d%7C0%7C1%7C637820383359878260%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=FdB7jyQwXX%2BVjjhLSDhKNSt41GUOgdg%2FG3ajSKIElo0%3D&amp;reserved=0 or your distribution:
|
|    Ubuntu: apt-get install liblua5.1-dev


It may be  the lua recipe.  I only see the static lib 'liblua.a'

-armin

> |
> /tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/suricata/6.0.3-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/9.2.0/ld:
> util-lua-dns.o: in function `DnsGetTxid':
> |
> /usr/src/debug/suricata/6.0.3-r0/suricata-6.0.3/src/util-lua-dns.c:80:
> undefined reference to `rs_dns_lua_get_tx_id'
> |
> /tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/suricata/6.0.3-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/9.2.0/ld:
> util-lua-dns.o: in function `DnsGetAnswerTable':
> |
> /usr/src/debug/suricata/6.0.3-r0/suricata-6.0.3/src/util-lua-dns.c:125:
> undefined reference to `rs_dns_lua_get_answer_table'
> |
> /tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/suricata/6.0.3-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/9.2.0/ld:
> util-lua-dns.o: in function `DnsGetAuthorityTable':
> |
> /usr/src/debug/suricata/6.0.3-r0/suricata-6.0.3/src/util-lua-dns.c:133:
> undefined reference to `rs_dns_lua_get_authority_table'
> |
> /tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/suricata/6.0.3-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/9.2.0/ld:
> util-lua-dns.o: in function `DnsGetQueryTable':
> |
> /usr/src/debug/suricata/6.0.3-r0/suricata-6.0.3/src/util-lua-dns.c:117:
> undefined reference to `rs_dns_lua_get_query_table'
> |
> /tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/suricata/6.0.3-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/9.2.0/ld:
> util-lua-dns.o: in function `DnsGetDnsRrname':
> |
> /usr/src/debug/suricata/6.0.3-r0/suricata-6.0.3/src/util-lua-dns.c:69:
> undefined reference to `rs_dns_lua_get_rrname'
> |
> /tmp/work/cortexa7t2hf-neon-poky-linux-gnueabi/suricata/6.0.3-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi/../../libexec/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/9.2.0/ld:
> util-lua-dns.o: in function `DnsGetRcode':
> |
> /usr/src/debug/suricata/6.0.3-r0/suricata-6.0.3/src/util-lua-dns.c:92:
> undefined reference to `rs_dns_lua_get_rcode'
> | collect2: error: ld returned 1 exit status
> | Makefile:2118: recipe for target 'suricata' failed
> | make[2]: *** [suricata] Error 1
>
>
>
>


Gary Huband
Sr. Software and Systems Engineer

Office: 434.284.8071 x720
Direct: 434.260.4995
Gary@...

Follow Us!
LinkedIn  |  Blog  |  Website

: : : : : : : : : : : : : : : : : : : : : : : : : : :

MSi

This email and any files transmitted with it are confidential and proprietary and intended solely for the use of the individual or entity to whom they are addressed. Any dissemination, distribution or copying of this communication is strictly prohibited without our prior permission. If you received this in error, please contact the sender and delete the material from any computer.





Gary Huband
Sr. Software and Systems Engineer

Office: 434.284.8071 x720
Direct: 434.260.4995
Gary@...

Follow Us!
LinkedIn  |  Blog  |  Website

: : : : : : : : : : : : : : : : : : : : : : : : : : :

MSi

This email and any files transmitted with it are confidential and proprietary and intended solely for the use of the individual or entity to whom they are addressed. Any dissemination, distribution or copying of this communication is strictly prohibited without our prior permission. If you received this in error, please contact the sender and delete the material from any computer.


[meta-rockchip][PATCH] wic: add e2fsprogs dependency

Trevor Woerner
 

Started seeing the following error in my builds:

ERROR: A native program mkfs.ext4 required to build the image was not found
Please make sure wic-tools have e2fsprogs-native in its DEPENDS

Signed-off-by: Trevor Woerner <twoerner@...>
---
conf/machine/include/rockchip-wic.inc | 1 +
1 file changed, 1 insertion(+)

diff --git a/conf/machine/include/rockchip-wic.inc b/conf/machine/include/rockchip-wic.inc
index 30b0d57..6fa5367 100644
--- a/conf/machine/include/rockchip-wic.inc
+++ b/conf/machine/include/rockchip-wic.inc
@@ -7,6 +7,7 @@ WKS_FILE = "rockchip.wks"
WKS_FILE_DEPENDS ?= " \
mtools-native \
dosfstools-native \
+ e2fsprogs-native \
virtual/bootloader \
virtual/kernel \
"
--
2.34.1.75.gabe6bb3905


Re: [meta-zephyr][PATCH 2/2] zephyr-kernel: add support for zephyr v3.0.0

Jon Mason
 

On Tue, Mar 08, 2022 at 11:12:00AM +0100, Bartosz Golaszewski wrote:
From: Bartosz Golaszewski <bartosz.golaszewski@...>

Add support for zephyr v3.0.0 and make it the preferred version.

Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@...>
Ran this patch through my nightly CI and it comes out green
https://gitlab.com/jonmason00/meta-zephyr/-/pipelines/487255541

Tested-by: Jon Mason <jon.mason@...>

---
.../zephyr-kernel/zephyr-kernel-src-2.7.1.inc | 16 ++---
.../zephyr-kernel/zephyr-kernel-src-3.0.0.inc | 70 +++++++++++++++++++
.../zephyr-kernel/zephyr-kernel-src.inc | 12 ++--
3 files changed, 83 insertions(+), 15 deletions(-)
create mode 100644 meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-3.0.0.inc

diff --git a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.7.1.inc b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.7.1.inc
index e090234..a2c100c 100644
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.7.1.inc
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.7.1.inc
@@ -2,11 +2,11 @@ SRCREV_FORMAT = "default_cmsis"

# These repositories are specific to post-2.6 branches

-SRC_URI += "\
- git://github.com/zephyrproject-rtos/hal_telink.git;protocol=https;nobranch=1;destsuffix=git/modules/hal/telink;name=telink \
- git://github.com/zephyrproject-rtos/lz4.git;protocol=https;nobranch=1;destsuffix=git/modules/lib/lz4;name=lz4 \
- git://github.com/zephyrproject-rtos/tflite-micro.git;protocol=https;nobranch=1;destsuffix=git/modules/lib/tflite-micro;name=tflite-micro \
- "
+SRC_URI += " \
+ git://github.com/zephyrproject-rtos/mcumgr.git;protocol=https;nobranch=1;destsuffix=git/modules/lib/mcumgr;name=mcumgr \
+ git://github.com/zephyrproject-rtos/TraceRecorderSource.git;protocol=https;nobranch=1;destsuffix=git/modules/debug/TraceRecorder;name=TraceRecorder \
+ git://github.com/zephyrproject-rtos/trusted-firmware-m.git;protocol=https;nobranch=1;destsuffix=git/modules/tee/tfm;name=tfm \
+"

#
# Generated from:
@@ -62,8 +62,4 @@ SRCREV_tfm = "c74be3890c9d975976fde1b1a3b2f5742bec34c0"
ZEPHYR_BRANCH = "v2.7-branch"
PV = "2.7.1+git${SRCPV}"

-SRC_URI:append = " \
- file://0001-cmake-add-yocto-toolchain.patch \
- file://0001-x86-fix-efi-binary-generation-issue-in-cross-compila.patch \
- file://dtc.patch \
-"
+SRC_URI:append = " file://dtc.patch"
diff --git a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-3.0.0.inc b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-3.0.0.inc
new file mode 100644
index 0000000..64594a0
--- /dev/null
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-3.0.0.inc
@@ -0,0 +1,70 @@
+SRCREV_FORMAT = "default_cmsis"
+
+#
+# Generated with:
+#
+# #!/usr/bin/python3
+#
+# import yaml
+# import sys
+#
+# if __name__ == "__main__":
+# with open(sys.argv[1], "r") as fd:
+# data = yaml.safe_load(fd)
+#
+# for project in data["manifest"]["projects"]:
+# print("SRCREV_{} = \"{}\"".format(project["name"], project["revision"]))
+#
+
+SRCREV_default = "4f8d78ceeb436e82f528511998515f6fc137c6cd"
+SRCREV_canopennode = "1052dae561497bef901f931ef75e117c9224aecd"
+SRCREV_civetweb = "094aeb41bb93e9199d24d665ee43e9e05d6d7b1c"
+SRCREV_cmsis = "b0612c97c1401feeb4160add6462c3627fe90fc7"
+SRCREV_edtt = "1fc2e6f7d2a01a01074456f2ef2ccf1f3df7fac1"
+SRCREV_fatfs = "09a9d913c61dccbb8ff92d8943b452c614ac5292"
+SRCREV_fff = "6ce5ba26486e93d5b7696a3e23f0585932c14b16"
+SRCREV_altera = "23c1c1dd7a0c1cc9a399509d1819375847c95b97"
+SRCREV_atmel = "9f78f520f6cbb997e5b44fe8ab17dd5bf2448095"
+SRCREV_cypress = "81a059f21435bc7e315bccd720da5a9b615bbb50"
+SRCREV_espressif = "bcd7565ffa390d5774dc2fbe71a002faa9a7d082"
+SRCREV_gigadevice = "242a7f4be7a3136606c7a65169775f7ef85ad444"
+SRCREV_infineon = "f1fa8241f8786198ba41155413243de36ed878a5"
+SRCREV_microchip = "870d05e6a64ea9548da6b907058b03c8c9420826"
+SRCREV_nordic = "a42b016d7c7610489f5f8c79773fedc05ba352ee"
+SRCREV_nuvoton = "b4d31f33238713a568e23618845702fadd67386f"
+SRCREV_nxp = "9629f15fd80169cc9669e3fbb1260467c3aeb175"
+SRCREV_openisa = "40d049f69c50b58ea20473bee14cf93f518bf262"
+SRCREV_quicklogic = "b3a66fe6d04d87fd1533a5c8de51d0599fcd08d0"
+SRCREV_rpi_pico = "191f5ba46fda49523cdaaef27583d1c875ba2c36"
+SRCREV_silabs = "be39d4eebeddac6e18e9c0c3ba1b31ad1e82eaed"
+SRCREV_st = "575de9d461aa6f430cf62c58a053675377e700f3"
+SRCREV_stm32 = "300109f80730cb2477bfcc706a6602b9870336b3"
+SRCREV_telink = "ffcfd6282aa213f1dc0848dbca6279b098f6b143"
+SRCREV_ti = "1992a4c536554c4f409c36896eda6abdc414d277"
+SRCREV_xtensa = "0e577021bb66e644afd067cd9f7c71ab11b62b3d"
+SRCREV_libmetal = "f237c9d420a51cc43bc37d744e41191ad613f348"
+SRCREV_littlefs = "33509ed9c3d369cdb9d909cd40c5eea8f64a902c"
+SRCREV_loramac-node = "12019623bbad9eb54fe51066847a7cbd4b4eac57"
+SRCREV_lvgl = "783c1f78c8e39751fe89d0883c8bce7336f55e94"
+SRCREV_lz4 = "8e303c264fc21c2116dc612658003a22e933124d"
+SRCREV_mbedtls = "3e3e58a92de76069730c63e0d524f40fea948a61"
+SRCREV_mcuboot = "89936c338e46f43cb177a8b928cd80b90f3ace8f"
+SRCREV_mipi-sys-t = "d9da086b11cda494d85f4d8a9829f505c2d5e380"
+SRCREV_nanopb = "d148bd26718e4c10414f07a7eb1bd24c62e56c5d"
+SRCREV_net-tools = "f49bd1354616fae4093bf36e5eaee43c51a55127"
+SRCREV_nrf_hw_models = "b8cea37dbdc8fc58cc14b4e19fa850877a9da520"
+SRCREV_open-amp = "cfd050ff38a9d028dc211690b2ec35971128e45e"
+SRCREV_openthread = "b7aa7686d3f4e326bd25abc234b209159977c26d"
+SRCREV_segger = "3a52ab222133193802d3c3b4d21730b9b1f1d2f6"
+SRCREV_sof = "500d77e0ac84ac2c969e0d4b2142cca192e893bc"
+SRCREV_tflite-micro = "9156d050927012da87079064db59d07f03b8baf6"
+SRCREV_tinycbor = "40daca97b478989884bffb5226e9ab73ca54b8c4"
+SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
+SRCREV_TraceRecorderSource = "e8ca3b6a83d19b2fc4738a0d9607190436e5e452"
+SRCREV_trusted-firmware-m = "5d32c3e64b3d589548e881eeeeb37d84944c90af"
+SRCREV_tf-m-tests = "52814181f0fde6d1422fac204d42cde30c62e40e"
+SRCREV_psa-arch-tests = "0aab24602cbef30f6422e7ef1066a8473073e586"
+SRCREV_zscilib = "12bfe3f0a9fcbfe3edab7eabc9678b6c62875d34"
+
+ZEPHYR_BRANCH = "v3.0-branch"
+PV = "3.0.0+git${SRCPV}"
diff --git a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
index 60291ed..9a92ddf 100644
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc
@@ -37,7 +37,6 @@ SRC_URI = "\
git://github.com/zephyrproject-rtos/lvgl.git;protocol=https;nobranch=1;destsuffix=git/modules/lib/gui/lvgl;name=lvgl \
git://github.com/zephyrproject-rtos/mbedtls.git;protocol=https;nobranch=1;destsuffix=git/modules/crypto/mbedtls;name=mbedtls \
git://github.com/zephyrproject-rtos/mcuboot.git;protocol=https;nobranch=1;destsuffix=git/bootloader/mcuboot;name=mcuboot \
- git://github.com/zephyrproject-rtos/mcumgr.git;protocol=https;nobranch=1;destsuffix=git/modules/lib/mcumgr;name=mcumgr \
git://github.com/zephyrproject-rtos/mipi-sys-t.git;protocol=https;nobranch=1;destsuffix=git/modules/debug/mipi-sys-t;name=mipi-sys-t \
git://github.com/zephyrproject-rtos/nanopb.git;protocol=https;nobranch=1;destsuffix=git/modules/lib/nanopb;name=nanopb \
git://github.com/zephyrproject-rtos/net-tools.git;protocol=https;nobranch=1;destsuffix=git/tools/net-tools;name=net-tools \
@@ -48,11 +47,14 @@ SRC_URI = "\
git://github.com/zephyrproject-rtos/sof.git;protocol=https;nobranch=1;destsuffix=git/modules/audio/sof;name=sof \
git://github.com/zephyrproject-rtos/tinycbor.git;protocol=https;nobranch=1;destsuffix=git/modules/lib/tinycbor;name=tinycbor \
git://github.com/zephyrproject-rtos/tinycrypt.git;protocol=https;nobranch=1;destsuffix=git/modules/crypto/tinycrypt;name=tinycrypt \
- git://github.com/zephyrproject-rtos/TraceRecorderSource.git;protocol=https;nobranch=1;destsuffix=git/modules/debug/TraceRecorder;name=TraceRecorder \
- git://github.com/zephyrproject-rtos/trusted-firmware-m.git;protocol=https;nobranch=1;destsuffix=git/modules/tee/tfm;name=tfm \
- "
+ git://github.com/zephyrproject-rtos/hal_telink.git;protocol=https;nobranch=1;destsuffix=git/modules/hal/telink;name=telink \
+ git://github.com/zephyrproject-rtos/lz4.git;protocol=https;nobranch=1;destsuffix=git/modules/lib/lz4;name=lz4 \
+ git://github.com/zephyrproject-rtos/tflite-micro.git;protocol=https;nobranch=1;destsuffix=git/modules/lib/tflite-micro;name=tflite-micro \
+ file://0001-cmake-add-yocto-toolchain.patch \
+ file://0001-x86-fix-efi-binary-generation-issue-in-cross-compila.patch \
+"
S = "${WORKDIR}/git"

# Default to a stable version
-PREFERRED_VERSION_zephyr-kernel ??= "2.7.1"
+PREFERRED_VERSION_zephyr-kernel ??= "3.0.0"
include zephyr-kernel-src-${PREFERRED_VERSION_zephyr-kernel}.inc
--
2.30.1

1021 - 1040 of 57387