date:20220110

Re: [yocto] How to clean the cache for a package?

2022-01-10 Thread Tony He

Thanks a lot. This is root cause. I did not update the SRCREV because
I have not added this SRCREV in my recipe.

Tony

Chen, Qi  于2022年1月11日周二 14:28写道：
>
> In theory, there's no need to run 'bitbake -c clean'. Did you update the 
> SRCREV? It would be easier if you could share some info of your recipe.
>
> Regards,
> Qi
>
> -Original Message-
> From: yocto@lists.yoctoproject.org  On Behalf 
> Of Tony He
> Sent: Tuesday, January 11, 2022 2:12 PM
> To: yocto@lists.yoctoproject.org
> Subject: [yocto] How to clean the cache for a package?
>
> Hi,
>
> I'm new to yocto. I write a reciple for my own package. The source code of 
> package is in my PC and maintained by GIT. When I change the source code of 
> the package, I need to compile this package again with "bitbake -c clean 
> package" and "bitbake -c compile package".
> However, even though I can see the code in the folder 
> downloads/git2/package.git is updated, but bitbake still use the last commit 
> of the git repo to compile. After debugging, I found the old commit ID is 
> stored in build-project/cache/bb_persist_data.sqlite3. Is this normal?
> Is it caused by my own wrong reciple or is there any command to clean the 
> cache for a package? Thank you!
>
> Tony

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55795): https://lists.yoctoproject.org/g/yocto/message/55795
Mute This Topic: https://lists.yoctoproject.org/mt/88343604/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] How to clean the cache for a package?

2022-01-10 Thread Chen Qi

In theory, there's no need to run 'bitbake -c clean'. Did you update the 
SRCREV? It would be easier if you could share some info of your recipe.

Regards,
Qi

-Original Message-
From: yocto@lists.yoctoproject.org  On Behalf Of 
Tony He
Sent: Tuesday, January 11, 2022 2:12 PM
To: yocto@lists.yoctoproject.org
Subject: [yocto] How to clean the cache for a package?

Hi,

I'm new to yocto. I write a reciple for my own package. The source code of 
package is in my PC and maintained by GIT. When I change the source code of the 
package, I need to compile this package again with "bitbake -c clean package" 
and "bitbake -c compile package".
However, even though I can see the code in the folder 
downloads/git2/package.git is updated, but bitbake still use the last commit of 
the git repo to compile. After debugging, I found the old commit ID is stored 
in build-project/cache/bb_persist_data.sqlite3. Is this normal?
Is it caused by my own wrong reciple or is there any command to clean the cache 
for a package? Thank you!

Tony

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55794): https://lists.yoctoproject.org/g/yocto/message/55794
Mute This Topic: https://lists.yoctoproject.org/mt/88343604/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] How to clean the cache for a package?

2022-01-10 Thread Tony He

Hi,

I'm new to yocto. I write a reciple for my own package. The source
code of package is in my PC and maintained by GIT. When I change the
source code of the package, I need to compile this package again with
"bitbake -c clean package" and "bitbake -c compile package".
However, even though I can see the code in the folder
downloads/git2/package.git is updated, but bitbake still use the last
commit of the git repo to compile. After debugging, I found the old
commit ID is stored in build-project/cache/bb_persist_data.sqlite3. Is
this normal?
Is it caused by my own wrong reciple or is there any command to clean
the cache for a package? Thank you!

Tony

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55793): https://lists.yoctoproject.org/g/yocto/message/55793
Mute This Topic: https://lists.yoctoproject.org/mt/88343604/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] M+ & H bugs with Milestone Movements WW02

2022-01-10 Thread Stephen Jolley

All,

YP M+ or high bugs which moved to a new milestone in WW02 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


Medium+

  8191

apply kernel config fragments to arbitrary kernels

randy.macl...@windriver.com

bruce.ashfi...@gmail.com

3.5 M1

3.5 M3


 

  12937

Consistent naming scheme for deployed artifacts

randy.macl...@windriver.com

martin.ja...@gmail.com

3.5 M1

3.5 M3


 

  13051

allow Open Container compliant "images" to be generated from oe images 
(container or not)

randy.macl...@windriver.com

bruce.ashfi...@gmail.com

3.5 M1

3.5 M3


 

  13360

kernel-dev: package full kernel source and headers for reference purposes

randy.macl...@windriver.com

bruce.ashfi...@gmail.com

3.5 M1

3.5 M3


 

  13731

Cross canadian GCC fails to find header files when using tclibc-newlib

randy.macl...@windriver.com

alejan...@enedino.org

3.5 M1

3.5 M3


 

  14303

Result of build is not stored in testresult.json with resulttool

randy.macl...@windriver.com

jay.shen.t...@intel.com

3.5 M1

3.5 M3


 

  14348

Layer dependencies not updated

randy.macl...@windriver.com

bluelightn...@bluelightning.org

3.5 M1

3.5 M3


 

  14357

No PDF and EPUB versions of the manuals available on the website

randy.macl...@windriver.com

mhalst...@linuxfoundation.org

3.5 M1

3.5 M3


 

  14394

Add a banner on the old documentation docs

randy.macl...@windriver.com

mhalst...@linuxfoundation.org

3.5 M1

3.5 M3


 

  14539

Remove vague "BSD" license

randy.macl...@windriver.com

r...@burtonini.com

3.5 M1

3.5 M2


 

  14552

Timeout reported as "ERROR: Exit status is 9" which is not very helpful

randy.macl...@windriver.com

limon.ani...@gmail.com

3.5 M1

3.5 M2


 

  14573

boost doesn't build for armv5

randy.macl...@windriver.com

jon.ma...@arm.com

3.5 M1

3.5 M3

Thanks, 

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com  

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55790): https://lists.yoctoproject.org/g/yocto/message/55790
Mute This Topic: https://lists.yoctoproject.org/mt/88334865/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Enhancements/Bugs closed WW02!

2022-01-10 Thread Stephen Jolley

All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


randy.macl...@windriver.com

4


st...@sakoman.com

1


alexandre.bell...@bootlin.com

1


richard.pur...@linuxfoundation.org

1


jpewhac...@gmail.com

1


Grand Total

8

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55789): https://lists.yoctoproject.org/g/yocto/message/55789
Mute This Topic: https://lists.yoctoproject.org/mt/88334828/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Current high bug count owners for Yocto Project 3.5

2022-01-10 Thread Stephen Jolley

All,

Below is the list as of top 45 bug owners as of the end of WW02 of who have
open medium or higher bugs and enhancements against YP 3.5.   There are 76
possible work days left until the final release candidates for YP 3.5 needs
to be released.


Who

Count


michael.opdenac...@bootlin.com

37


r...@burtonini.com

37


david.re...@windriver.com

22


randy.macl...@windriver.com

22


bruce.ashfi...@gmail.com

16


tim.orl...@konsulko.com

13


trevor.gamb...@windriver.com

12


sakib.sa...@windriver.com

12


richard.pur...@linuxfoundation.org

9


mhalst...@linuxfoundation.org

8


kai.k...@windriver.com

7


bluelightn...@bluelightning.org

6


saul.w...@windriver.com

6


jpewhac...@gmail.com

4


chee.yang@intel.com

4


hongxu@windriver.com

4


pgowda@gmail.com

3


qi.c...@windriver.com

3


jon.ma...@arm.com

3


kiran.surend...@windriver.com

3


raj.k...@gmail.com

2


ms...@mvista.com

2


pokyli...@reliableembeddedsystems.com

2


alexandre.bell...@bootlin.com

2


alejan...@enedino.org

2


mingli...@windriver.com

1


yf...@uwaterloo.ca

1


jonathan.richard...@broadcom.com

1


nicolas.deche...@linaro.org

1


jay.shen.t...@intel.com

1


yi.z...@windriver.com

1


martin.ja...@gmail.com

1


aeh...@gmail.com

1


kexin@windriver.com

1


matthew...@posteo.net

1


thomas.per...@bootlin.com

1


limon.ani...@gmail.com

1


elber...@amazon.com

1


mark.ha...@kernel.crashing.org

1


ticot...@gmail.com

1


shac...@vdoo.com

1


john.kaldas.e...@gmail.com

1


open.sou...@oleksandr-kravchuk.com

1


mostthings...@gmail.com

1


akuster...@gmail.com

1


Grand Total

