Date   

pygame 1.9.1 python3 issue?

Marek Belisko
 

Hi,

I'm trying to add pygame to my image and took a recipe from
https://github.com/openembedded/openembedded/blob/master/recipes/python/python-pygame_1.9.1.bb.
with few tweaks I can build it on dunfell but when trying to use on
board
I'm getting cythos errors. Doesn anybody share updated version which
works with recent poky releases? I tried to pass cmpila phase on 2.0.0
but it seems it's too much for my knowledge ;)

Thanks and BR,

marek

--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


#yocto #zeus #kernel -broken atomic modsset #yocto #zeus #kernel

Monsees, Steven C (US)
 

 

Ok, so I am trying to understand the impact of the following issue seen under our “zeus” based Intel platform build:

 

https://patchwork.kernel.org/project/dri-devel/patch/20190905181834.6234-1-daniel.vetter@.../

 

The patch is currently preventing my image from going down the DRM_CLIENT_CAP_ATOMIC path…

 

I currently have algorithms centered around the GPU dependent on X and this path, and would like to be able to work around this, if possible.

 

My goal was to get our Yocto based platform in line with the current Yocto release, all our original code was done using the “rocko” release. I have now ported our Intel based build to “zeus” with this being our final issue…

 

Questions:

 

(1) If I wanted to rebuild the “zeus” 3.0.4 kernel to add debug code around this issue how would I go about doing this ?

(2)  Under my downloads directory I see linux-5.2.tar.xz is downloaded, tar ball is without the patch, so I am assuming the patch being applied after, correct ?

(3)  I do not see this built under the build tree after I build my Yocto image, Are some components under the builds tree removed after successfully being built ?, and how might I stop them from being deleted for inspection, etc. ?

(4)  When I perform “bitbake -e linux | grep ^T=” I see the following”

ERROR: Nothing PROVIDES 'linux'. Close matches:

  syslinux

  linuxptp

  linux-atm

Was the linux-5.2 package renamed on built or am I looking at the wrong package as my stating point ?