261

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55788): https://lists.yoctoproject.org/g/yocto/message/55788
Mute This Topic: https://lists.yoctoproject.org/mt/88334697/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2022-01-10 Thread Stephen Jolley

All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 396
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now, "3.4", "3.5, "3.99" and "Future", the more pressing/urgent issues
being in "3.4" and then "3.5".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55787): https://lists.yoctoproject.org/g/yocto/message/55787
Mute This Topic: https://lists.yoctoproject.org/mt/88334666/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Problems switching from busybox-udhcpc to dhcpcd

2022-01-10 Thread Bryan Evenson

All,

I solved my problems.

> -Original Message-
> From: yocto@lists.yoctoproject.org  On
> Behalf Of Bryan Evenson via lists.yoctoproject.org
> Sent: Thursday, January 6, 2022 9:32 AM
> To: yocto@lists.yoctoproject.org
> Subject: [yocto] Problems switching from busybox-udhcpc to dhcpcd
> 
> I have a system that is based off core-image-minimal which uses sysvinit and
> busybox-udhcpc.  I'm trying to switch to dhcpcd because I want to get the
> NTP server list from the local DHCP server; dhcpcd supports this feature and
> busybox-udhcpc does not.  I'm on the dunfell branch.  I think I finally got
> firmware upgrade to work cleanly (with opkg) but I'm having trouble
> triggering dhcpcd.  It doesn't work straight out of the box and I'm looking 
> for
> assistance in how to get dhcpcd started.
> 
> First, here are the recipe changes I made in my custom layer to install dhcpcd
> onto my image and for it to get pulled in on firmware upgrade.
> 1. I added the following to my busybox_%.bbappend:
> 
> Do not install busybox-udcpcd, since we are using dhcpcd
> RRECOMMENDS_${PN} = ""
> 
> 2. I modified my busybox defconfig to unset all the udhcpc related
> configuration features
> 
> 3. I created a dhcpcd_%.bbappend with these contents:
> # Set the package to conflict with busybox-udhcpc
> RCONFLICTS_${PN} = "busybox-udhcpc"
> RREPLACES_${PN} = "busybox-udhcpc"
> 
> # Add configuration settings to enable NTP configuration
> PACKAGECONFIG += " \
>ntp \
>  "
> PACKAGECONFIG[ntp] = "--with-hook=ntp, , , ntp"
> 
> # Include the hook scripts on the system
> EXTRA_OECONF += " \
>  --with-hooks \
> "
> 4. In my init-ifupdown_%.bbappend:
>   a. I added dhcpcd to the RDEPENDS list
>   b. I added a script to start dhcpcd and installed it in the
> ${D}${sysconfdir}/network/if-up directory
> 
> 5. Here is the if-up script (note: I only have one Ethernet port on this 
> device
> which will always be eth0):
> #!/bin/sh
> 
> # Only do this for eth0 and not the loopback interface
> if [ "$IFACE" == "eth0" ]; then
>   # Start the DHCP client
>   dhcpcd -4 -6 -f /etc/dhcpcd.conf "$IFACE"
> fi
> 
> 
> I think I'm close, but the dhcpcd never gets called when the Ethernet
> interface starts up.  As best I can tell from my debugging, I think $IFACE is
> never set whenever my if-up script is called.  I'm not sure why that is,
> because I have a pre-up script that depends on $IFACE that has been working
> for years for me.

First, I was having issue even directly calling dhcpcd from the command line 
with the line I had in my pre-up script.  There have been some updates to the 
dhcpcd recipe in master that affects the file installation locations.  I copied 
the dhcpcd recipe in master and put it in my custom layer.  I could then call 
dhcpcd directly without issue.

Second, I needed to enable the CONFIG_FEATURE_IFUPDOWN_EXTERNAL_DHCP 
configuration parameter in busybox.  The ifup and ifdown applets from Busybox 
were not attempted to call dhcpcd without this set.  Once I got both of these 
fixes in place, I found out that I don't need the if-up script I had created.  
Everything is running fine now.

> 
> Has anyone else made this transition that can offer some more support?  Are
> there some examples floating around on how to start dhcpcd on ifup that I
> am missing?
> 
> Thanks,
> Bryan Evenson

Bryan Evenson

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55786): https://lists.yoctoproject.org/g/yocto/message/55786
Mute This Topic: https://lists.yoctoproject.org/mt/88238321/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-zephyr][PATCH] README.txt: Document generate-zephyr-machine use

2022-01-10 Thread Eilís Ní Fhlannagáin

From: Eilís Ní Fhlannagáin 

This commit just adds some documentation on how to use the machine
generation recipe.

Signed-off-by: Eilís Ní Fhlannagáin 
---
 README.txt | 16 
 1 file changed, 16 insertions(+)

diff --git a/README.txt b/README.txt
index f3dda51..ec860fd 100644
--- a/README.txt
+++ b/README.txt
@@ -105,6 +105,22 @@ or
 $ MACHINE=qemu-nios2 bitbake zephyr-kernel-test-all -c testimage
 
 
+Generating OE Machines based on Zephyr board definitions
+
+We currently have a recipe called generate-zephry-machines which will go 
through
+and attempt to create an OE machine conf file for every board in Zephyr.
+
+This is run via:
+
+MACHINE=qemu-x86 bitbake generate-zephyr-machines
+
+The output is then put in the normal deploy dir. This recipe is really only
+useful for maintainers. There is currently no way to use the Zephyr board 
+definition in a single step build. So if you wish to regenerate those machines,
+you will need to run the above, copy the conf files from the deploy dir to the
+machine conf directory and then run your build. This shouldn't need to happen 
+often.
+
 Contributing
 
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55784): https://lists.yoctoproject.org/g/yocto/message/55784
Mute This Topic: https://lists.yoctoproject.org/mt/88330111/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-zephyr][PATCH] zephyr-kernel: Modify recipes to work with new -DZEPHYR_MODULES

2022-01-10 Thread Eilís Ní Fhlannagáin

From: Eilís Ní Fhlannagáin 

Some of these recipes ended up overriding the ZEPHYR_MODULES we set
elsewhere. As well, zephyr-lvgl tries to apply a patch we already apply.

Signed-off-by: Eilís Ní Fhlannagáin 
---
 .../zephyr-kernel/zephyr-coap-client.bb  |  2 --
 .../zephyr-kernel/zephyr-coap-server.bb  |  2 --
 .../zephyr-kernel/zephyr-echo-client.bb  |  2 --
 .../zephyr-kernel/zephyr-http-client.bb  |  1 -
 .../recipes-kernel/zephyr-kernel/zephyr-lvgl.bb  | 12 +---
 .../zephyr-kernel/zephyr-mqtt-publisher.bb   |  2 --
 .../zephyr-kernel/zephyr-openthread-echo-client.bb   |  3 ---
 .../zephyr-kernel/zephyr-peripheral-esp.bb   |  2 --
 .../zephyr-kernel/zephyr-peripheral-hr.bb|  2 --
 .../zephyr-kernel/zephyr-websocket-client.bb |  2 --
 10 files changed, 1 insertion(+), 29 deletions(-)

diff --git 
a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-coap-client.bb 
b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-coap-client.bb
index 1c79dbe..d7ea837 100644
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-coap-client.bb
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-coap-client.bb
@@ -1,5 +1,3 @@
 include zephyr-sample.inc
 
 ZEPHYR_SRC_DIR = "${S}/samples/net/sockets/coap_client"
-
-ZEPHYR_MODULES:append = "\;${S}/modules/lib/mbedtls"
diff --git 
a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-coap-server.bb 
b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-coap-server.bb
index 7100f96..dece67d 100644
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-coap-server.bb
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-coap-server.bb
@@ -1,5 +1,3 @@
 include zephyr-sample.inc
 
 ZEPHYR_SRC_DIR = "${S}/samples/net/sockets/coap_server"
-
-ZEPHYR_MODULES:append = "\;${S}/modules/lib/mbedtls"
diff --git 
a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-echo-client.bb 
b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-echo-client.bb
index e7fcaab..53d1ef3 100644
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-echo-client.bb
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-echo-client.bb
@@ -1,5 +1,3 @@
 include zephyr-sample.inc
 
 ZEPHYR_SRC_DIR = "${S}/samples/net/sockets/echo_client"
-
-ZEPHYR_MODULES:append = "\;${S}/modules/lib/mbedtls"
diff --git 
a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-http-client.bb 
b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-http-client.bb
index d06ad37..bf99bbd 100644
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-http-client.bb
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-http-client.bb
@@ -2,4 +2,3 @@ include zephyr-sample.inc
 
 ZEPHYR_SRC_DIR = "${S}/samples/net/sockets/http_client"
 
-ZEPHYR_MODULES:append = "\;${S}/modules/lib/mbedtls"
diff --git a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-lvgl.bb 
b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-lvgl.bb
index 4f08fc7..efe2154 100644
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-lvgl.bb
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-lvgl.bb
@@ -1,18 +1,8 @@
 include zephyr-sample.inc
 
 ZEPHYR_SRC_DIR = "${S}/samples/subsys/display/lvgl"
-ZEPHYR_MODULES:append = 
"\;${S}/modules/lib/gui/lvgl\;${S}/modules/debug/segger"
 
 # TODO Once more machines and displays are supported, add a PACKAGECONFIG.
 EXTRA_OECMAKE:append =" -DSHIELD=adafruit_2_8_tft_touch_v2"
 
-SRC_URI:append = " \
-
file://0001-cmake-added-missing-file-ext-to.patch;patchdir=modules/lib/gui/lvgl 
\
-
git://github.com/zephyrproject-rtos/segger.git;protocol=https;nobranch=1;destsuffix=git/modules/debug/segger;name=segger
 \
-
git://github.com/zephyrproject-rtos/TraceRecorderSource.git;branch=zephyr;protocol=https;destsuffix=git/modules/debug/TraceRecorder;name=TraceRecorderSource
 \
-"
-
-SRCREV_segger = "3a52ab222133193802d3c3b4d21730b9b1f1d2f6"
-SRCREV_TraceRecorderSource = "36c577727642457b0db7274298a4b96558374832"
-
-COMATIBLE_MACHINE = "(nrf52840dk-nrf52840)"
+COMPATIBLE_MACHINE = "(nrf52840dk-nrf52840)"
diff --git 
a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb 
b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb
index 02b3c16..c679798 100644
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-mqtt-publisher.bb
@@ -1,5 +1,3 @@
 include zephyr-sample.inc
 
 ZEPHYR_SRC_DIR = "${S}/samples/net/mqtt_publisher"
-
-ZEPHYR_MODULES:append = "\;${S}/modules/lib/mbedtls"
diff --git 
a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-openthread-echo-client.bb
 
b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-openthread-echo-client.bb
index 88922b8..b83c6b3 100644
--- 
a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-openthread-echo-client.bb
+++ 
b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-openthread-echo-client.bb
@@ -2,9 +2,6

[yocto] [meta-zephyr][PATCH] zephyr-kernel-src-2.6.1: Add dtc patch.

2022-01-10 Thread Eilís Ní Fhlannagáin

From: Eilís Ní Fhlannagáin 

fd8bf397792d58280928d23686313a8da810485a should have also applied the
dtc.patch to the 2.6.1 kernel. This commits applies it, so both 2.7.1
and 2.6.1 work.

Signed-off-by: Eilís Ní Fhlannagáin 
---
 .../recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.1.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git 
a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.1.inc 
b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.1.inc
index e86a8d9..5306196 100644
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.1.inc
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.1.inc
@@ -50,4 +50,5 @@ SRC_URI:append = " \
 file://0001-cmake-add-yocto-toolchain.patch \
 file://0001-x86-fix-efi-binary-generation-issue-in-cross-compila.patch \
 file://arduino-nano-33-ble-storage-partition.patch \
+file://dtc.patch \
 "
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55782): https://lists.yoctoproject.org/g/yocto/message/55782
Mute This Topic: https://lists.yoctoproject.org/mt/88330109/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [meta-zephyr][PATCH] zephyr.bbclass: Remove need for MACHINEOVERRIDES for ZEPHYR_MODULES

2022-01-10 Thread Eilís Ní Fhlannagáin

From: Eilís Ní Fhlannagáin 

This commit removes the need for calling out ZEPHYR_MODULES via
MACHINEOVERRIDES. It uses west list to figure out what ZEPHYR_MODULES
are available and attaches them to -DZEPHYR_MODULES. Additional out of
tree modules may be added via ZEPHYR_EXTRA_MODULES.

Signed-off-by: Eilís Ní Fhlannagáin 
---
 .../conf/machine/include/nrf52.inc|   2 -
 .../machine/include/stm32mp1-cortex-m4.inc|   3 -
 ...xport-an-OpenEmbedded-machine-config.patch | 201 ++
 .../meta/generate-zephyr-machines.bb  |  48 +
 meta-zephyr-core/classes/zephyr.bbclass   |  42 
 meta-zephyr-core/conf/layer.conf  |   2 +
 .../zephyr-kernel/zephyr-kernel-common.inc|  13 +-
 7 files changed, 298 insertions(+), 13 deletions(-)
 create mode 100644 
meta-zephyr-bsp/recipes-meta/meta/files/0001-zephyr-Export-an-OpenEmbedded-machine-config.patch
 create mode 100644 
meta-zephyr-bsp/recipes-meta/meta/generate-zephyr-machines.bb

diff --git a/meta-zephyr-bsp/conf/machine/include/nrf52.inc 
b/meta-zephyr-bsp/conf/machine/include/nrf52.inc
index d22f8bc..4162d3e 100644
--- a/meta-zephyr-bsp/conf/machine/include/nrf52.inc
+++ b/meta-zephyr-bsp/conf/machine/include/nrf52.inc
@@ -5,8 +5,6 @@
 
 require conf/machine/include/tune-cortexm4.inc
 
-MACHINEOVERRIDES =. "nordic:"
-
 TUNE_FEATURES = "armv7m cortexm4"
 
 # Target type for this machine used by Pyocd
diff --git a/meta-zephyr-bsp/conf/machine/include/stm32mp1-cortex-m4.inc 
b/meta-zephyr-bsp/conf/machine/include/stm32mp1-cortex-m4.inc
index b82b02d..0d46620 100644
--- a/meta-zephyr-bsp/conf/machine/include/stm32mp1-cortex-m4.inc
+++ b/meta-zephyr-bsp/conf/machine/include/stm32mp1-cortex-m4.inc
@@ -5,7 +5,4 @@
 
 require conf/machine/include/tune-cortexm4.inc
 
-# Include OpenAMP for communication with Cortex-A7 core of the SoC
-MACHINEOVERRIDES =. "stm32:openamp:"
-
 TUNE_FEATURES = "armv7m cortexm4"
diff --git 
a/meta-zephyr-bsp/recipes-meta/meta/files/0001-zephyr-Export-an-OpenEmbedded-machine-config.patch
 