(5)  It appears the patch was added to the kernel (https://github.com/torvalds/linux/tree/master) about a year ago, has the patch been applied to any earlier pre-zeus releases ?

(6)  Will this X11 issue be addressed in future releases, i.e. “gatesgarth”. “hardnott” ?

(7)  It is unclear but would you know about what release they might have broken this path ?

 

Thanks,

Steve

 

 


Re: curl_easy_perform() failed: Couldn't connect to server #linux #yocto

Vijay Rakesh Munganda
 

Hi Khem Raj,

I had checked, but I couldn’t find any such option in .bb file. As I’m to new to Yocto, can you kindly please tell me how to remove man page option.

Thanks & Regards,
Vijay Rakesh

On 15-Dec-2020, at 03:00, Khem Raj <raj.khem@gmail.com> wrote:
On Mon, Dec 14, 2020 at 12:02 AM Vijay Rakesh Munganda
<vijayrakeshmunganda@gmail.com> wrote:

Hi Khem raj,

Regarding zbar, I found the video option was disabled in the .bb file, so I had changed it to --enable-video and ran the build, but the build failed at do_install. Do I Need to make change anything else?

Log:
| /home/bl-docker/rity/bsp/tmp/hosttools/mkdir -p '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/image/usr/bin'
| ./aarch64-poky-linux-libtool --mode=install /home/bl-docker/rity/bsp/tmp/hosttools/install -c zbarcam/zbarcam '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/image/usr/bin'
| /home/bl-docker/rity/bsp/tmp/hosttools/install -c -m 644 ../git/doc/man/zbarcam.1 '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/image/usr/share/man/man1'
| /home/bl-docker/rity/bsp/tmp/hosttools/install: cannot stat '../git/doc/man/zbarcam.1': No such file or directory
| Makefile:2386: recipe for target 'install-man1' failed
| make[3]: *** [install-man1] Error 1
| make[3]: *** Waiting for unfinished jobs....
| aarch64-poky-linux-libtool: warning: 'zbar/libzbar.la' has not been installed in '/usr/lib'
| aarch64-poky-linux-libtool: install: /home/bl-docker/rity/bsp/tmp/hosttools/install -c zbarcam/.libs/zbarcam /home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/image/usr/bin/zbarcam
| make[3]: Leaving directory '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/build'
| Makefile:2850: recipe for target 'install-am' failed
| make[2]: *** [install-am] Error 2
| make[2]: Leaving directory '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/build'
| Makefile:2541: recipe for target 'install-recursive' failed
| make[1]: *** [install-recursive] Error 1
| make[1]: Leaving directory '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/build'
| Makefile:2844: recipe for target 'install' failed
| make: *** [install] Error 2
| WARNING: /home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/temp/run.do_install.15449:1 exit 1 from 'exit 1'
you might want to check if there is a way to disable
building/installing manpages, most of the times you don't need them on
embedded targets.

Thanks & Regards,
Vijay Rakesh.


FW: [yocto] QA notification for completed autobuilder build (yocto-3.3_M1.rc2)

Sangeeta Jain
 

Hello All,

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

======= Summary ========
No new defects are found.
No high milestone defects.

Bugs verified:

BUG id:13997 - [QA 3.2 M2 RC1] failure in ptest : libinput.libinput-test-suite
Verified Fixed.

Existing bugs observed in this release:

BUG id:14051 - [QA 3.2 M3 RC1] failure in ptest : valgrind.drd and valgrind.helgrind
1 ptest passed, 2 ptest failed



======= Bugs ========
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13997
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14051

Thanks,
Sangeeta

-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On
Behalf Of Pokybuild User
Sent: Thursday, 10 December, 2020 12:51 PM
To: yocto@lists.yoctoproject.org
Cc: qa-build-notification@lists.yoctoproject.org
Subject: [yocto] QA notification for completed autobuilder build
(yocto-
3.3_M1.rc2)


A build flagged for QA (yocto-3.3_M1.rc2) was completed on the
autobuilder and is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.3_M1.rc2


Build hash information:

bitbake: 5775d9463ecedf8681cb6c919b240b80fe70f5a3
meta-arm: 2a530c34199e9aaff2bab1ac53d81f112f34647f
meta-gplv2: 6e8e969590a22a729db1ff342de57f2fd5d02d43
meta-intel: 7d79beb5093da8adf0f9b106a33d8e0904a50a48
meta-kernel: e5a0723a3f3dadd880893bccf9bff88a9b46843d
meta-mingw: 352d8b0aa3c7bbd5060a4cc2ebe7c0e964de4879
oecore: a55b01a3a1faf9a52d7edad074c76327f637aaa2
poky: f36484e88d21346357bd1fa1bef6fdcc42bed54a



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



Re: QA notification for completed autobuilder build (yocto-3.3_M1.rc2)

Sangeeta Jain
 

Hello All,

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

======= Summary ========
No new defects are found.
No high milestone defects.

Bugs verified:

BUG id:13997 - [QA 3.2 M2 RC1] failure in ptest : libinput.libinput-test-suite
Verified Fixed.

Existing bugs observed in this release:

BUG id:14051 - [QA 3.2 M3 RC1] failure in ptest : valgrind.drd and valgrind.helgrind
1 ptest passed, 2 ptest failed



======= Bugs ========
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13997
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14051

Thanks,
Sangeeta

-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf
Of Pokybuild User
Sent: Thursday, 10 December, 2020 12:51 PM
To: yocto@lists.yoctoproject.org
Cc: qa-build-notification@lists.yoctoproject.org
Subject: [yocto] QA notification for completed autobuilder build (yocto-
3.3_M1.rc2)


A build flagged for QA (yocto-3.3_M1.rc2) was completed on the autobuilder
and is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.3_M1.rc2


Build hash information:

bitbake: 5775d9463ecedf8681cb6c919b240b80fe70f5a3
meta-arm: 2a530c34199e9aaff2bab1ac53d81f112f34647f
meta-gplv2: 6e8e969590a22a729db1ff342de57f2fd5d02d43
meta-intel: 7d79beb5093da8adf0f9b106a33d8e0904a50a48
meta-kernel: e5a0723a3f3dadd880893bccf9bff88a9b46843d
meta-mingw: 352d8b0aa3c7bbd5060a4cc2ebe7c0e964de4879
oecore: a55b01a3a1faf9a52d7edad074c76327f637aaa2
poky: f36484e88d21346357bd1fa1bef6fdcc42bed54a



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



M+ & H bugs with Milestone Movements WW50

Stephen Jolley
 

All,

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

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

13123

package.PackageTests.test_gdb_hardlink_debug failed

randy.macleod@...

randy.macleod@...

3.3 M1

3.3 M2

 

13802

ltp tests fail with ssh connection lost  error intermittently

randy.macleod@...

sakib.sajal@...

3.3 M1

3.3 M2

 

13935

Intermittent  taskhash mismatch errors on autobuilder

randy.macleod@...

JPEWhacker@...

3.3 M1

3.3 M2

 

13934

Apparent duplication of libtirpc package causes failure in "bitbake linux-yocto -c menuconfig"

randy.macleod@...

hongxu.jia@...

3.1.4

3.1.5

 

13950

Intermittent qemu connection failures during oe-selftest on autobuilder

randy.macleod@...

sakib.sajal@...

3.3 M1

3.3 M2

 

13992

qemumips testimage keeps failing

randy.macleod@...

kamensky@...

3.3 M1

3.3 M2

 

13999

do_packagedata setscene file race

randy.macleod@...

ross@...

3.3 M1

3.3 M2

 

14002

ssh connection failure during stap testing on qemuarm

randy.macleod@...

saul.wold@...

3.3 M1

3.3 M2

 

14010

qemumips-alt systemd boot unit failure on fedora32-ty-1

randy.macleod@...

akuster808@...

3.3 M1

3.3 M2

 

14018

efibootpartition.GenericEFITest.test_boot_efi selftest failed

randy.macleod@...

chee.yang.lee@...

3.3 M1

3.3 M2

 

14041

qemuarm-alt  failed to load rpcbind

randy.macleod@...

kai.kang@...

3.3 M1

3.3 M2

 

14095

signing selftest failure in test_signing_sstate_archive  debina9-ty-2

randy.macleod@...

saul.wold@...

3.3 M1

3.3 M2

 

14090

devtool.DevtoolExtractTests.test_devtool_deploy_target selftest failure

randy.macleod@...

stacy.gaikovaia@...

3.3 M1

3.3 M2

 

14123

Intermittent FileNotFound error on autobuilder oe-selftest-debian

randy.macleod@...

richard.purdie@...

3.3 M1

3.3 M2

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Enhancements/Bugs closed WW50!

Stephen Jolley
 

All,

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

Who

Count

randy.macleod@...

9

anuj.mittal@...

2

steve@...

1

ross@...

1

richard.purdie@...

1

akuster808@...

1

Grand Total

15

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current high bug count owners for Yocto Project 3.3

Stephen Jolley
 

All,

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

Who

Count

richard.purdie@...

36

ross@...

27

david.reyna@...

21

bluelightning@...

19

bruce.ashfield@...

14

timothy.t.orling@...

12

JPEWhacker@...

11

sakib.sajal@...

11

mark.morton@...

11

akuster808@...

10

kai.kang@...

9

trevor.gamblin@...

9

Qi.Chen@...

6

mingli.yu@...

4

stacy.gaikovaia@...

4

hongxu.jia@...

4

idadelm@...

4

yi.zhao@...

4

raj.khem@...

4

randy.macleod@...

4

alejandro@...

3

mostthingsweb@...

3

chee.yang.lee@...

3

saul.wold@...

2

matthewzmd@...

2

jeanmarie.lemetayer@...

2

pokylinux@...

2

jon.mason@...

2

ydirson@...

2

anuj.mittal@...

2

jaewon@...

2

nicolas.dechesne@...

2

aehs29@...

1

apoorvsangal@...

1

kexin.hao@...

1

liezhi.yang@...

1

mhalstead@...

1

dl9pf@...

1

kergoth@...

1

Martin.Jansa@...

1

mark.hatle@...

1

maxime.roussinbelanger@...

1

shachar@...

1

joe.slater@...

1

akuster@...

1

matt.ranostay@...

1

kamensky@...

1

Grand Total

266

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

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 336 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.2”, “3.3, "3.99" and "Future", the more pressing/urgent issues being in "3.2" and then “3.3”.

 

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

 


Re: [meta-tensorflow] maintained?

hongxu
 

On 12/15/20 5:11 AM, Randy MacLeod wrote:
Add Hongxu.

On 2020-12-14 3:03 p.m., Philip Balister wrote:
On 12/14/20 7:56 AM, Marek Belisko wrote:
Hi,

I'm l;booking for a tensorflow recipe and forum that meta-tensorflow
have support for it (also saw that gatesgarth branch is there) but I
cannot build tensorflow + tensorflow seems to be a bit outdated.

Yes, it is a bit dated.
tf-2.x is out and I think that Hongxu has an uprev
underway but I'm not sure when he'll get to finishing it off.

Hongxu?

The upgrading is almost done, I will send them out for review by the end of next week

The new version is 2.4.0 (RC4) which is the newest of upstream

By the way, the build system of tensorflow, bazel will be upgraded to 3.7.1 which is also the newest of upstream

//Hongxu


Anybody know if this layer is maintained? Thanks.
Searching the layer index for tensorflow shows:

http://layers.openembedded.org/layerindex/branch/master/recipes/?q=tensorflow

So the recipe exists in several layers. Looks like it is time to try and
get everyone to work on together on one layer. I ahve a recipe that
mostly works to build the c library part of torch that needs a home.

Philip


Nice, I think a new layer called something like: meta-ai

would be good to have.

../Randy


        
BR,

marek








-- 
# Randy MacLeod
# Wind River Linux



Re: curl_easy_perform() failed: Couldn't connect to server #linux #yocto

Khem Raj
 

On Mon, Dec 14, 2020 at 12:02 AM Vijay Rakesh Munganda
<vijayrakeshmunganda@gmail.com> wrote:

Hi Khem raj,

Regarding zbar, I found the video option was disabled in the .bb file, so I had changed it to --enable-video and ran the build, but the build failed at do_install. Do I Need to make change anything else?

Log:
| /home/bl-docker/rity/bsp/tmp/hosttools/mkdir -p '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/image/usr/bin'
| ./aarch64-poky-linux-libtool --mode=install /home/bl-docker/rity/bsp/tmp/hosttools/install -c zbarcam/zbarcam '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/image/usr/bin'
| /home/bl-docker/rity/bsp/tmp/hosttools/install -c -m 644 ../git/doc/man/zbarcam.1 '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/image/usr/share/man/man1'
| /home/bl-docker/rity/bsp/tmp/hosttools/install: cannot stat '../git/doc/man/zbarcam.1': No such file or directory
| Makefile:2386: recipe for target 'install-man1' failed
| make[3]: *** [install-man1] Error 1
| make[3]: *** Waiting for unfinished jobs....
| aarch64-poky-linux-libtool: warning: 'zbar/libzbar.la' has not been installed in '/usr/lib'
| aarch64-poky-linux-libtool: install: /home/bl-docker/rity/bsp/tmp/hosttools/install -c zbarcam/.libs/zbarcam /home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/image/usr/bin/zbarcam
| make[3]: Leaving directory '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/build'
| Makefile:2850: recipe for target 'install-am' failed
| make[2]: *** [install-am] Error 2
| make[2]: Leaving directory '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/build'
| Makefile:2541: recipe for target 'install-recursive' failed
| make[1]: *** [install-recursive] Error 1
| make[1]: Leaving directory '/home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/build'
| Makefile:2844: recipe for target 'install' failed
| make: *** [install] Error 2
| WARNING: /home/bl-docker/rity/bsp/tmp/work/aarch64-poky-linux/zbar/0.10+gitAUTOINC+67003d2a98-r0/temp/run.do_install.15449:1 exit 1 from 'exit 1'
you might want to check if there is a way to disable
building/installing manpages, most of the times you don't need them on
embedded targets.

Thanks & Regards,
Vijay Rakesh.



Re: [meta-tensorflow] maintained?

Randy MacLeod
 

Add Hongxu.

On 2020-12-14 3:03 p.m., Philip Balister wrote:
On 12/14/20 7:56 AM, Marek Belisko wrote:
Hi,

I'm l;booking for a tensorflow recipe and forum that meta-tensorflow
have support for it (also saw that gatesgarth branch is there) but I
cannot build tensorflow + tensorflow seems to be a bit outdated.

Yes, it is a bit dated.
tf-2.x is out and I think that Hongxu has an uprev
underway but I'm not sure when he'll get to finishing it off.

Hongxu?


Anybody know if this layer is maintained? Thanks.
Searching the layer index for tensorflow shows:

http://layers.openembedded.org/layerindex/branch/master/recipes/?q=tensorflow

So the recipe exists in several layers. Looks like it is time to try and
get everyone to work on together on one layer. I ahve a recipe that
mostly works to build the c library part of torch that needs a home.

Philip


Nice, I think a new layer called something like: meta-ai

would be good to have.

../Randy



BR,

marek









-- 
# Randy MacLeod
# Wind River Linux


Depends loop with UBOOT_SIGN_ENABLE and initramfs

Amr Bekhit
 

Hello,

I'm using Yocto Dunfell and working on building an image for the
Toradex Colibri iMX6 ULL. The main image integrates an initramfs image
into the kernel (my initramfs image recipe is a copy of
core-image-minimal-initramfs but without initramfs-module-install and
initramfs-module-install-efi). As soon as I enable UBOOT_SIGN_ENABLE,
and attempt to build the main image, I get a dependency loop error,
one of which is shown below.

How can I go about debugging and getting to the source of the error?

Thanks.

Dependency loop #1 found:
Task /workdir/build/../layers/meta-precept/recipes-images/images/idh-os-initramfs-image.bb:do_image
(dependent Tasks ['idh-os-initramfs-image.bb:do_rootfs',
'idh-os-initramfs-image.bb:do_image_qa'])
Task /workdir/build/../layers/meta-precept/recipes-images/images/idh-os-initramfs-image.bb:do_image_complete
(dependent Tasks ['idh-os-initramfs-image.bb:do_image',
'idh-os-initramfs-image.bb:do_image_cpio'])
Task /workdir/build/../layers/meta-toradex-nxp/recipes-kernel/linux/linux-toradex_5.4-2.1.x.bb:do_bundle_initramfs
(dependent Tasks ['idh-os-initramfs-image.bb:do_image_complete',
'linux-toradex_5.4-2.1.x.bb:do_install'])
Task /workdir/build/../layers/meta-toradex-nxp/recipes-kernel/linux/linux-toradex_5.4-2.1.x.bb:do_deploy
(dependent Tasks ['depmodwrapper-cross_1.0.bb:do_populate_sysroot',
'linux-toradex_5.4-2.1.x.bb:do_packagedata',
'linux-toradex_5.4-2.1.x.bb:do_bundle_initramfs',
'linux-toradex_5.4-2.1.x.bb:do_assemble_fitimage_initramfs',
'linux-toradex_5.4-2.1.x.bb:do_populate_sysroot'])
Task /workdir/build/../layers/meta-toradex-nxp/recipes-bsp/u-boot/u-boot-toradex_2020.07.bb:do_deploy
(dependent Tasks ['u-boot-toradex_2020.07.bb:do_compile',
'u-boot-toradex_2020.07.bb:do_create_extlinux_config',
'linux-toradex_5.4-2.1.x.bb:do_deploy'])
Task /workdir/build/../layers/meta-toradex-nxp/recipes-bsp/u-boot/u-boot-toradex_2020.07.bb:do_package
(dependent Tasks ['u-boot-toradex_2020.07.bb:do_deploy',
'glibc_2.31.bb:do_packagedata', 'pseudo_git.bb:do_populate_sysroot',
'dwarfsrcfiles.bb:do_populate_sysroot',
'rpm_4.14.2.1.bb:do_populate_sysroot',
'u-boot-toradex_2020.07.bb:do_install',
'gcc-runtime_9.3.bb:do_packagedata'])
Task /workdir/build/../layers/meta-toradex-nxp/recipes-bsp/u-boot/u-boot-toradex_2020.07.bb:do_package_qa
(dependent Tasks ['pseudo_git.bb:do_populate_sysroot',
'binutils-cross_2.34.bb:do_populate_sysroot',
'u-boot-toradex_2020.07.bb:do_package',
'u-boot-toradex_2020.07.bb:do_packagedata'])
Task /workdir/build/../layers/meta-precept/recipes-images/images/idh-os-initramfs-image.bb:do_rootfs
(dependent Tasks ['util-linux_2.35.1.bb:do_populate_lic',
'kmod_git.bb:do_package_qa',
'util-linux_2.35.1.bb:do_package_write_ipk',
'u-boot-toradex_2020.07.bb:do_packagedata',
'm4_1.4.18.bb:do_populate_lic', 'gperf_3.1.bb:do_populate_lic',
'systemd-systemctl-native.bb:do_populate_lic',
'bzip2_1.0.8.bb:do_package_write_ipk',
'libsm_1.2.3.bb:do_packagedata', 'dbus_1.12.16.bb:do_populate_lic',
'gcc-runtime_9.3.bb:do_packagedata',
'unifdef_2.12.bb:do_populate_lic', 'bzip2_1.0.8.bb:do_packagedata',
'wayland-protocols_1.18.imx.bb:do_package_write_ipk',
'python3-setuptools_45.2.0.bb:do_populate_lic',
'libxcrypt_4.4.15.bb:do_populate_lic',
'base-files_3.0.14.bb:do_populate_lic',
'os-release.bb:do_package_write_ipk',
'openssl_1.1.1g.bb:do_packagedata',
'bash-completion_2.10.bb:do_package_write_ipk',
'gettext_0.20.1.bb:do_populate_lic',
'sqlite3_3.31.1.bb:do_populate_lic',
'wayland-protocols_1.18.imx.bb:do_packagedata',
'wayland_1.18.0.bb:do_populate_lic',
'cracklib_2.9.5.bb:do_package_qa',
'acl_2.2.53.bb:do_package_write_ipk', 'acl_2.2.53.bb:do_populate_lic',
'libxkbcommon_0.10.0.bb:do_populate_lic',
'libtirpc_1.2.6.bb:do_package_write_ipk',
'ncurses_6.2.bb:do_package_qa', 'make_4.3.bb:do_populate_lic',
'update-rc.d_0.8.bb:do_populate_lic',
'initramfs-framework_1.0.bb:do_populate_lic',
'run-postinsts_1.0.bb:do_populate_lic',
'libx11_1.6.9.bb:do_package_write_ipk', 'pigz_2.4.bb:do_populate_lic',
'volatile-binds.bb:do_packagedata',
'u-boot-toradex_2020.07.bb:do_populate_lic',
'xtrans_1.4.0.bb:do_populate_lic', 'ncurses_6.2.bb:do_packagedata',
'python3_3.8.2.bb:do_package_qa',
'libgcc-initial_9.3.bb:do_populate_lic',
'wayland_1.18.0.bb:do_packagedata',
'udev-extraconf_1.1.bb:do_packagedata',
'libcap_2.32.bb:do_package_write_ipk',
'expat_2.2.9.bb:do_package_write_ipk',
'python3_3.8.2.bb:do_populate_lic',
'update-rc.d_0.8.bb:do_populate_lic', 'm4_1.4.18.bb:do_package_qa',
'xkeyboard-config_2.28.bb:do_package_write_ipk',
'libpcre2_10.34.bb:do_populate_lic',
'systemd_244.3.bb:do_packagedata',
'systemd-conf_244.3.bb:do_populate_lic',
'idh-os-initramfs-image.bb:do_prepare_recipe_sysroot',
'xorgproto_2019.2.bb:do_packagedata',
'util-linux_2.35.1.bb:do_package_qa',
'libsm_1.2.3.bb:do_populate_lic',
'dbus_1.12.16.bb:do_package_write_ipk',
'cpio_2.13.bb:do_populate_lic', 'dbus_1.12.16.bb:do_package_qa',
'libxdmcp_1.1.3.bb:do_package_write_ipk',
'e2fsprogs_1.45.4.bb:do_package_qa', 'rsync_3.1.3.bb:do_populate_lic',
'bash_5.0.bb:do_populate_lic',
'shadow-securetty_4.6.bb:do_package_qa',
'prelink_git.bb:do_populate_sysroot',
'systemd-serialgetty.bb:do_package_write_ipk',
'xz_5.2.4.bb:do_package_qa', 'gtk-doc_1.32.bb:do_populate_lic',
'readline_8.0.bb:do_package_qa', 'findutils_4.7.0.bb:do_packagedata',
'initramfs-module-setup-live_1.0.bb:do_package_write_ipk',
'wayland_1.18.0.bb:do_package_write_ipk',
'intltool_0.51.0.bb:do_populate_lic', 'dtc_1.6.0.bb:do_populate_lic',
'ca-certificates_20190110.bb:do_packagedata',
'os-release.bb:do_populate_lic', 'update-rc.d_0.8.bb:do_packagedata',
'kmod_git.bb:do_package_write_ipk',
'base-passwd_3.5.29.bb:do_packagedata',
'openssl_1.1.1g.bb:do_package_qa',
'ca-certificates_20190110.bb:do_populate_lic',
'libcap-ng_0.7.10.bb:do_package_write_ipk',
'cmake-native_3.16.5.bb:do_populate_lic',
'bash_5.0.bb:do_package_write_ipk', 'libffi_3.3.bb:do_populate_lic',
'dwarfsrcfiles.bb:do_populate_lic',
'binutils_2.34.bb:do_populate_lic',
'libcap-ng_0.7.10.bb:do_packagedata',
'libpthread-stubs_0.4.bb:do_package_write_ipk',
'ldconfig-native_2.12.1.bb:do_populate_lic',
'libice_1.0.10.bb:do_package_write_ipk',
'coreutils_8.31.bb:do_packagedata',
'findutils_4.7.0.bb:do_package_write_ipk',
'autoconf-archive_2019.01.06.bb:do_package_write_ipk',
'libnsl2_git.bb:do_populate_lic',
'libxkbcommon_0.10.0.bb:do_packagedata',
'shadow-securetty_4.6.bb:do_populate_lic',
'u-boot-toradex_2020.07.bb:do_package_write_ipk',
'update-rc.d_0.8.bb:do_package_qa', 'sqlite3_3.31.1.bb:do_package_qa',
'opkg_0.4.2.bb:do_populate_sysroot', 'shadow_4.8.1.bb:do_package_qa',
'run-postinsts_1.0.bb:do_package_qa',
'util-macros_1.19.2.bb:do_package_write_ipk',
'initramfs-module-setup-live_1.0.bb:do_package_qa',
'libcap_2.32.bb:do_package_qa', 'glibc_2.31.bb:do_package_write_ipk',
'gmp_6.2.0.bb:do_package_qa',
'libxml2_2.9.10.bb:do_package_write_ipk',
'm4-native_1.4.18.bb:do_populate_lic',
'systemd-serialgetty.bb:do_packagedata',
'zlib_1.2.11.bb:do_package_write_ipk',
'pseudo_git.bb:do_populate_sysroot',
'automake_1.16.1.bb:do_populate_lic',
'volatile-binds.bb:do_populate_lic',
'linux-toradex_5.4-2.1.x.bb:do_packagedata',
'volatile-binds.bb:do_package_write_ipk',
'xorgproto_2019.2.bb:do_populate_lic',
're2c_1.0.1.bb:do_populate_lic',
'systemd-compat-units.bb:do_package_qa',
'initramfs-framework_1.0.bb:do_package_write_ipk',
'systemd_244.3.bb:do_package_write_ipk',
'libnsl2_git.bb:do_package_qa',
'bash-completion_2.10.bb:do_populate_lic',
'swig_3.0.12.bb:do_populate_lic', 'gmp_6.2.0.bb:do_populate_lic',
'busybox_1.31.1.bb:do_package_qa',
'initramfs-module-setup-live_1.0.bb:do_populate_lic',
'libcap_2.32.bb:do_populate_lic',
'util-macros_1.19.2.bb:do_packagedata',
'libx11_1.6.9.bb:do_populate_lic',
'systemd-serialgetty.bb:do_populate_lic',
'libxdmcp_1.1.3.bb:do_packagedata',
'coreutils_8.31.bb:do_populate_lic', 'glibc_2.31.bb:do_package_qa',
'ninja_1.10.0.bb:do_populate_lic',
'libtool-native_2.4.6.bb:do_populate_lic',
'libtirpc_1.2.6.bb:do_populate_lic',
'libxcb_1.13.1.bb:do_package_write_ipk',
'libxcb_1.13.1.bb:do_package_qa', 'rpm_4.14.2.1.bb:do_populate_lic',
'python3_3.8.2.bb:do_packagedata', 'libxau_1.0.9.bb:do_package_qa',
'autoconf-archive_2019.01.06.bb:do_populate_lic',
'kmod_git.bb:do_packagedata', 'xtrans_1.4.0.bb:do_packagedata',
'makedevs_1.0.1.bb:do_populate_sysroot',
'gmp_6.2.0.bb:do_package_write_ipk', 'xz_5.2.4.bb:do_packagedata',
'libpam_1.3.1.bb:do_package_qa',
'python3_3.8.2.bb:do_package_write_ipk',
'linux-toradex_5.4-2.1.x.bb:do_package_qa',
'libxkbcommon_0.10.0.bb:do_package_qa',
'libtirpc_1.2.6.bb:do_packagedata', 'expat_2.2.9.bb:do_populate_lic',
'xcb-proto_1.13.bb:do_populate_lic',
'wayland_1.18.0.bb:do_package_qa', 'libpam_1.3.1.bb:do_packagedata',
'busybox_1.31.1.bb:do_packagedata', 'expat_2.2.9.bb:do_packagedata',
'cracklib_2.9.5.bb:do_packagedata',
'libcap-ng_0.7.10.bb:do_populate_lic',
'prelink_git.bb:do_populate_lic', 'libxau_1.0.9.bb:do_populate_lic',
'pigz_2.4.bb:do_populate_sysroot',
'mklibs-native_0.1.44.bb:do_populate_lic',
'bash-completion_2.10.bb:do_packagedata',
'os-release.bb:do_package_qa', 'kmod-native_git.bb:do_populate_lic',
'm4_1.4.18.bb:do_packagedata', 'opkg-utils_0.4.2.bb:do_packagedata',
'xz_5.2.4.bb:do_populate_lic',
'autoconf-archive_2019.01.06.bb:do_packagedata',
'gcc-runtime_9.3.bb:do_populate_lic', 'kbd_2.2.0.bb:do_package_qa',
'xtrans_1.4.0.bb:do_package_qa', 'flex_2.6.4.bb:do_package_qa',
'acl_2.2.53.bb:do_package_qa',
'opkg-utils_0.4.2.bb:do_populate_sysroot',
'libsm_1.2.3.bb:do_package_write_ipk',
'e2fsprogs_1.45.4.bb:do_populate_lic',
'udev-extraconf_1.1.bb:do_package_qa',
'flex_2.6.4.bb:do_populate_lic', 'volatile-binds.bb:do_package_qa',
'bc_1.07.1.bb:do_populate_lic', 'libgcc_9.3.bb:do_package_write_ipk',
'e2fsprogs_1.45.4.bb:do_populate_lic',
'autoconf-archive_2019.01.06.bb:do_package_qa',
'glibc_2.31.bb:do_populate_lic',
'wayland-protocols_1.18.imx.bb:do_package_qa',
'os-release.bb:do_packagedata', 'gawk_5.0.1.bb:do_package_write_ipk',
'xcb-proto_1.13.bb:do_package_qa',
'libpam_1.3.1.bb:do_package_write_ipk',
'opkg-utils_0.4.2.bb:do_package_write_ipk',
'readline_8.0.bb:do_package_write_ipk',
'xorgproto_2019.2.bb:do_package_write_ipk',
'glibc_2.31.bb:do_packagedata', 'libgcc_9.3.bb:do_populate_lic',
'libxslt_1.1.34.bb:do_populate_lic', 'libice_1.0.10.bb:do_package_qa',
'linux-libc-headers_5.4.bb:do_populate_lic',
'coreutils_8.31.bb:do_package_qa',
'base-files_3.0.14.bb:do_package_qa',
'libarchive_3.4.2.bb:do_populate_lic',
'libsolv_0.7.10.bb:do_populate_lic',
'initramfs-framework_1.0.bb:do_packagedata',
'attr_2.4.48.bb:do_package_qa', 'sqlite3_3.31.1.bb:do_populate_lic',
'cracklib_2.9.5.bb:do_populate_lic',
'libxdmcp_1.1.3.bb:do_populate_lic',
'systemd-compat-units.bb:do_packagedata',
'opkg-utils_0.4.2.bb:do_populate_lic',
'zlib_1.2.11.bb:do_populate_lic',
'glib-2.0_2.62.6.bb:do_populate_lic',
'base-passwd_3.5.29.bb:do_package_write_ipk',
'ncurses_6.2.bb:do_populate_lic',
'base-files_3.0.14.bb:do_packagedata',
'libpam_1.3.1.bb:do_populate_lic', 'gawk_5.0.1.bb:do_packagedata',
'autoconf-archive_2019.01.06.bb:do_populate_lic',
'bzip2_1.0.8.bb:do_populate_lic', 'meson_0.53.2.bb:do_populate_lic',
'busybox_1.31.1.bb:do_package_write_ipk',
'bison_3.5.4.bb:do_populate_lic', 'file_5.38.bb:do_populate_lic',
'update-rc.d_0.8.bb:do_populate_sysroot',
'base-passwd_3.5.29.bb:do_package_qa',
'libxdmcp_1.1.3.bb:do_package_qa',
'linux-libc-headers_5.4.bb:do_package_qa',
'libpcre_8.44.bb:do_populate_lic',
'opkg-utils_0.4.2.bb:do_package_qa', 'gmp_6.2.0.bb:do_populate_lic',
'bzip2_1.0.8.bb:do_package_qa', 'opkg-utils_0.4.2.bb:do_populate_lic',
'cracklib_2.9.5.bb:do_populate_lic',
'libice_1.0.10.bb:do_populate_lic', 'kbd_2.2.0.bb:do_populate_lic',
'libusb1_1.0.22.bb:do_populate_lic',
'qemu-native_4.2.0.bb:do_populate_lic',
'libxml2_2.9.10.bb:do_package_qa', 'findutils_4.7.0.bb:do_package_qa',
'coreutils_8.31.bb:do_package_write_ipk',
'linux-libc-headers_5.4.bb:do_packagedata',
'xtrans_1.4.0.bb:do_package_write_ipk',
'libffi_3.3.bb:do_packagedata', 'busybox_1.31.1.bb:do_populate_lic',
'mpfr_4.0.2.bb:do_populate_lic',
'shadow-securetty_4.6.bb:do_package_write_ipk',
'run-postinsts_1.0.bb:do_package_write_ipk',
'run-postinsts_1.0.bb:do_packagedata',
'libnsl2_git.bb:do_packagedata',
'base-passwd_3.5.29.bb:do_populate_lic',
'libnsl2_git.bb:do_package_write_ipk', 'popt_1.16.bb:do_populate_lic',
'depmodwrapper-cross_1.0.bb:do_populate_lic',
'bash_5.0.bb:do_package_qa', 'findutils_4.7.0.bb:do_populate_lic',
'u-boot-tools_2020.01.bb:do_populate_lic',
'libtirpc_1.2.6.bb:do_package_qa',
'base-files_3.0.14.bb:do_package_write_ipk',
'ldconfig-native_2.12.1.bb:do_populate_sysroot',
'readline_8.0.bb:do_populate_lic',
'e2fsprogs_1.45.4.bb:do_package_write_ipk',
'flex_2.6.4.bb:do_package_write_ipk',
'libxcb_1.13.1.bb:do_packagedata',
'libpthread-stubs_0.4.bb:do_populate_lic',
'mklibs-native_0.1.44.bb:do_populate_sysroot',
'xcb-proto_1.13.bb:do_packagedata',
'libtool-cross_2.4.6.bb:do_populate_lic',
'curl_7.69.1.bb:do_populate_lic',
'shadow-sysroot_4.6.bb:do_populate_lic',
'gettext-minimal-native_0.20.1.bb:do_populate_lic',
'lzop_1.04.bb:do_populate_lic', 'unzip_6.0.bb:do_populate_lic',
'libgcc_9.3.bb:do_packagedata', 'perl_5.30.1.bb:do_populate_lic',
'udev-extraconf_1.1.bb:do_populate_lic',
'expat_2.2.9.bb:do_package_qa',
'binutils-cross_2.34.bb:do_populate_lic',
'opkg_0.4.2.bb:do_populate_lic', 'libsm_1.2.3.bb:do_package_qa',
'gcc-runtime_9.3.bb:do_package_qa',
'libxml2_2.9.10.bb:do_packagedata',
'python3_3.8.2.bb:do_populate_lic', 'libx11_1.6.9.bb:do_package_qa',
'dbus_1.12.16.bb:do_packagedata', 'ncurses_6.2.bb:do_populate_lic',
'readline_8.0.bb:do_packagedata',
'libffi_3.3.bb:do_package_write_ipk', 'pseudo_git.bb:do_populate_lic',
'gdbm_1.18.1.bb:do_package_write_ipk',
'libxau_1.0.9.bb:do_package_write_ipk',
'coreutils_8.31.bb:do_populate_lic',
'gnu-config_git.bb:do_populate_lic', 'shadow_4.8.1.bb:do_packagedata',
'shadow_4.8.1.bb:do_populate_lic', 'zlib_1.2.11.bb:do_packagedata',
'util-linux_2.35.1.bb:do_populate_lic',
'gcc-runtime_9.3.bb:do_package_write_ipk',
'debianutils_4.9.1.bb:do_populate_lic',
'm4_1.4.18.bb:do_package_write_ipk',
'libxcrypt_4.4.15.bb:do_package_write_ipk',
'bash-completion_2.10.bb:do_package_qa',
'flex_2.6.4.bb:do_packagedata', 'e2fsprogs_1.45.4.bb:do_packagedata',
'xcb-proto_1.13.bb:do_package_write_ipk',
'util-linux_2.35.1.bb:do_packagedata',
'pkgconfig_git.bb:do_populate_lic',
'kern-tools-native_git.bb:do_populate_lic',
'systemd-compat-units.bb:do_populate_lic',
'ca-certificates_20190110.bb:do_package_qa',
'openssl_1.1.1g.bb:do_populate_lic',
'update-rc.d_0.8.bb:do_package_write_ipk',
'dbus_1.12.16.bb:do_populate_lic', 'attr_2.4.48.bb:do_populate_lic',
'texinfo-dummy-native.bb:do_populate_lic',
'systemd-compat-units.bb:do_package_write_ipk',
'shadow-securetty_4.6.bb:do_packagedata',
'ca-certificates_20190110.bb:do_package_write_ipk',
'acl_2.2.53.bb:do_populate_lic', 'kmod_git.bb:do_populate_lic',
'libxcrypt_4.4.15.bb:do_packagedata',
'initramfs-framework_1.0.bb:do_package_qa',
'libtirpc_1.2.6.bb:do_populate_lic',
'xz_5.2.4.bb:do_package_write_ipk', 'bzip2_1.0.8.bb:do_populate_lic',
'util-macros_1.19.2.bb:do_populate_lic',
'libffi_3.3.bb:do_populate_lic', 'libxml2_2.9.10.bb:do_populate_lic',
'idh-os-initramfs-image.bb:do_packagedata',
'zlib_1.2.11.bb:do_populate_lic', 'gdbm_1.18.1.bb:do_packagedata',
'xkeyboard-config_2.28.bb:do_package_qa',
'flex_2.6.4.bb:do_populate_lic',
'linux-toradex_5.4-2.1.x.bb:do_package_write_ipk',
'util-macros_1.19.2.bb:do_package_qa', 'acl_2.2.53.bb:do_packagedata',
'xkeyboard-config_2.28.bb:do_packagedata',
'attr_2.4.48.bb:do_packagedata', 'kbd_2.2.0.bb:do_packagedata',
'bash_5.0.bb:do_packagedata', 'systemd_244.3.bb:do_package_qa',
'libxml2_2.9.10.bb:do_populate_lic',
'kbd_2.2.0.bb:do_package_write_ipk',
'libcap-ng_0.7.10.bb:do_populate_lic',
'makedevs_1.0.1.bb:do_populate_lic',
'sqlite3_3.31.1.bb:do_packagedata',
'initramfs-module-setup-live_1.0.bb:do_packagedata',
'u-boot-toradex_2020.07.bb:do_package_qa',
'readline_8.0.bb:do_populate_lic', 'expat_2.2.9.bb:do_populate_lic',
'systemd-serialgetty.bb:do_package_qa',
'libpthread-stubs_0.4.bb:do_packagedata',
'attr_2.4.48.bb:do_package_write_ipk', 'libffi_3.3.bb:do_package_qa',
'udev-extraconf_1.1.bb:do_package_write_ipk',
'libice_1.0.10.bb:do_packagedata', 'db_5.3.28.bb:do_populate_lic',
'libmpc_1.1.0.bb:do_populate_lic',
'quilt-native_0.66.bb:do_populate_lic',
'wayland-protocols_1.18.imx.bb:do_populate_lic',
'systemd-conf_244.3.bb:do_packagedata', 'lzo_2.10.bb:do_populate_lic',
'libnsl2_git.bb:do_populate_lic',
'systemd-conf_244.3.bb:do_package_write_ipk',
'gdbm_1.18.1.bb:do_populate_lic',
'shadow_4.8.1.bb:do_package_write_ipk',
'libpthread-stubs_0.4.bb:do_package_qa',
'wayland_1.18.0.bb:do_populate_lic',
'xorgproto_2019.2.bb:do_package_qa',
'libcap-ng_0.7.10.bb:do_package_qa',
'libxkbcommon_0.10.0.bb:do_package_write_ipk',
'gmp_6.2.0.bb:do_packagedata',
'libxml-parser-perl_2.46.bb:do_populate_lic',
'libgcc_9.3.bb:do_package_qa', 'gdbm_1.18.1.bb:do_populate_lic',
'gcc-cross_9.3.bb:do_populate_lic',
'cracklib_2.9.5.bb:do_package_write_ipk',
'openssl_1.1.1g.bb:do_populate_lic', 'xz_5.2.4.bb:do_populate_lic',
'xorgproto_2019.2.bb:do_populate_lic',
'systemd_244.3.bb:do_populate_lic',
'libxcb_1.13.1.bb:do_populate_lic',
'systemd-conf_244.3.bb:do_package_qa',
'gawk_5.0.1.bb:do_populate_lic', 'libcap_2.32.bb:do_packagedata',
'sqlite3_3.31.1.bb:do_package_write_ipk',
'xkeyboard-config_2.28.bb:do_populate_lic',
'elfutils_0.178.bb:do_populate_lic',
'linux-toradex_5.4-2.1.x.bb:do_populate_lic',
'shadow_4.8.1.bb:do_populate_lic',
'libxcrypt_4.4.15.bb:do_package_qa', 'patch_2.7.6.bb:do_populate_lic',
'attr_2.4.48.bb:do_populate_lic', 'gdbm_1.18.1.bb:do_package_qa',
'zlib_1.2.11.bb:do_package_qa',
'openssl_1.1.1g.bb:do_package_write_ipk',
'libx11_1.6.9.bb:do_packagedata', 'autoconf_2.69.bb:do_populate_lic',
'libxau_1.0.9.bb:do_packagedata', 'gawk_5.0.1.bb:do_package_qa',
'linux-libc-headers_5.4.bb:do_package_write_ipk',
'ncurses_6.2.bb:do_package_write_ipk'])


Re: [meta-tensorflow] maintained?

Philip Balister
 

On 12/14/20 7:56 AM, Marek Belisko wrote:
Hi,

I'm l;booking for a tensorflow recipe and forum that meta-tensorflow
have support for it (also saw that gatesgarth branch is there) but I
cannot build tensorflow + tensorflow seems to be a bit outdated.
Anybody know if this layer is maintained? Thanks.
Searching the layer index for tensorflow shows:

http://layers.openembedded.org/layerindex/branch/master/recipes/?q=tensorflow

So the recipe exists in several layers. Looks like it is time to try and
get everyone to work on together on one layer. I ahve a recipe that
mostly works to build the c library part of torch that needs a home.

Philip



BR,

marek





[PATCH yocto-autobuilder-helper] config.json: add mandatory --layers argument to check-layer

Ross Burton
 

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
config.json | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/config.json b/config.json
index 5249d73..aa0de15 100644
--- a/config.json
+++ b/config.json
@@ -758,16 +758,16 @@
"check-layer" : {
"NEEDREPOS" : ["poky", "meta-gplv2", "meta-mingw"],
"step1" : {
- "EXTRACMDS" : ["yocto-check-layer-wrapper ../meta-poky"]
+ "EXTRACMDS" : ["yocto-check-layer-wrapper --layers ../me=
ta-poky"]
},
"step2" : {
- "EXTRACMDS" : ["yocto-check-layer-wrapper ../meta-yocto-=
bsp"]
+ "EXTRACMDS" : ["yocto-check-layer-wrapper --layers ../me=
ta-yocto-bsp"]
},
"step3" : {
- "EXTRACMDS" : ["yocto-check-layer-wrapper ../meta-mingw"=
]
+ "EXTRACMDS" : ["yocto-check-layer-wrapper --layers ../me=
ta-mingw"]
},
"step4" : {
- "EXTRACMDS" : ["yocto-check-layer-wrapper ../meta-gplv2"=
]
+ "EXTRACMDS" : ["yocto-check-layer-wrapper --layers ../me=
ta-gplv2"]
}
},
"meta-mingw" : {
--=20
2.25.1


Re: [meta-tensorflow] maintained?

Armin Kuster
 

On 12/14/20 4:56 AM, Marek Belisko wrote:
Hi,

I'm l;booking for a tensorflow recipe and forum that meta-tensorflow
have support for it (also saw that gatesgarth branch is there) but I
cannot build tensorflow + tensorflow seems to be a bit outdated.
Anybody know if this layer is maintained?
There are two maintainers listed in the maintainer.md file.  You may
want to ping them.

-armin
Thanks.

BR,

marek




[meta-zephyr][PATCH 3/3] conf: machine: add 96boards Avenger96 support

Wojciech Zmuda
 

From: Wojciech Zmuda <wojciech.zmuda@huawei.com>

The board is based on STMicro STM32MP157AAC 2xCortex-A7+2xCortex-M4
system-on-chip.

Add STM32MP1 family machine config. STM32MP1 support depends on
STM32 HAL and OpenAMP for inter-core communication.

This change has been verified with zephyr-philosophers
and zephyr-shell sample applications on by loading Zephyr image
to Cortex-M4 core from Linux using remoteproc framework.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
---
conf/machine/96b-avenger96.conf | 8 ++++++++
conf/machine/include/stm32mp1-cortex-m4.inc | 11 +++++++++++
2 files changed, 19 insertions(+)
create mode 100644 conf/machine/96b-avenger96.conf
create mode 100644 conf/machine/include/stm32mp1-cortex-m4.inc

diff --git a/conf/machine/96b-avenger96.conf b/conf/machine/96b-avenger96.conf
new file mode 100644
index 0000000..7bcfb4a
--- /dev/null
+++ b/conf/machine/96b-avenger96.conf
@@ -0,0 +1,8 @@
+#@TYPE: Machine
+#@NAME: 96b_avenger96
+
+#@DESCRIPTION: Machine configuration for 96Boards Avenger96 Board.
+
+require conf/machine/include/stm32mp1-cortex-m4.inc
+
+ARCH_96b-avenger96 = "arm"
diff --git a/conf/machine/include/stm32mp1-cortex-m4.inc b/conf/machine/include/stm32mp1-cortex-m4.inc
new file mode 100644
index 0000000..b82b02d
--- /dev/null
+++ b/conf/machine/include/stm32mp1-cortex-m4.inc
@@ -0,0 +1,11 @@
+#@TYPE: Machine
+#@NAME: stm32mp1-cortex-m4
+
+#@DESCRIPTION: Machine configuration for Cortex-M4 core of STMicroelectronics STM32MP1 SoC.
+
+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"
--
2.25.1


[meta-zephyr][PATCH 2/3] zephyr-kernel: clone OpenAMP

Wojciech Zmuda
 

From: Wojciech Zmuda <wojciech.zmuda@huawei.com>

OpenAMP is a framework providing software components enabling
development of software applications for AMP systems.
It is downloaded by default by west from two Zephyr Project
repositories based on original OpenAMP repositories:

- open-amp - IPC layer that implements rpmsg communication
between cores,
- libmetal - HAL abstraction layer used by open-amp.

Clone the repositories so they can be used for building images
for boards with multicore chips.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
---
classes/zephyr-kernel-src.bbclass | 4 ++++
recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 1 +
2 files changed, 5 insertions(+)

diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass
index 4e05182..b7fb81d 100644
--- a/classes/zephyr-kernel-src.bbclass
+++ b/classes/zephyr-kernel-src.bbclass
@@ -7,11 +7,15 @@ SRCREV_default = "7a3b253ced7333f5c0269387a7f3ed1dee69739d"
SRCREV_cmsis = "542b2296e6d515b265e25c6b7208e8fea3014f90"
SRCREV_nordic = "d8a6ea9695ddf792bb18bb6035c13b1daac5d79c"
SRCREV_stm32 = "f0e11398128ac9abdff713da5d3035e6c96e9b86"
+SRCREV_open-amp = "de1b85a13032a2de1d8b6695ae5f800b613e739d"
+SRCREV_libmetal = "9d4ee2c3cfd5f49861939447990f3b7d7bf9bf94"

SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.4-branch;name=default \
git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \
git://github.com/zephyrproject-rtos/hal_nordic.git;protocol=https;destsuffix=git/modules/hal/nordic;name=nordic \
git://github.com/zephyrproject-rtos/hal_stm32.git;protocol=https;destsuffix=git/modules/hal/stm32;name=stm32 \
+ git://github.com/zephyrproject-rtos/open-amp.git;protocol=https;destsuffix=git/modules/lib/open-amp;name=open-amp \
+ git://github.com/zephyrproject-rtos/libmetal.git;protocol=https;destsuffix=git/modules/hal/libmetal;name=libmetal \
file://0001-cmake-add-yocto-toolchain.patch \
"

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
index c7c894e..1357c8f 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
@@ -18,6 +18,7 @@ EXTRA_OECMAKE = " -DZEPHYR_BASE=${S} -DZEPHYR_GCC_VARIANT=yocto -DBOARD=${BOARD}
EXTRA_OECMAKE_append_arm = " -DZEPHYR_MODULES=${S}/modules/cmsis"
EXTRA_OECMAKE_append_nordic = "\;${S}/modules/hal/nordic"
EXTRA_OECMAKE_append_stm32 = "\;${S}/modules/hal/stm32"
+EXTRA_OECMAKE_append_openamp = "\;${S}/modules/lib/open-amp\;${S}/modules/hal/libmetal"
export ZEPHYR_BASE="${S}"


--
2.25.1


[meta-zephyr][PATCH 1/3] zephyr-kernel: clone STM32 HAL

Wojciech Zmuda
 

From: Wojciech Zmuda <wojciech.zmuda@huawei.com>

HAL for STM32 chipsets is one of Zephyr subprojects. It is downloaded
by default by west. Clone the HAL repository so it can be used for
building images for boards with STM32 chips.

Signed-off-by: Wojciech Zmuda <wojciech.zmuda@huawei.com>
---
classes/zephyr-kernel-src.bbclass | 2 ++
recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 1 +
2 files changed, 3 insertions(+)

diff --git a/classes/zephyr-kernel-src.bbclass b/classes/zephyr-kernel-src.bbclass
index ea9b30b..4e05182 100644
--- a/classes/zephyr-kernel-src.bbclass
+++ b/classes/zephyr-kernel-src.bbclass
@@ -6,10 +6,12 @@ SRCREV_FORMAT = "default_cmsis"
SRCREV_default = "7a3b253ced7333f5c0269387a7f3ed1dee69739d"
SRCREV_cmsis = "542b2296e6d515b265e25c6b7208e8fea3014f90"
SRCREV_nordic = "d8a6ea9695ddf792bb18bb6035c13b1daac5d79c"
+SRCREV_stm32 = "f0e11398128ac9abdff713da5d3035e6c96e9b86"

SRC_URI = "git://github.com/zephyrproject-rtos/zephyr.git;protocol=https;branch=v2.4-branch;name=default \
git://github.com/zephyrproject-rtos/cmsis.git;protocol=https;destsuffix=git/modules/cmsis;name=cmsis \
git://github.com/zephyrproject-rtos/hal_nordic.git;protocol=https;destsuffix=git/modules/hal/nordic;name=nordic \
+ git://github.com/zephyrproject-rtos/hal_stm32.git;protocol=https;destsuffix=git/modules/hal/stm32;name=stm32 \
file://0001-cmake-add-yocto-toolchain.patch \
"

diff --git a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
index a1f640d..c7c894e 100644
--- a/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
+++ b/recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc
@@ -17,6 +17,7 @@ ZEPHYR_MAKE_OUTPUT = "zephyr.elf"
EXTRA_OECMAKE = " -DZEPHYR_BASE=${S} -DZEPHYR_GCC_VARIANT=yocto -DBOARD=${BOARD} -DARCH=${ARCH} -DCROSS_COMPILE=${CROSS_COMPILE} -DZEPHYR_SYSROOT=${ZEPHYR_SYSROOT} -DZEPHYR_TOOLCHAIN_VARIANT=yocto"
EXTRA_OECMAKE_append_arm = " -DZEPHYR_MODULES=${S}/modules/cmsis"
EXTRA_OECMAKE_append_nordic = "\;${S}/modules/hal/nordic"
+EXTRA_OECMAKE_append_stm32 = "\;${S}/modules/hal/stm32"
export ZEPHYR_BASE="${S}"


--
2.25.1


[meta-zephyr][PATCH 0/3] Add 96Boards Avenger96 support

Wojciech Zmuda
 

From: Wojciech Zmuda <wojciech.zmuda@huawei.com>

This patch set adds support of Avenger96 boards based on
STMicro STM32MP157AAC 2xCortex-A7+2xCortex-M4 SoC.
The support consists of:
- cloning dependencies i.e. STM32 HAL and OpenAMP framework,
- adding STM32MP1 and Avenger96 $MACHINE config files.

Verification:

1. Build an example app for Avenger96:

$ DISTRO=zephyr MACHINE=96b-avenger96 bitbake zephyr-philosophers

2. Please be aware that Avenger96's Cortex-M4 core can be
programmed and got out of reset only by software running
on the Cortex-A7 core, e.g. by U-Boot or Linux. Therefore,
despite the SoC can enter DFU mode, it cannot be used
for programming the M4 firmware. This example uses Linux.

3. Linux has to be built with remoteproc support. This can
be verified with simple dmesg inspection:

root@stm32mp1-av96:~# dmesg | grep remoteproc
[ 2.336231] remoteproc remoteproc0: m4 is available

4. Transfer the example app to the board, e.g. using scp.
The elf is located as usual in build/tmp-newlib/deploy/images/96b-avenger96/.

5. On the board, check the expected location of the fimrware image.
Empty path defaults to /lib/firmware. You can leave them as
they are and copy the Zephyr ELF file to the location pointed
by them or you can echo the new path and image name.

root@stm32mp1-av96:~# cat /sys/module/firmware_class/parameters/path
<empty>

root@stm32mp1-av96:~# cat /sys/class/remoteproc/remoteproc0/firmware
rproc-m4-fw

6. After the image path and name are configured, start the M4 core:

root@stm32mp1-av96:~# echo start > /sys/class/remoteproc/remoteproc0/state
remoteproc remoteproc0: powering up m4
remoteprocroc remoteproc0: Booting fw image rproc-m4-fw, size 591544
rproc-srm-core m4@0:m4_system_resources: bound m4@0:m4_system_resources:m4_led (ops 0xc0be1210)
remoteproc remoteproc0: remote processor m4 is now

7. Firmware output can be inspected with:

root@stm32mp1-av96:~# cat /sys/kernel/debug/remoteproc/remoteproc0/trace0
Philosopher 5 [C:-2] STARVING
Philosopher 3 [P: 0] DROPPED ONE FORK
Philosopher 3 [P: 0] THINKING [ 25 ms ]
Philosopher 2 [P: 1] EATING [ 425 ms ]
Philosopher 3 [P: 0] STARVING
Philosopher 4 [C:-1] STARVING
Philosopher 4 [C:-1] HOLDING ONE FORK
Philosopher 4 [C:-1] EATING [ 800 ms ]
Philosopher 3 [P: 0] HOLDING ONE FORK
Philosopher 2 [P: 1] DROPPED ONE FORK
Philosopher 2 [P: 1] THINKING [ 725 ms ]
Philosopher 1 [P: 2] EATING [ 225 ms ]

Wojciech Zmuda (3):
zephyr-kernel: clone STM32 HAL
zephyr-kernel: clone OpenAMP
conf: machine: add 96boards Avenger96 support

classes/zephyr-kernel-src.bbclass | 6 ++++++
conf/machine/96b-avenger96.conf | 8 ++++++++
conf/machine/include/stm32mp1-cortex-m4.inc | 11 +++++++++++
recipes-kernel/zephyr-kernel/zephyr-kernel-common.inc | 2 ++
4 files changed, 27 insertions(+)
create mode 100644 conf/machine/96b-avenger96.conf
create mode 100644 conf/machine/include/stm32mp1-cortex-m4.inc

--
2.25.1

2181 - 2200 of 53914