b/meta-zephyr-bsp/recipes-meta/meta/files/0001-zephyr-Export-an-OpenEmbedded-machine-config.patch
new file mode 100644
index 000..207237e
--- /dev/null
+++ 
b/meta-zephyr-bsp/recipes-meta/meta/files/0001-zephyr-Export-an-OpenEmbedded-machine-config.patch
@@ -0,0 +1,201 @@
+From 412f998467633ab9e8ff0c7cb2ceff1c76c0435c Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Eil=C3=ADs=20N=C3=AD=20Fhlannag=C3=A1in?=
+ 
+Date: Mon, 18 Oct 2021 13:17:38 +0100
+Subject: [PATCH] zephyr: Export an OpenEmbedded machine config
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+This commit abuses cmake to attempt to figure out the OE tune file
+required and automatically generates an OpenEmbedded machine definition.
+
+We're basically abusing the same mechanism zephyr uses to export
+Makefile build information. When using this, you will need to point
+to a layer with a conf/machine in it (most likely oe-core).
+
+For testing purposes, I generate the machine confs like so:
+
+rm -rf build/*;
+for x in `west boards`;
+do
+west build -d build/$x --cmake-only -b $x samples/hello_world -- \
+-DCONFIG_OEMACHINE_EXPORTS=y \
+-DMETA_OE_BASE:STRING="/home/pidge/poky/meta/";
+done
+
+Upstream-Status: Pending
+
+Signed-off-by: Eilís Ní Fhlannagáin 
+---
+ CMakeLists.txt |   6 +
+ Kconfig.zephyr |   5 +
+ cmake/oemachine_exports/CMakeLists.txt | 234 +
+ 3 files changed, 245 insertions(+)
+ create mode 100644 cmake/oemachine_exports/CMakeLists.txt
+
+diff --git a/CMakeLists.txt b/CMakeLists.txt
+index 242e30cd2e..b19a908f03 100644
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -1647,3 +1647,9 @@ add_subdirectory_ifdef(
+   CONFIG_MAKEFILE_EXPORTS
+   cmake/makefile_exports
+   )
++
++# Finally export all build flags from Zephyr
++add_subdirectory_ifdef(
++  CONFIG_OEMACHINE_EXPORTS
++  cmake/oemachine_exports
++  )
+diff --git a/Kconfig.zephyr b/Kconfig.zephyr
+index 42d2d163cf..16eacb4382 100644
+--- a/Kconfig.zephyr
 b/Kconfig.zephyr
+@@ -455,6 +455,11 @@ config MAKEFILE_EXPORTS
+ Generates a file with build information that can be read by
+ third party Makefile-based build systems.
+ 
++config OEMACHINE_EXPORTS
++  bool "Generate machine configs to be used by OpenEmbedded and the Yocto 
Project"
++  help
++Generates a machine configureation for OpenEmbedded and the Yocto 
Project.
++
+ endmenu
+ endmenu
+ 
+diff --git a/cmake/oemachine_exports/CMakeLists.txt 
b/cmake/oemachine_exports/CMakeLists.txt
+new file mode 100644
+index 00..aaf0ced5e8
+--- /dev/null
 b/cmake/oemachine_exports/CMakeLists.txt
+@@ -0,0 +1,126 @@
++# Copyright (c) 2021 Huawei Inc.
++# SPDX-License-Identifier: Apache-2.0
++
++string(REPLACE _ - OE_BOARD ${BOARD})
++if(GCC_M_CPU)
++   string(REPLACE _ - OE_M_CPU ${GCC_M_CPU})
++endif()
++
++zephyr_get_compile_options_for_lang_as_string(C C_com

[yocto] [meta-zephyr][PATCH] meta-zephyr-core/bsp: Restructure into sublayers

2022-01-10 Thread Eilís Ní Fhlannagáin

From: Eilís Ní Fhlannagáin 

This commit restructures meta-zephyr into meta-zephyr-core and
meta-zephyr-bsp. It moves machine definitions into meta-zephyr-bsp
in preparation for adding the autogenerated zephyr machines.

Signed-off-by: Eilís Ní Fhlannagáin 
---
 README.txt|   2 +-
 meta-zephyr-bsp/conf/layer.conf   |  20 +++
 .../conf}/machine/96b-avenger96.conf  |   0
 .../conf}/machine/96b-nitrogen.conf   |   0
 .../conf}/machine/arduino-nano-33-ble.conf|   0
 .../conf}/machine/include/nrf52.inc   |   0
 .../machine/include/stm32mp1-cortex-m4.inc|   0
 .../conf}/machine/include/tune-arc.inc|   0
 .../machine/include/tune-corei7-common.inc|   0
 .../conf}/machine/include/tune-cortexm0.inc   |   0
 .../conf}/machine/include/tune-cortexm3.inc   |   0
 .../conf}/machine/include/tune-cortexm4.inc   |   0
 .../conf}/machine/include/tune-iamcu.inc  |   0
 .../conf}/machine/include/tune-nios2.inc  |   0
 .../conf}/machine/intel-x86-64.conf   |   0
 .../conf}/machine/nrf52840dk-nrf52840.conf|   0
 .../conf}/machine/qemu-cortex-m3.conf |   0
 .../conf}/machine/qemu-nios2.conf |   0
 .../conf}/machine/qemu-x86.conf   |   0
 .../conf}/machine/stm32mp157c-dk2.conf|   0
 COPYING.MIT => meta-zephyr-core/COPYING.MIT   |   0
 meta-zephyr-core/README.txt   | 119 ++
 .../classes}/siteinfo-zephyr.bbclass  |   0
 .../classes}/zephyr-flash-bossac.bbclass  |   0
 .../classes}/zephyr-flash-dfu.bbclass |   0
 .../classes}/zephyr-flash-pyocd.bbclass   |   0
 .../classes}/zephyr-qemuboot.bbclass  |   0
 .../classes}/zephyr.bbclass   |   0
 .../classes}/zephyrtest.bbclass   |   0
 .../conf}/distro/zephyr.conf  |   0
 {conf => meta-zephyr-core/conf}/layer.conf|  12 +-
 .../lib}/oeqa/controllers/__init__.py |   0
 .../oeqa/controllers/zephyrtargetcontrol.py   |   0
 .../lib}/oeqa/runtime/__init__.py |   0
 .../lib}/oeqa/runtime/cases/zephyr.py |   0
 .../lib}/oeqa/utils/qemuzephyrrunner.py   |   0
 .../recipes-core}/newlib/newlib_%.bbappend|   0
 .../binutils/binutils-2.26arc.inc |   0
 .../binutils-cross-canadian_2.26arc.bb|   0
 .../binutils/binutils-cross_2.26arc.bb|   0
 ...e54244cd02bdcf4f1057be3ce96631f35ac3.patch |   0
 .../recipes-devtools-arc}/gcc/gcc-6.x.arc.inc |   0
 .../gcc/gcc-cross-canadian_6.x.arc.bb |   0
 .../gcc/gcc-cross_6.x.arc .bb |   0
 .../gcc/gcc-source_6.x.arc.bb |   0
 .../gcc/libgcc_6.x.arc.bb |   0
 .../gcc/gcc-cross_6.%.bbappend|   0
 .../recipes-devtools}/gcc/libgcc_6.%.bbappend |   0
 .../python/python3-colorama_0.4.4.bb  |  16 +++
 .../python/python3-intelhex_2.3.0.bb  |  12 ++
 .../python/python3-lpc-checksum_2.2.0.bb  |  14 +++
 .../qemu/files/nios2-add-support.patch|   0
 .../recipes-devtools}/qemu/qemu_%.bbappend|   0
 .../0001-cmake-add-yocto-toolchain.patch  |   0
 ...0001-cmake-added-missing-file-ext-to.patch |   0
 ...ry-generation-issue-in-cross-compila.patch |   0
 ...rduino-nano-33-ble-storage-partition.patch |   0
 .../zephyr-kernel/files/dtc.patch |   0
 .../zephyr-kernel/zephyr-blinky.bb|   0
 .../zephyr-kernel/zephyr-coap-client.bb   |   0
 .../zephyr-kernel/zephyr-coap-server.bb   |   0
 .../zephyr-kernel/zephyr-echo-client.bb   |   0
 .../zephyr-kernel/zephyr-hci-uart.bb  |   0
 .../zephyr-kernel/zephyr-helloworld.bb|   0
 .../zephyr-kernel/zephyr-http-client.bb   |   0
 .../zephyr-kernel/zephyr-image.inc|   0
 .../zephyr-kernel/zephyr-kernel-common.inc|   0
 .../zephyr-kernel/zephyr-kernel-src-2.6.1.inc |   0
 .../zephyr-kernel/zephyr-kernel-src-2.7.1.inc |   0
 .../zephyr-kernel/zephyr-kernel-src-dev.inc   |   0
 .../zephyr-kernel/zephyr-kernel-src.bb|   0
 .../zephyr-kernel/zephyr-kernel-src.inc   |   0
 .../zephyr-kernel/zephyr-kernel-test-all.bb   |   0
 .../zephyr-kernel/zephyr-kernel-test.bb   |   0
 .../zephyr-kernel/zephyr-kernel-test.inc  |   0
 .../zephyr-kernel/zephyr-lvgl.bb  |   0
 .../zephyr-kernel/zephyr-mqtt-publisher.bb|   0
 .../zephyr-kernel/zephyr-openamp-rsc-table.bb |   0
 .../zephyr-openthread-echo-client.bb  |   0
 .../zephyr-kernel/zephyr-peripheral-esp.bb|   0
 .../zephyr-kernel/zephyr-peripheral-hr.bb |   0
 .../zephyr-kernel/zephyr-philosophers.bb  |   0
 .../zephyr-kernel/zephyr-sample.inc   |   0
 .../zephyr-kernel/zephyr-websocket-client.bb  |   0
 84 files changed, 188 insertions(+), 7 deletions(-)
 create mode 100644 meta-zephyr-bsp/conf/layer.conf
 rename {conf => meta-zephyr-bsp/conf}/machine/96b-avenger96.conf (100%)
 rename {conf => meta-zephyr-bsp/conf}/machine/96b-nitrogen.conf (1

[yocto] [meta-zephyr][PATCH] zephyr-kernel-src: Add complete zephyr source

2022-01-10 Thread Eilís Ní Fhlannagáin

From: Eilís Ní Fhlannagáin 

Currently meta-zephyr only checks out a subset of the kernel source.
With the addition of being able to generate machine configs from
zephyr source, we need to be able to have the complete source if we
don't want things to break badly.

Signed-off-by: Eilís Ní Fhlannagáin 
---
 .../zephyr-kernel/zephyr-kernel-src-2.6.1.inc | 39 -
 .../zephyr-kernel/zephyr-kernel-src-2.7.1.inc | 57 +--
 .../zephyr-kernel/zephyr-kernel-src.inc   | 41 +++--
 3 files changed, 125 insertions(+), 12 deletions(-)

diff --git 
a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.1.inc 
b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.1.inc
index ce5e067..e86a8d9 100644
--- a/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.1.inc
+++ b/meta-zephyr-core/recipes-kernel/zephyr-kernel/zephyr-kernel-src-2.6.1.inc
@@ -1,14 +1,47 @@
 SRCREV_FORMAT = "default_cmsis"
+SRCREV_default = "c8755e0b46bd9e171fae38adc1c614197b8ac2cd"
 SRCREV_cmsis = "c3bd2094f92d574377f7af2aec147ae181aa5f8e"
-SRCREV_default = "2d6322d74aaac838ead46bfcba0db619cff4b534"
+SRCREV_atmel = "d17b7dd92d209b20bc1e15431d068edc29bf438d"
+SRCREV_altera = "23c1c1dd7a0c1cc9a399509d1819375847c95b97"
+SRCREV_canopennode = "468d350028a975b96563e58344de48281a0ab371"
+SRCREV_civetweb = "e6903b80c09d17cd1a8bb32e40080005558aad29"
+SRCREV_espressif = "22e757632677e3579e6f20bb9955fffb2e1b3e1c"
+SRCREV_fatfs = "1d1fcc725aa1cb3c32f366e0c53d7490d0fe1109"
+SRCREV_cypress = "81a059f21435bc7e315bccd720da5a9b615bbb50"
+SRCREV_infineon = "f1fa8241f8786198ba41155413243de36ed878a5"
+SRCREV_nordic = "574493fe29c79140df4827ab5d4a23df79d03681"
+SRCREV_openisa = "40d049f69c50b58ea20473bee14cf93f518bf262"
+SRCREV_nuvoton = "b4d31f33238713a568e23618845702fadd67386f"
+SRCREV_microchip = "b280eec5d3b1296b231117c1999bcd0269b6ecc4"
+SRCREV_silabs = "be39d4eebeddac6e18e9c0c3ba1b31ad1e82eaed"
+SRCREV_st = "b52fdbf4b62439be9fab9bb4bae9690a42d2fb14"
+SRCREV_stm32 = "f8ff8d25aa0a9e65948040c7b47ec67f3fa300df"
+SRCREV_ti = "3da6fae25fc44ec830fac4a92787b585ff55435e"
 SRCREV_libmetal = "39d049d4ae68e6f6d595fce7de1dcfc1024fb4eb"
+SRCREV_quicklogic = "b3a66fe6d04d87fd1533a5c8de51d0599fcd08d0"
 SRCREV_lvgl = "31acbaa36e9e74ab88ac81e3d21e7f1d00a71136"
 SRCREV_mbedtls = "5765cb7f75a9973ae9232d438e361a9d7bbc49e7"
-SRCREV_nordic = "574493fe29c79140df4827ab5d4a23df79d03681"
+SRCREV_mcuboot = "2fce9769b191411d580bbc65b043956c2ae9307e"
+SRCREV_mcumgr = "5c5055f5a7565f8152d75fcecf07262928b4d56e"
+SRCREV_net-tools = "f49bd1354616fae4093bf36e5eaee43c51a55127"
+SRCREV_nxp = "0d11138724959e1162777d9206f841ccdf64348e"
 SRCREV_open-amp = "6010f0523cbc75f551d9256cf782f173177acdef"
+SRCREV_loramac-node = "2cee5f7295ff0ff804bf06fea5de006bc7cd121e"
 SRCREV_openthread = "385e19da1ae15f27872c2543b97276a42f102ead"
-SRCREV_stm32 = "f8ff8d25aa0a9e65948040c7b47ec67f3fa300df"
+SRCREV_segger = "3a52ab222133193802d3c3b4d21730b9b1f1d2f6"
+SRCREV_sof = "779f28ed465c03899c8a7d4aaf399856f4e51158"
+SRCREV_tinycbor = "40daca97b478989884bffb5226e9ab73ca54b8c4"
 SRCREV_tinycrypt = "3e9a49d2672ec01435ffbf0d788db6d95ef28de0"
+SRCREV_littlefs = "9e4498d1c73009acd84bb36036ee5e2869112a6c"
+SRCREV_mipi-sys-t = "75e671550ac1acb502f315fe4952514dc73f7bfb"
+SRCREV_nrf_hw_models = "a47e326ca772ddd14cc3b9d4ca30a9ab44ecca16"
+SRCREV_TraceRecorder = "5b5f8d7adbf0e93a09087e8f5708f0eebb8b25bf"
+SRCREV_xtensa = "2f04b615cd5ad3a1b8abef33f9bdd10cc1990ed6"
+SRCREV_edtt = "7dd56fc100d79cc45c33d43e7401d1803e26f6e7"
+SRCREV_tfm = "e18b7a9b040b5b5324520388047c9e7d678447e6"
+SRCREV_tfm-mcuboot = "4aa516e7281fc6f9a2dce0b0efda9acc580fa254"
+SRCREV_nanopb = "d148bd26718e4c10414f07a7eb1bd24c62e56c5d"
+SRCREV_tensorflow = "dc70a45a7cc12c25726a32cd91b28be59e7bc596"
 
 ZEPHYR_BRANCH = "v2.6-branch"
 PV = "2.6.1+git${SRCPV}"
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 9d31c69..e090234 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
@@ -1,14 +1,63 @@
 SRCREV_FORMAT = "default_cmsis"
-SRCREV_cmsis = "b0612c97c1401feeb4160add6462c3627fe90fc7"
+
+# 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
 \
+"
+
+#
+# Generated from:
+# west forall -c 'x=$(filename `pwd`); rev=$(git rev-parse HEAD); \
+#  echo SRCREV_$x = \"$rev\"'
+#
+
 SRCREV_default = "e4da3e528088a34a9989f5a50e7ed3149d57de92"
+SRCREV_canopennode

[yocto] [meta-zephyr][PATCH] west: Add west and python dependencies

2022-01-10 Thread Eilís Ní Fhlannagáin

From: Eilís Ní Fhlannagáin 

We will need west for a few things.

First, west knows about all the boards supported, so for automatic
machine generation, we will need to be able to run west boards.

Secondly, I want to get rid of the dependance on MACHINEOVERRIDES in
machine definition files. One of the things that drives me a bit mad
about how we're doing this is effort replication. Zephyr knows what the
machine is, and modules needed and includes. We shouldn't need to
replicate that effort. Future patches will address that through
automatic machine generation.

Signed-off-by: Eilís Ní Fhlannagáin 
---
 .../python/python3-anytree_2.8.0.bb   | 14 
 .../python/python3-breathe_4.31.0.bb  | 17 ++
 .../python/python3-canopen_1.2.1.bb   | 17 ++
 .../python/python3-cbor_1.0.0.bb  | 19 
 .../python/python3-colorama_0.4.4.bb  | 16 --
 .../python/python3-gitlint_0.15.1.bb  | 14 
 .../python/python3-imgtool_1.7.2.bb   | 14 
 .../python/python3-intelhex_2.3.0.bb  | 12 --
 .../python/python3-junithtml_30.0.4.bb| 14 
 .../python/python3-junitparser_2.1.1.bb   | 14 
 .../python/python3-packaging_21.0.bb  | 14 
 .../python/python3-pyelftools_0.27.bb | 14 
 .../python/python3-pygithub_1.55.bb   | 14 
 .../python/python3-pygments_2.10.0.bb | 15 +
 .../recipes-devtools/python/python3-pylink| 11 ++
 .../python/python3-pyocd_0.32.0.bb| 14 
 .../python/python3-pyparsing_2.4.7.bb | 14 
 .../python/python3-sphinx_4.2.0.bb| 14 
 .../recipes-devtools/west/west_0.12.99.bb | 22 +++
 19 files changed, 255 insertions(+), 28 deletions(-)
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-anytree_2.8.0.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-breathe_4.31.0.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-canopen_1.2.1.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-cbor_1.0.0.bb
 delete mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-colorama_0.4.4.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-gitlint_0.15.1.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-imgtool_1.7.2.bb
 delete mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-intelhex_2.3.0.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-junithtml_30.0.4.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-junitparser_2.1.1.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-packaging_21.0.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-pyelftools_0.27.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-pygithub_1.55.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-pygments_2.10.0.bb
 create mode 100644 meta-zephyr-core/recipes-devtools/python/python3-pylink
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-pyocd_0.32.0.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-pyparsing_2.4.7.bb
 create mode 100644 
meta-zephyr-core/recipes-devtools/python/python3-sphinx_4.2.0.bb
 create mode 100644 meta-zephyr-core/recipes-devtools/west/west_0.12.99.bb

diff --git a/meta-zephyr-core/recipes-devtools/python/python3-anytree_2.8.0.bb 
b/meta-zephyr-core/recipes-devtools/python/python3-anytree_2.8.0.bb
new file mode 100644
index 000..a19c998
--- /dev/null
+++ b/meta-zephyr-core/recipes-devtools/python/python3-anytree_2.8.0.bb
@@ -0,0 +1,14 @@
+# SPDX-FileCopyrightText: Huawei Inc.
+# SPDX-License-Identifier: Apache-2.0
+
+SUMMARY = "Python anytree"
+DESCRIPTION = "Powerful and Lightweight Python Tree Data Structure"
+HOMEPAGE = "https://pypi.org/project/anytree";
+LICENSE = "Apache-2.0"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=e3fc50a88d0a364313df4b21ef20c29e"
+
+inherit pypi setuptools3
+
+PYPI_PACKAGE = "anytree"
+SRC_URI[md5sum] = "25ef3e656ad16a2a6b6c187807da7e5f"
+BBCLASSEXTEND = "native nativesdk"
diff --git a/meta-zephyr-core/recipes-devtools/python/python3-breathe_4.31.0.bb 
b/meta-zephyr-core/recipes-devtools/python/python3-breathe_4.31.0.bb
new file mode 100644
index 000..4389d20
--- /dev/null
+++ b/meta-zephyr-core/recipes-devtools/python/python3-breathe_4.31.0.bb
@@ -0,0 +1,17 @@
+# SPDX-FileCopyrightText: Huawei Inc.
+# SPDX-License-Identifier: Apache-2.0
+
+SUMMARY = "Python breathe"
+DESCRIPTION = "Breathe is an extension to reStructuredText and Sphinx to be \
+   able to read and render Doxygen xml output."
+HOMEPAGE = "https://pypi.org/project/breathe";
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=9e49eecf36fc015de7c61a0247d

[yocto] [meta-zephyr][PATCH] Additional machines and removal of MACHINEOVERRIDES

2022-01-10 Thread Eilís Ní Fhlannagáin

From: Eilís Ní Fhlannagáin 

This set of patches relates to what I discussed at 
https://lists.yoctoproject.org/g/yocto/message/55285.

Four major issues (and one minor issue)are dealt with in this series. The first 
is a logical split of the
meta-zephyr layer into a machine BSP layer and a functional core layer.

The second is the removal for the need of MACHINEOVERRIDES as a method of 
telling zephyr it's'-DZEPHYR_MODULES. Zephyr
already knows this, so by abusing west list a bit, we can pull that information 
out and generate the needed config
line to be passed into cmake. Out of tree ZEPHYR_MODULES should be added via 
ZEPHYR_EXTRA_MODULES.

The third major issue is as we're now relying on west to know what modules 
Zephyr needs, we need to checkout the
complete Zephyr source.

The last major issue is that Zephyr knows it's own machine config and I would 
like us to support as many of the Zephyr
machines as possible. As I've yet to find a way to do this at build time, with 
a little abuse of cmake exports we can
generate machine configurations based on what is in Zephyr itself. These have 
obviously not all been tested

In essence, this patch gives us 382 additional machines to add to the 9 that 
already existed. Testing for these new
boards is still being worked out.

Lastly there was a minor issue with the 2.6.1 kernel in that the dtc patch Ross 
created for 2.7.0 (moved to 2.7.1) wasn't
applied which causes 2.6.1 to fail with the same error


Eilís Ní Fhlannagáin (8):
  meta-zephyr-core/bsp: Restructure into sublayers
  west: Add west and python dependencies
  zephyr.bbclass: Remove need for MACHINEOVERRIDES for ZEPHYR_MODULES
  zephyr-kernel-src: Add complete zephyr source
  zephyr-kernel-src-2.6.1: Add dtc patch.
  meta-zephyr-bsp: Add autogenerated machines.
  zephyr-kernel: Modify recipes to work with new -DZEPHYR_MODULES
  README.txt: Document generate-zephyr-machine use

 README.txt|  18 +-
 {conf => meta-zephyr-bsp/conf}/layer.conf |  12 +-
 .../conf/machine/96b-aerocore2.conf   |  22 ++
 .../conf/machine/96b-argonkey.conf|  22 ++
 .../conf}/machine/96b-avenger96.conf  |   0
 .../conf/machine/96b-carbon-nrf51.conf|  22 ++
 meta-zephyr-bsp/conf/machine/96b-carbon.conf  |  22 ++
 .../conf/machine/96b-meerkat96.conf   |  22 ++
 meta-zephyr-bsp/conf/machine/96b-neonkey.conf |  22 ++
 .../conf}/machine/96b-nitrogen.conf   |   0
 .../conf/machine/96b-stm32-sensor-mez.conf|  22 ++
 meta-zephyr-bsp/conf/machine/96b-wistrio.conf |  22 ++
 .../conf/machine/acrn-ehl-crb.conf|  22 ++
 meta-zephyr-bsp/conf/machine/acrn.conf|  22 ++
 .../conf/machine/actinius-icarus-bee-ns.conf  |  22 ++
 .../conf/machine/actinius-icarus-bee.conf |  22 ++
 .../conf/machine/actinius-icarus-ns.conf  |  22 ++
 .../conf/machine/actinius-icarus-som-ns.conf  |  22 ++
 .../conf/machine/actinius-icarus-som.conf |  22 ++
 .../conf/machine/actinius-icarus.conf |  22 ++
 .../adafruit-feather-m0-basic-proto.conf  |  22 ++
 .../machine/adafruit-feather-nrf52840.conf|  22 ++
 .../machine/adafruit-feather-stm32f405.conf   |  22 ++
 .../adafruit-itsybitsy-m4-express.conf|  22 ++
 .../conf/machine/adafruit-trinket-m0.conf |  22 ++
 .../conf/machine/adp-xc7k-ae350.conf  |  22 ++
 .../conf/machine/altera-max10.conf|  22 ++
 meta-zephyr-bsp/conf/machine/arduino-due.conf |  22 ++
 .../conf}/machine/arduino-nano-33-ble.conf|   0
 .../conf/machine/arduino-nano-33-iot.conf |  22 ++
 .../conf/machine/arduino-zero.conf|  22 ++
 .../machine/arty-a7-arm-designstart-m1.conf   |  22 ++
 .../machine/arty-a7-arm-designstart-m3.conf   |  22 ++
 .../conf/machine/atsamd20-xpro.conf   |  22 ++
 .../conf/machine/atsamd21-xpro.conf   |  22 ++
 .../conf/machine/atsame54-xpro.conf   |  22 ++
 .../conf/machine/atsamr21-xpro.conf   |  22 ++
 .../conf/machine/b-l072z-lrwan1.conf  |  22 ++
 .../conf/machine/b-l4s5i-iot01a.conf  |  22 ++
 .../conf/machine/b-u585i-iot02a.conf  |  22 ++
 .../conf/machine/bbc-microbit-v2.conf |  22 ++
 .../conf/machine/bbc-microbit.conf|  22 ++
 meta-zephyr-bsp/conf/machine/bcm958401m2.conf |  22 ++
 .../conf/machine/bcm958402m2-a72.conf |  22 ++
 .../conf/machine/bcm958402m2-m7.conf  |  22 ++
 .../machine/beaglev-starlight-jh7100.conf |  22 ++
 .../conf/machine/bl5340-dvk-cpuapp-ns.conf|  22 ++
 .../conf/machine/bl5340-dvk-cpuapp.conf   |  22 ++
 .../conf/machine/bl5340-dvk-cpunet.conf   |  22 ++
 meta-zephyr-bsp/conf/machine/bl652-dvk.conf   |  22 ++
 meta-zephyr-bsp/conf/machine/bl653-dvk.conf   |  22 ++
 meta-zephyr-bsp/conf/machine/bl654-dvk.conf   |  22 ++
 .../conf/machine/bl654-sensor-board.conf  |  22 ++
 meta-zephyr-bsp/conf/machine/bl654-usb.conf   |  22 ++
 .../conf/machine/black-f407ve.conf|  22 ++
 .../conf/ma

Re: [yocto] hosttools

2022-01-10 Thread Monsees, Steven C (US) via lists.yoctoproject.org

Thank you, this explains/fixes an anomaly I saw while building under Jenkins...

-Original Message-
From: Richard Purdie  
Sent: Monday, January 10, 2022 8:43 AM
To: Monsees, Steven C (US) ; 
yocto@lists.yoctoproject.org
Subject: Re: [yocto] hosttools

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click 
on a link, decrypt/open an attachment, or enable macros.  For further 
information on how to spot phishing, access “Cybersecurity OneSpace Page” and 
report phishing by clicking the button “Report Phishing” on the Outlook toolbar.

On Mon, 2022-01-10 at 13:21 +, Monsees, Steven C (US) via 
lists.yoctoproject.org wrote:
>  
> How does yocto determine the locations/paths to the “hosttools” ?
>  
> Is there precedence order established for locating the “hosttools” ?,  
> and how would one update the search list so as to pick the tool from a 
> different/specific location ?
>  

It uses PATH, just like the shell would. You'd adjust PATH to influence it.

Once it is constructed you have to remove the path to cause it to be 
regenerated.

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55776): https://lists.yoctoproject.org/g/yocto/message/55776
Mute This Topic: https://lists.yoctoproject.org/mt/88322621/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] rebuilding images

2022-01-10 Thread Ivan Riabtsov

Ok, thanks.

пн, 10 янв. 2022 г. в 16:16, Alexander Kanavin :
>
> Do not remove sstate cache, it is there specifically so that you do not have 
> to rebuild all the packages.
>
> Alex
>
> On Mon, 10 Jan 2022 at 14:13, Ivan Riabtsov  wrote:
>>
>> I build the image with the command
>>
>> #bitbake phytec-headless-image
>>
>> then I need to add something to the image and I do it like this
>>
>> #rm -rf tmp sstate-cache deploy
>>
>> and
>>
>> #bitbake phytec-headless-image
>>
>> but this is too long, the question is: what to remove , so as not to
>> rebuild all the packages, but so that the package was added to the
>> image, for example, I modified local.conf, it was like this:
>> IMAGE_INSTALL_append = "mbpoll mosquitto"
>> it became like this
>> IMAGE_INSTALL_append = "mbpoll mosquitto ntp ntpdate rsyslog"
>>
>> 
>>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55775): https://lists.yoctoproject.org/g/yocto/message/55775
Mute This Topic: https://lists.yoctoproject.org/mt/88322460/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] hosttools

2022-01-10 Thread Richard Purdie

On Mon, 2022-01-10 at 13:21 +, Monsees, Steven C (US) via
lists.yoctoproject.org wrote:
>  
> How does yocto determine the locations/paths to the “hosttools” ?
>  
> Is there precedence order established for locating the “hosttools” ?,  and
> how would one update the search list so as to pick the tool from a
> different/specific location ?
>  

It uses PATH, just like the shell would. You'd adjust PATH to influence it.

Once it is constructed you have to remove the path to cause it to be
regenerated.

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55774): https://lists.yoctoproject.org/g/yocto/message/55774
Mute This Topic: https://lists.yoctoproject.org/mt/88322621/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] hosttools

2022-01-10 Thread Monsees, Steven C (US) via lists.yoctoproject.org


How does yocto determine the locations/paths to the "hosttools" ?

Is there precedence order established for locating the "hosttools" ?,  and
how would one update the search list so as to pick the tool from a 
different/specific location ?


Thanks,
Steve

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55773): https://lists.yoctoproject.org/g/yocto/message/55773
Mute This Topic: https://lists.yoctoproject.org/mt/88322621/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] rebuilding images

2022-01-10 Thread Alexander Kanavin

Do not remove sstate cache, it is there specifically so that you do not
have to rebuild all the packages.

Alex

On Mon, 10 Jan 2022 at 14:13, Ivan Riabtsov  wrote:

> I build the image with the command
>
> #bitbake phytec-headless-image
>
> then I need to add something to the image and I do it like this
>
> #rm -rf tmp sstate-cache deploy
>
> and
>
> #bitbake phytec-headless-image
>
> but this is too long, the question is: what to remove , so as not to
> rebuild all the packages, but so that the package was added to the
> image, for example, I modified local.conf, it was like this:
> IMAGE_INSTALL_append = "mbpoll mosquitto"
> it became like this
> IMAGE_INSTALL_append = "mbpoll mosquitto ntp ntpdate rsyslog"
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55772): https://lists.yoctoproject.org/g/yocto/message/55772
Mute This Topic: https://lists.yoctoproject.org/mt/88322460/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] rebuilding images

2022-01-10 Thread Ivan Riabtsov

I build the image with the command

#bitbake phytec-headless-image

then I need to add something to the image and I do it like this

#rm -rf tmp sstate-cache deploy

and

#bitbake phytec-headless-image

but this is too long, the question is: what to remove , so as not to
rebuild all the packages, but so that the package was added to the
image, for example, I modified local.conf, it was like this:
IMAGE_INSTALL_append = "mbpoll mosquitto"
it became like this
IMAGE_INSTALL_append = "mbpoll mosquitto ntp ntpdate rsyslog"

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55771): https://lists.yoctoproject.org/g/yocto/message/55771
Mute This Topic: https://lists.yoctoproject.org/mt/88322460/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-zephyr][RFC][PATCH 0/6] Additional machines and removal of MACHINEOVERRIDES.

2022-01-10 Thread Eilís Ní Fhlannagáin

On Mon, 10 Jan 2022 at 09:36, Saini, Naveen Kumar
 wrote:
>
> Thank you Eilís Ní Fhlannagáin.
>
> I faced failures, when I tried to build few recipes:
>
> (1)  'zephyr-lvgl' with 'nrf52840dk-nrf52840' machine.
>
> Error log:
> abi/zephyr-lvgl/2.7.1+gitAUTOINC+e4da3e5280_b0612c97c1-r0/recipe-sysroot-native/etc/quiltrc
>  push', 0, 'stdout: Applying patch 0001-cmake-added-missing-file-ext-to.patch
> patching file CMakeLists.txt
> Hunk #1 FAILED at 58.
> 1 out of 1 hunk FAILED -- rejects in file CMakeLists.txt
> Patch 0001-cmake-added-missing-file-ext-to.patch can be reverse-applied

This patch is now promoted to zephyr-kernel-src-2.*.1.inc so removing
this from zephyr-lvgl fixes this.

>
> (2) 'zephyr-http-client' with '96b-nitrogen' machine:
> | Merged configuration 
> '/home/saininav/work/development/zephyr-workspace/poky/build-zephyr/tmp-newlib/work/armv7m-yocto-eabi/zephyr-http-client/2.7.1+gitAUTOINC+e4da3e5280_b0612c97c1-r0/git/samples/net/sockets/http_client/prj.conf'
> |
> | error: Aborting due to Kconfig warnings
> |
> | CMake Error at 
> /home/saininav/work/development/zephyr-workspace/poky/build-zephyr/tmp-newlib/work/armv7m-yocto-eabi/zephyr-http-client/2.7.1+gitAUTOINC+e4da3e5280_b0612c97c1-r0/git/cmake/kconfig.cmake:269
>  (message):
> |   command failed with return code: 1
> | Call Stack (most recent call first):
>

Ah, yes. This is caused by having ZEPHYR_MODULES in the sample
recipes. I've removed them from all the samples builds and have each
one building now.



As for python recipes, I'm removing dups that are in meta-python.

And as far as I can tell, the last is documenting the machine
generation recipe. I'll have a new patchset today for you.

-b

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55770): https://lists.yoctoproject.org/g/yocto/message/55770
Mute This Topic: https://lists.yoctoproject.org/mt/88261389/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-zephyr][RFC][PATCH 0/6] Additional machines and removal of MACHINEOVERRIDES.

2022-01-10 Thread Naveen Saini

Thank you Eilís Ní Fhlannagáin.

I faced failures, when I tried to build few recipes:

(1)  'zephyr-lvgl' with 'nrf52840dk-nrf52840' machine.

Error log:
abi/zephyr-lvgl/2.7.1+gitAUTOINC+e4da3e5280_b0612c97c1-r0/recipe-sysroot-native/etc/quiltrc
 push', 0, 'stdout: Applying patch 0001-cmake-added-missing-file-ext-to.patch
patching file CMakeLists.txt
Hunk #1 FAILED at 58.
1 out of 1 hunk FAILED -- rejects in file CMakeLists.txt
Patch 0001-cmake-added-missing-file-ext-to.patch can be reverse-applied

(2) 'zephyr-http-client' with '96b-nitrogen' machine:
| Merged configuration 
'/home/saininav/work/development/zephyr-workspace/poky/build-zephyr/tmp-newlib/work/armv7m-yocto-eabi/zephyr-http-client/2.7.1+gitAUTOINC+e4da3e5280_b0612c97c1-r0/git/samples/net/sockets/http_client/prj.conf'
|
| error: Aborting due to Kconfig warnings
|
| CMake Error at 
/home/saininav/work/development/zephyr-workspace/poky/build-zephyr/tmp-newlib/work/armv7m-yocto-eabi/zephyr-http-client/2.7.1+gitAUTOINC+e4da3e5280_b0612c97c1-r0/git/cmake/kconfig.cmake:269
 (message):
|   command failed with return code: 1
| Call Stack (most recent call first):

Please find more  comments inline..

> -Original Message-
> From: Eilís Ní Fhlannagáin 
> Sent: Friday, January 7, 2022 10:10 PM
> To: pi...@pidge.org; yocto@lists.yoctoproject.org
> Cc: Saini, Naveen Kumar ; Eilís Ní
> Fhlannagáin 
> Subject: [meta-zephyr][RFC][PATCH 0/6] Additional machines and removal of
> MACHINEOVERRIDES.
> 
> From: Eilís Ní Fhlannagáin 
> 
> This set of patches relates to what I discussed at
> https://lists.yoctoproject.org/g/yocto/message/55285.
> 
> Four major issues (and one minor issue)are dealt with in this series. The 
> first
> is a logical split of the
> meta-zephyr layer into a machine BSP layer and a functional core layer.
> 
> The second is the removal for the need of MACHINEOVERRIDES as a method
> of telling zephyr it's'-DZEPHYR_MODULES. Zephyr
> already knows this, so by abusing west list a bit, we can pull that 
> information
> out and generate the needed config
> line to be passed into cmake. Out of tree ZEPHYR_MODULES should be
> added via ZEPHYR_EXTRA_MODULES.
> 
> The third major issue is as we're now relying on west to know what modules
> Zephyr needs, we need to checkout the
> complete Zephyr source.
> 
> The last major issue is that Zephyr knows it's own machine config and I would
> like us to support as many of the Zephyr
> machines as possible. As I've yet to find a way to do this at build time, 
> with a
> little abuse of cmake exports we can
> generate machine configurations based on what is in Zephyr itself. These
> have obviously not all been tested
> 
> In essence, this patch gives us 382 additional machines to add to the 9 that
> already existed. Testing for these new
> boards is still being worked out.

[Naveen] Thanks for working on testing part too. It would be challenge to test 
all (~382) machine configurations !

> 
> Lastly there was a minor issue with the 2.6.1 kernel in that the dtc patch 
> Ross
> created for 2.7.0 (moved to 2.7.1) wasn't
> applied which causes 2.6.1 to fail with the same error
> 
> Eilís Ní Fhlannagáin (6):
>   meta-zephyr-core/bsp: Restructure into sublayers
>   west: Add west and python dependencies
>   zephyr.bbclass: Remove need for MACHINEOVERRIDES for
> ZEPHYR_MODULES
>   zephyr-kernel-src: Add complete zephyr source
>   zephyr-kernel-src-2.6.1: Add dtc patch.
>   meta-zephyr-bsp: Add autogenerated machines.
> 
>  README.txt|   2 +-
>  {conf => meta-zephyr-bsp/conf}/layer.conf |  12 +-
>  .../conf/machine/96b-aerocore2.conf   |  22 ++
>  .../conf/machine/96b-argonkey.conf|  22 ++
>  .../conf}/machine/96b-avenger96.conf  |   0
>  .../conf/machine/96b-carbon-nrf51.conf|  22 ++
>  meta-zephyr-bsp/conf/machine/96b-carbon.conf  |  22 ++
>  .../conf/machine/96b-meerkat96.conf   |  22 ++
>  meta-zephyr-bsp/conf/machine/96b-neonkey.conf |  22 ++
>  .../conf}/machine/96b-nitrogen.conf   |   0
>  .../conf/machine/96b-stm32-sensor-mez.conf|  22 ++
>  meta-zephyr-bsp/conf/machine/96b-wistrio.conf |  22 ++
>  .../conf/machine/acrn-ehl-crb.conf|  22 ++
>  meta-zephyr-bsp/conf/machine/acrn.conf|  22 ++
>  .../conf/machine/actinius-icarus-bee-ns.conf  |  22 ++
>  .../conf/machine/actinius-icarus-bee.conf |  22 ++
>  .../conf/machine/actinius-icarus-ns.conf  |  22 ++
>  .../conf/machine/actinius-icarus-som-ns.conf  |  22 ++
>  .../conf/machine/actinius-icarus-som.conf |  22 ++
>  .../conf/machine/actinius-icarus.conf |  22 ++
>  .../adafruit-feather-m0-basic-proto.conf  |  22 ++
>  .../machine/adafruit-feather-nrf52840.conf|  22 ++
>  .../machine/adafruit-feather-stm32f405.conf   |  22 ++
>  .../adafruit-itsybitsy-m4-express.conf|  22 ++
>  .../conf/machine/adafruit-trinket-m0.conf |  22 ++
>  .../conf/machine/adp-xc7k-ae350.conf  |  22 ++
>  .../conf/mac

Re: [yocto] How to clean the cache for a package?

Re: [yocto] How to clean the cache for a package?

[yocto] How to clean the cache for a package?

[yocto] M+ & H bugs with Milestone Movements WW02

[yocto] Enhancements/Bugs closed WW02!

[yocto] Current high bug count owners for Yocto Project 3.5

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

Re: [yocto] Problems switching from busybox-udhcpc to dhcpcd

[yocto] [meta-zephyr][PATCH] README.txt: Document generate-zephyr-machine use

[yocto] [meta-zephyr][PATCH] zephyr-kernel: Modify recipes to work with new -DZEPHYR_MODULES

[yocto] [meta-zephyr][PATCH] zephyr-kernel-src-2.6.1: Add dtc patch.

[yocto] [meta-zephyr][PATCH] zephyr.bbclass: Remove need for MACHINEOVERRIDES for ZEPHYR_MODULES

[yocto] [meta-zephyr][PATCH] meta-zephyr-core/bsp: Restructure into sublayers

[yocto] [meta-zephyr][PATCH] zephyr-kernel-src: Add complete zephyr source

[yocto] [meta-zephyr][PATCH] west: Add west and python dependencies

[yocto] [meta-zephyr][PATCH] Additional machines and removal of MACHINEOVERRIDES

Re: [yocto] hosttools

Re: [yocto] rebuilding images

Re: [yocto] hosttools

[yocto] hosttools

Re: [yocto] rebuilding images

[yocto] rebuilding images

Re: [yocto] [meta-zephyr][RFC][PATCH 0/6] Additional machines and removal of MACHINEOVERRIDES.

Re: [yocto] [meta-zephyr][RFC][PATCH 0/6] Additional machines and removal of MACHINEOVERRIDES.

24 matches

Site Navigation

Mail list logo

Footer information