xilinx / meta-petalinux

meta-petalinux distro layer supporting Xilinx Tools

meta-petalinux

This layer is a distro layer on supported architectures MicroBlaze, Zynq, ZynqMP and Versal.

Note: Additional information on Xilinx architectures can be found at: https://www.xilinx.com/products/silicon-devices.html

Toolchains

To build standalone toolchains similar to those embedded with the Xilinx xsct tooling:

Use one of the custom machines: aarch32-tc - 32-bit ARM toolchains (various) aarch64-tc - 64-bit ARM toolchains (various) arm-rm-tc - ARM Cortex-R (and various) microblaze-tc - Microblaze toolchains (various)

MACHINE=<machine> DISTRO=xilinx-standalone bitbake meta-xilinx-toolchain

---

Maintainers, Patches/Submissions, Community

Please send any patches, pull requests, comments or questions for this layer to the meta-xilinx mailing list:

[email protected]

When sending patches, please make sure the email subject line includes [meta-petalinux][<BRANCH_NAME>][PATCH] and cc'ing the maintainers.

For more details follow the OE community patch submission guidelines, as described in:

https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

git send-email --to [email protected] *.patch

Note: When creating patches, please use below format. To follow best practice, if you have more than one patch use --cover-letter option while generating the patches. Edit the 0000-cover-letter.patch and change the title and top of the body as appropriate.

Syntax: git format-patch -s --subject "meta-petalinux][<BRANCH_NAME>][PATCH" -1

Example: git format-patch -s --subject "meta-petalinux][rel-v2023.1][PATCH" -1

Maintainers:

Mark Hatle <[email protected]>
Sandeep Gundlupet Raju <[email protected]>
John Toomey <[email protected]>

Dependencies

This layer depends on:

URI: https://git.yoctoproject.org/poky
layers: meta, meta-poky
branch: langdale

URI: https://git.openembedded.org/meta-openembedded
layers: meta-oe, meta-perl, meta-python, meta-filesystems, meta-gnome,
        meta-multimedia, meta-networking, meta-webserver, meta-xfce,
        meta-initramfs.
branch: langdale

URI:
    https://git.yoctoproject.org/meta-xilinx (official version)
    https://github.com/Xilinx/meta-xilinx (development and amd xilinx release)
layers: meta-xilinx-core, meta-xilinx-microblaze, meta-xilinx-bsp,
        meta-xilinx-standalone, meta-xilinx-vendor.
branch: langdale or amd xilinx release version (e.g. rel-v2023.1)

URI:
    https://git.yoctoproject.org/meta-xilinx-tools (official version)
    https://github.com/Xilinx/meta-xilinx-tools (development and amd xilinx release)
branch: langdale or amd xilinx release version (e.g. rel-v2023.1)

URI: https://github.com/Xilinx/meta-jupyter
branch: langdale or amd xilinx release version (e.g. rel-v2023.1)

URI: https://git.yoctoproject.org/meta-mingw
branch: langdale

URI: https://github.com/OpenAMP/meta-openamp
branch: langdale

URI: https://github.com/meta-qt5/meta-qt5
branch: langdale

URI: https://github.com/Xilinx/meta-ros
layers: meta-ros-common, meta-ros2, meta-ros2-humble
branch: amd xilinx release version (e.g. rel-v2023.1)

URI: https://git.yoctoproject.org/meta-security
layers: meta-tpm
branch: langdale

URI: https://github.com/Xilinx/meta-kria
branch: amd xilinx release version (e.g. rel-v2023.1)

URI: https://git.yoctoproject.org/meta-virtualization
branch: langdale

URI: https://github.com/Xilinx/meta-vitis
branch: amd xilinx release version (e.g. rel-v2023.1)

URI: https://github.com/Xilinx/meta-xilinx-tsn
branch: amd xilinx release version (e.g. rel-v2023.1)

URI: https://git.yoctoproject.org/meta-aws
branch: langdale

meta-petalinux's Issues

packagegroup-petalinux-ros doesn't actually include ros2-control

meta-petalinux/recipes-core/packagegroups/packagegroup-petalinux-ros.bb

Line 151 in 5799be3

${ROS_DEMO_PACKAGES} \

See above. This is duplicatively pulling in demos, not ros2-control. Nominally, this would be the fix:

diff --git a/recipes-core/packagegroups/packagegroup-petalinux-ros.bb b/recipes-core/packagegroups/packagegroup-petalinux-ros.bb
index c97813d..b6b15bf 100644
--- a/recipes-core/packagegroups/packagegroup-petalinux-ros.bb
+++ b/recipes-core/packagegroups/packagegroup-petalinux-ros.bb
@@ -148,7 +148,7 @@ RDEPENDS:${PN}-demo:aarch64 = "\
 "
 
 RDEPENDS:${PN}-control:aarch64 = "\
-    ${ROS_DEMO_PACKAGES} \
+    ${ROS_CONTROL_PACKAGES} \
 "
 
 RDEPENDS:${PN}-dev:aarch64 = "\

However, if one is to actually attempt to build the ROS_CONTROL_PACKAGES recipes, the build will fail. Those recipes are these:

SUMMARY:${PN}-control = "ROS_CONTROL_PACKAGES includes ROS control packages"
ROS_CONTROL_PACKAGES = "\
    controller-interface \
    controller-manager \
    controller-manager-msgs \
    hardware-interface \
    ros2-control \
    ros2controlcli \
    ros2-control-test-assets \
    transmission-interface \
"

When I check what content is included for meta-ros from petalinux 2022.2, it is very close to this: https://github.com/ros/meta-ros/tree/honister

So I think the problem is two-fold:

• packagegroup-petalinux-ros purports to pull in ros2-control, but doesn't actually do so; hence there is no CI coverage or visibility into those recipes failing
• AND those recipes do fail to build, as they seem to be broken in meta-ros:honister.

README.md - link to mailing list does not work

The Yocto mailing list URL seems to be wrong, as the link brings just 404.

https://lists.yoctoproject.org/listinfo/meta-xilinx

I.e. that link is now somehow broken.

petalinux matchbox

Hi, I would like to ask about matchbox. I'm using petalinux version 2022.2, I set up matchbox by using petalinux-config -c rootfs command, but after powering up the development board, the matchbox desktop doesn't appear, is it because of something I didn't configure properly?

Gstreamer version discrepancy in rel-2020.1 and rel-2020.2

When checking the bbappends for the gstreamer recipes i realized that the version is set to 1.16.0
However in the gstreamer mirror repos of xilinx itself it says it is release 1.16.1
And on the poky zeus release it is version 1.16.2.
Seems a bit messy. Which version is the one really targeted with the xilinx 2020.1 release?

ERROR: petalinux-user-image-1.0-r0 do_rootfs: The postinstall intercept hook 'update_font_cache' failed

Dear all,

I am getting the following error on Petalinux 2019.1/Ubuntu 18.04 LTS:

ERROR: petalinux-user-image-1.0-r0 do_rootfs: The postinstall intercept hook 'update_font_cache' failed, details in /Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/temp/log.do_rootfs
ERROR: petalinux-user-image-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/temp/log.do_rootfs.20085
ERROR: Task (/Petalinux/Builds/2019.1/ZU4EV/project-spec/meta-plnx-generated/recipes-core/images/petalinux-user-image.bb:do_rootfs) failed with exit code '1'

$ cat (/Petalinux/Builds/2019.1/ZU4EV/project-spec/meta-plnx-generated/recipes-core/images/petalinux-user-image.bb:do_rootfs

NOTE: Running /Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/recipe-sysroot-native/usr/bin/dnf -v --rpmverbosity=debug -y -c /Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/rootfs/etc/yum.repos.d --repofrompath=oe-repo,/Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/oe-rootfs-repo --installroot=/Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/rootfs --setopt=logdir=/Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/temp repoquery --installed --queryformat Package: %{name} %{arch} %{version} %{name}-%{version}-%{release}.%{arch}.rpm
Dependencies:
%{requires}
Recommendations:
%{recommends}
DependenciesEndHere:

NOTE: Installing complementary packages ...
NOTE: Running ['oe-pkgdata-util', '-p', '/Petalinux/Builds/2019.1/ZU4EV/build/tmp/pkgdata/plnx-zynqmp', 'glob', '/tmp/installed-pkgsnbdg5_2o', '']
NOTE: Running intercept scripts:
NOTE: > Executing update_font_cache intercept ...
NOTE: Exit code 1. Output:

• '[' True = False ']'
• qemu-aarch64 -r 3.14 -E LD_LIBRARY_PATH=/Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/rootfs/usr/lib:/Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/rootfs/lib -L /Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/rootfs -E /Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/rootfs/usr/libexec/fc-cache --sysroot=/Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/rootfs --system-only
  usage: qemu-aarch64 [options] program [arguments...]
  Linux CPU emulator (compiled for aarch64 emulation)

Options and associated environment variables:

Argument Env-variable Description
-h print this help
-help
-g port QEMU_GDB wait gdb connection to 'port'
-L path QEMU_LD_PREFIX set the elf interpreter prefix to 'path'
-s size QEMU_STACK_SIZE set the stack size to 'size' bytes
-cpu model QEMU_CPU select CPU (-cpu help for list)
-E var=value QEMU_SET_ENV sets targets environment variable (see below)
-U var QEMU_UNSET_ENV unsets targets environment variable (see below)
-0 argv0 QEMU_ARGV0 forces target process argv[0] to be 'argv0'
-r uname QEMU_UNAME set qemu uname release string to 'uname'
-B address QEMU_GUEST_BASE set guest_base address to 'address'
-R size QEMU_RESERVED_VA reserve 'size' bytes for guest virtual address space
-d item[,...] QEMU_LOG enable logging of specified items (use '-d help' for a list of items)
-dfilter range[,...] QEMU_DFILTER filter logging based on address range
-D logfile QEMU_LOG_FILENAME write logs to 'logfile' (default stderr)
-p pagesize QEMU_PAGESIZE set the host page size to 'pagesize'
-singlestep QEMU_SINGLESTEP run in singlestep mode
-strace QEMU_STRACE log system calls
-seed QEMU_RAND_SEED Seed for pseudo-random number generator
-trace QEMU_TRACE [[enable=]][,events=][,file=]
-version QEMU_VERSION display version information and exit

Defaults:
QEMU_LD_PREFIX = /Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/rootfs
QEMU_STACK_SIZE = 8388608 byte

You can use -E and -U options or the QEMU_SET_ENV and
QEMU_UNSET_ENV environment variables to set and unset
environment variables for the target process.
It is possible to provide several variables by separating them
by commas in getsubopt(3) style. Additionally it is possible to
provide the -E and -U options multiple times.
The following lines are equivalent:
-E var1=val2 -E var2=val2 -U LD_PRELOAD -U LD_DEBUG
-E var1=val2,var2=val2 -U LD_PRELOAD,LD_DEBUG
QEMU_SET_ENV=var1=val2,var2=val2 QEMU_UNSET_ENV=LD_PRELOAD,LD_DEBUG
Note that if you provide several changes to a single variable
the last change will stay in effect.

See https://qemu.org/contribute/report-a-bug for how to report bugs.
More information on the QEMU project at https://qemu.org.

ERROR: The postinstall intercept hook 'update_font_cache' failed, details in /Petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/temp/log.do_rootfs
DEBUG: Python function do_rootfs finished
ERROR: Function failed: do_rootfs

The project compiles fine on Petalinux 2019.1/Ubuntu 16.04 LTS and Petalinux 2019.1 is compatible with Ubuntu 18.04.

Also reported here

ERROR: petalinux-user-image-1.0-r0 do_rootfs: The postinstall intercept hook 'update_pixbuf_cache' failed, details in /data/zu19eg/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/temp/log.do_rootfs

I am getting the following error when running petalinux-build on Petalinux 2019.2 running on Ubuntu 18.04 LTS:
ERROR: petalinux-user-image-1.0-r0 do_rootfs: The postinstall intercept hook 'update_pixbuf_cache' failed, details in /data/zu19eg/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/temp/log.do_rootfs
petalinux-config -c rootfs
configure gdk-pixbuf, but is not OK, How to Fix? Pls answer it , Thanks

load uImage by uboot spl error

I'm using spl to load uImage directly. (boot.bin, uImage, system.dtb)

1. the default uImage address is 0x8000 by default, which will override spl bss, then hang.
2. after changed the uImage address, the kernel says
   : Hit pending asynchronous external abort (FSR=0x00001c06) during first unmask
   and after mount rootfs / exe systemd, it says
   : Unhandled fault: imprecise external abort (0x1c06)"
   system hang.

I don't know where to get help, if error place, sorry for that.

If I use spl to load u-boot.img, and load uImage/system.dtb by u-boot, system can work normally.

bad.txt

petalinux-image-minimal fails for MACHINE=microzed-zynq7

I'm trying to build petalinux minimal image and it fails because of missing microzed-zynq7/system.hdf in external-hdf repo (I am using rel-v2018.3 manifest).

user@11cce7f65e6f:/home/petalinux/build$  MACHINE=microzed-zynq7 bitbake petalinux-image-minimal
Loading cache: 100% |#############################################################################################################################################| Time: 0:00:00
Loaded 3441 entries from dependency cache.
Parsing recipes: 100% |###########################################################################################################################################| Time: 0:00:02
Parsing of 2566 .bb files complete (2565 cached, 1 parsed). 3442 targets, 149 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION           = "1.36.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "arm-xilinx-linux-gnueabi"
MACHINE              = "microzed-zynq7"
DISTRO               = "petalinux"
DISTRO_VERSION       = "2018.3"
TUNE_FEATURES        = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU           = "hard"
meta                 
meta-poky            = "HEAD:3be15ed93e52d797250ad90467760eb1fd7eca56"
meta-perl            
meta-python          
meta-filesystems     
meta-gnome           
meta-multimedia      
meta-networking      
meta-webserver       
meta-xfce            
meta-initramfs       
meta-oe              = "HEAD:83fbd5d5d605de13f47263fab680d910375e1f95"
meta-browser         = "HEAD:c5ff301787ef76eec57ca500ec9d1ccf0f74b488"
meta-qt5             = "HEAD:f7e16aeeaa58cd7cc166f16d8537a8b3627e0397"
meta-xilinx-bsp      
meta-xilinx-contrib  = "HEAD:7922f16dfa5308fb5419a80f513bb07c0384f95e"
meta-xilinx-tools    = "HEAD:b286943d7d468e9ff10b9f9662767e8c71f104d1"
meta-petalinux       = "HEAD:254edec8368c3d30676135365734abe06e596881"
meta-virtualization  = "HEAD:df7b7937b9c91eeea05665c0b69ddcf435cddbcb"
meta-openamp         = "HEAD:fb5fbc77fa5595ed291b886abe9555a91e67d241"

Initialising tasks: 100% |########################################################################################################################################| Time: 0:00:05
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: external-hdf-1.0-r0 do_deploy: Function failed: do_deploy (log file is located at /home/petalinux/build/tmp/work/microzed_zynq7-xilinx-linux-gnueabi/external-hdf/1.0-r0/temp/log.do_deploy.4705)
ERROR: Logfile of failure stored in: /home/petalinux/build/tmp/work/microzed_zynq7-xilinx-linux-gnueabi/external-hdf/1.0-r0/temp/log.do_deploy.4705
Log data follows:
| DEBUG: Executing python function sstate_task_prefunc
| DEBUG: Python function sstate_task_prefunc finished
| DEBUG: Executing shell function do_deploy
| install: cannot stat '/home/petalinux/build/tmp/work/microzed_zynq7-xilinx-linux-gnueabi/external-hdf/1.0-r0/git/microzed-zynq7/system.hdf': No such file or directory
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_deploy (log file is located at /home/petalinux/build/tmp/work/microzed_zynq7-xilinx-linux-gnueabi/external-hdf/1.0-r0/temp/log.do_deploy.4705)
ERROR: Task (/home/petalinux/sources/core/../meta-xilinx-tools/recipes-bsp/hdf/external-hdf.bb:do_deploy) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1584 tasks of which 1580 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory

Summary: 1 task failed:
  /home/petalinux/sources/core/../meta-xilinx-tools/recipes-bsp/hdf/external-hdf.bb:do_deploy
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Looking to the https://github.com/Xilinx/hdf-examples repository it seems that only zedboard-zynq7 is present.

Can you please advise on how to solve this issue?

Menu config does not show external DDR3 controller IP

I am running petalinux-config with attached XSA file (renamed as a ZIP file to upload). I expected the menuconfig will show the DDR3 controller (named - mig_7series_1_1) would show up as an option for Primary memory in following configuration page:

However, I only see the Manual option.
mb_hardware_platform_wrapper.zip

Race condition with do_image_wic and u-boot-xlnx in petalinux/core-image-minimal

If petalinux/core-image-minimal do_image_wic is executed this function depends on u-boot.bin (u-boot-xlnx). This issue occurs with DISTRO=petalinux/poky.

DEBUG: Executing shell function do_image_wic
| INFO: Creating image(s)...
|
| WARNING: bootloader config not specified, using defaults
|
| ERROR: _exec_cmd: install -m 0644 -D [...]/build/tmp/deploy/images/zcu102-zynqmp/u-boot.bin [...]/build/tmp/work/zcu102_zynqmp-xilinx-linux/core-image-minimal/1.0-r0/deploy-core-image-minimal-image-complete/core-image-minimal-zcu102-zynqmp-20180916102735/tmp.wic.n67gi0vv/boot.1/u-boot.bin returned '1' instead of 0
| output: install: cannot stat '[...]/build/tmp/deploy/images/zcu102-zynqmp/u-boot.bin': No such file or directory

Suggested solution/workaround, add following line to local.conf or distro config:
WKS_FILE_DEPENDS="virtual/bootloader"

arduino-toolchain do_fetch failure

recipes-utils/arduino-toolchain/arduino-toolchain_1.0.bb trys to download http://http.us.debian.org/debian/pool/main/e/elfutils/libelf1_0.176-1_arm64.deb but gets a 404 error. It looks like libelf1_0.176-1_arm64.deb is no longer hosted by the debian repository and has been superseded by libelf1_.176-1.1_arm64.deb. Could we get that recipe updated to fetch the working deb along with hashes? Thanks!

ERROR: petalinux-user-image-1.0-r0 do_rootfs: The postinstall intercept hook 'update_icon_cache' failed

Dear all,

I am getting the following error when running petalinux-build on Petalinux 2019.1 running on Ubuntu 18.04 LTS:

ERROR: petalinux-user-image-1.0-r0 do_rootfs: The postinstall intercept hook 'update_icon_cache' failed, details in /media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/temp/log.do_rootfs
ERROR: petalinux-user-image-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/temp/log.do_rootfs.7604
ERROR: Task (/media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/project-spec/meta-plnx-generated/recipes-core/images/petalinux-user-image.bb:do_rootfs) failed with exit code '1'

$ cat /media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/temp/log.do_rootfs

NOTE: Running /media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/recipe-sysroot-native/usr/bin/dnf -v --rpmverbosity=debug -y -c /media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/rootfs/etc/yum.repos.d --repofrompath=oe-repo,/media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/oe-rootfs-repo --installroot=/media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/rootfs --setopt=logdir=/media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/temp repoquery --installed --queryformat Package: %{name} %{arch} %{version} %{name}-%{version}-%{release}.%{arch}.rpm
Dependencies:
%{requires}
Recommendations:
%{recommends}
DependenciesEndHere:

NOTE: Installing complementary packages ...
NOTE: Running ['oe-pkgdata-util', '-p', '/media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/pkgdata/plnx-zynqmp', 'glob', '/tmp/installed-pkgsp2s98wr8', '']
NOTE: Running intercept scripts:
NOTE: > Executing update_icon_cache intercept ...
NOTE: Exit code 127. Output:
/media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/intercept_scripts-c972dfd7f61e41279b1ea6467ddf3eeb0fa368dddd1f641e88cb83712a33f996/update_icon_cache: line 6: /media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/recipe-sysroot-native//gdk-pixbuf-2.0/gdk-pixbuf-query-loaders: No such file or directory

ERROR: The postinstall intercept hook 'update_icon_cache' failed, details in /media/pedro/OS/Xilinx/petalinux/Builds/2019.1/ZU4EV/build/tmp/work/plnx_zynqmp-xilinx-linux/petalinux-user-image/1.0-r0/temp/log.do_rootfs
DEBUG: Python function do_rootfs finished
ERROR: Function failed: do_rootfs

The project compiles fine on Petalinuz 2019.1 running on Ubuntu 16.04 LTS. It is said thon the Petalinux 2019.1 documentation that it is compatible with Ubuntu 18.04 LTS.

Also reported here

Moved Git-Repository tcf-agent

The SRC_URI for the tcf-agent seems to be moved to a different folder:
https://git.eclipse.org/c/tcf/org.eclipse.tcf.agent.git/

meta-petalinux/recipes-devtools/tcf-agent/tcf-agent_%.bbappend

Line 14 in 5d9a1b6

git://git.eclipse.org/gitroot/tcf/org.eclipse.tcf.agent.git;branch=master;protocol=https \

Does anybody know how to patch this in master and in former releases? We're still using 2018.2 and it's obviously moved there as well

PetaLinux v2022.2 bug report: FSBL recipe in `meta-user` doesn't affect the `zynqmp_fsbl.elf`

Some details about my problem: Forum Post

As I can't find other means to report a bug in PetaLinux I'm reporting it here.

What are my steps:

1. Start patch of ZynqMP FSBL by petalinux-devtool modify fsbl
2. Implement changes, commit
3. Build the project with petalinux-build
4. Pack the boot.bin with petalinux-package ...
5. Put the boot.bin into the first partition of the SD Card
6. Boot the system and we see our changes acting in the output
7. Finish the patch via petalinux-devtool finish fsbl <absolute-path-to-project>/project-spec/meta-user (why absolute is required here?)
8. Pack the boot.bin with petalinux-package ... --force
9. Put the boot.bin into the first partition of the SD Card
10. Boot the system and we see just the vanilla default FSBL is running, no our changes

I assume there's bug in PetaLinux or its recipes as I've tried couple times with no success (we have project creation and build process automated in CI as PetaLinux project cannot be easily committed to Git).

I even asked OpenGPT for help, but it didn't suggested anything else that I'm already doing, so a live brain that knows PetaLinux inside out is required to help with this.

Thank you.

Xen: example-simple.cfg file does not work Petalinux 2020.2

Hi,
I'm trying to use Xen on petalinux 2020.2 using the confluence but "Starting simple additional guests" part is not working.
I believe that a "root=" and/or "ramdisk=" argument is missing in the config file.
Please provide additional info and update the example files.
Thanks

Unable to build zynq-generic

After running bitbake zynq-generic I get the following error:

$ bitbake petalinux-image
WARNING: /home/some-user/projects/zynq/../poky/meta/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.12.2.bb: Unable to get checksum for gstreamer1.0-plugins-base SRC_URI entry encodebin-Need-more-buffers-in-output-queue-for-bett.patch: file could not be found
Parsing recipes: 100% |################################################################################################| Time: 0:01:19
Parsing of 2329 .bb files complete (0 cached, 2329 parsed). 3199 targets, 137 skipped, 0 masked, 0 errors.
WARNING: No recipes available for:
  /home/some-user/projects/zynq/layers/meta-petalinux/recipes-bsp/fsbl/fsbl_%.bbappend
  /home/some-user/projects/zynq/layers/meta-petalinux/recipes-devtools/iptraf/iptraf_%.bbappend
  /home/some-user/projects/zynq/layers/meta-petalinux/recipes-devtools/python/python-smartpm_%.bbappend
  /home/some-user/projects/zynq/layers/meta-petalinux/recipes-efl/efl/efl_%.bbappend
  /home/some-user/projects/zynq/layers/meta-petalinux/recipes-extended/images/xen-image-minimal.bbappend
  /home/some-user/projects/zynq/layers/meta-petalinux/recipes-extended/xen/xen_4.8.0.bbappend
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES '${ROOTFS_PKGMANAGE_BOOTSTRAP}' (but /home/some-user/projects/zynq/layers/meta-petalinux/recipes-core/images/petalinux-image.bb RDEPENDS on or otherwise requires it)
NOTE: Runtime target '${ROOTFS_PKGMANAGE_BOOTSTRAP}' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['${ROOTFS_PKGMANAGE_BOOTSTRAP}']
ERROR: Required build target 'petalinux-image' has no buildable providers.
Missing or unbuildable dependency chain was: ['petalinux-image', '${ROOTFS_PKGMANAGE_BOOTSTRAP}']

Summary: There were 2 WARNING messages shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

My bblayrs.conf looks like the following:

# POKY_BBLAYERS_CONF_VERSION is increased each time build/conf/bblayers.conf
# changes incompatibly
POKY_BBLAYERS_CONF_VERSION = "2"


BBPATH = "${TOPDIR}"
BBFILES ?= ""

BBLAYERS ?= " \
    ${TOPDIR}/../poky/meta \
    ${TOPDIR}/../poky/meta-poky \
    ${TOPDIR}/../poky/meta-yocto-bsp \
    ${TOPDIR}/layers/meta-openembedded/meta-perl \
    ${TOPDIR}/layers/meta-openembedded/meta-python \
    ${TOPDIR}/layers/meta-openembedded/meta-filesystems \
    ${TOPDIR}/layers/meta-openembedded/meta-gnome \
    ${TOPDIR}/layers/meta-openembedded/meta-multimedia \
    ${TOPDIR}/layers/meta-openembedded/meta-networking \
    ${TOPDIR}/layers/meta-openembedded/meta-webserver \
    ${TOPDIR}/layers/meta-openembedded/meta-xfce \
    ${TOPDIR}/layers/meta-openembedded/meta-initramfs \
    ${TOPDIR}/layers/meta-openembedded/meta-oe \
    ${TOPDIR}/layers/meta-qt5 \
    ${TOPDIR}/layers/meta-xilinx \
    ${TOPDIR}/layers/meta-petalinux \
    "

MACHINE = "zynq-generic"

LICENSE_FLAGS_WHITELIST += "xilinx"

Is something missing from the README that it doesn't allow me to build an image?

Could not initialize supporting library.

Help！Help！
The first thank you for your help everyone.
I run the command in zcu104.
It shows error :

root@xilinx:~# gst-launch-1.0 filesrc location=/media/card/kbg.mp4 ! qtdemux name=demux demux.video_0 ! h264parse ! omxh264dec ! queue max-size-bytes=0 ! kmssink bus-id=b00c0000.v_mix fullscreen-overlay=1 demux.audio_0 ! queue max-size-bytes=0 ! faad ! audioconvert ! audioresample ! audio/x-raw, channels=2 ! autoaudiosink
Setting pipeline to PAUSED ...
Couldnt allocate dma allocator (tried using /dev/allegroDecodeIP)
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstOMXH264Dec-omxh264dec:omxh264dec-omxh264dec0: Could not initialize supporting library.
Additional debug info:
../../../../git/gst-libs/gst/video/gstvideodecoder.c(2530): gst_video_decoder_change_state (): /GstPipeline:pipeline0/GstOMXH264Dec-omxh264dec:omxh264dec-omxh264dec0:
Failed to open decoder
Setting pipeline to NULL ...
Freeing pipeline ...
root@xilinx:~# 

recipes-graphics/drm/libdrm_%.bbappend outdated and incompatible with scarthgap

file://0001-modetest-Add-YUV444-and-X403-format-support-for-mode.patch is incomaptible
file://0003-modetest-Add-semiplanar-10bit-pattern-support-for-mo.patch is incomaptible
file://0004-modetest-fix-smpte-colour-pattern-issue-for-XV20-and.patch is incomaptible

Can't build petalinux-image-full for zcu102-zynqmp

When trying to build (using Yocto distribution fetched using github.com/Xilinx/yocto-manifests), 2017.4 building xen fails with:

WARNING: xen-4.8.0-r0 do_fetch: Failed to fetch URL git://github.com/Xilinx/xen.git;protocol=https;branch=xilinx/stable-4.8, attempting MIRRORS if available                                                       
ERROR: xen-4.8.0-r0 do_fetch: Fetcher failure: Unable to find revision 75c00aca503fe7093ccfecb3d0dd803642cb7bae in branch xilinx/stable-4.8 even from upstream                                                     
ERROR: xen-4.8.0-r0 do_fetch: Fetcher failure for URL: 'git://github.com/Xilinx/xen.git;protocol=https;branch=xilinx/stable-4.8'. Unable to fetch URL from any source.                                             
ERROR: xen-4.8.0-r0 do_fetch: Function failed: base_do_fetch

Upon further inspection, the commit 75c00aca503fe7093ccfecb3d0dd803642cb7bae does not belong to any branch in the tree. It is tagged as rel-v2017.4 which makes sense as to why this revision would be selected in the rel-v2017.4 branch of meta-petalinux. (I am avoiding 2018.1 for now)

Temporarily fixed it by using the latest commit in the upstream branch, however this is pretty annoying.

rel-v2022.2 XSCT URL dead link

Hi,

I fetched repo for rel-v2022.2. When I run MACHINE=zc706-zynq7 bitbake petalinux-image-minimal, bitbake cannot fetch xsct binary tarball:

NOTE: Fetching xsct binary tarball from http://petalinux.xilinx.com/sswreleases/rel-v2022/xsct-trim/xsct-2022-2.tar.xz;sha256sum=8a3272036ca61f017f357bf6ad9dfbdec6aebb39f43c3ca0cee7ec86ea4c066f;downloadfilename=xsct_2022.2.tar.xz

Build stucks on the command above, The link itself returns 404.

start_getty cannot handle tty number > 9

Line 14 of start_getty uses a regular expression that only works for single digit tty numbers.
runtime_tty=$(echo $2 | grep -oh '[0-9]')
If you have e.g. a ttyPS10, it fails.

Please change line 14 to:
runtime_tty=$(echo $2 | grep -oh '[0-9]*')

Yocto LTS Support

Petalinux and generally all xilinx layers are based on yocto releases which are already EOL !

any thought about including support for LTS !!!

Could not initialize supporting library (omxh264dec-omxh264dec0)

I use Petalinux to build the system run on ZCU102 board. I have played .webm video format sucessfully, but when I try to play a .mp4 video format I met an error:
The error is shown below, could you help me out?

root@xilinx-zcu102-2020_1:~/honglc_samples/segmentation# gst-launch-1.0 filesrc location=./video/traffic.mp4 ! qtdemux name=demux demux.video_0 ! h264parse ! omxh264dec ! queue max-size-bytes=0 ! kmssink bus-id=fd4a0000.zynqmp-display fullscreen-overlay=1
Setting pipeline to PAUSED ...
[2020-08-19 05:02:20.494530490] [omx_core.cpp:181] [OMX_GetHandle] Couldnt allocate dma allocator (tried using /dev/allegroDecodeIP)
ERROR: Pipeline doesn't want to pause.
ERROR: from element /GstPipeline:pipeline0/GstOMXH264Dec-omxh264dec:omxh264dec-omxh264dec0: Could not initialize supporting library.
Additional debug info:
../../../../git/gst-libs/gst/video/gstvideodecoder.c(2614): gst_video_decoder_change_state (): /GstPipeline:pipeline0/GstOMXH264Dec-omxh264dec:omxh264dec-omxh264dec0:
Failed to open decoder
Setting pipeline to NULL ...
Freeing pipeline ...

device_remove: Device '[email protected]' failed to remove, but children are gone

Hi, I've built a petalinux project with basic MPSoC block configuration for vitis support.

I'm facing the following error while booting the board.

device_remove: Device '[email protected]' failed to remove, but children are gone

Here is the complete boot log:

NOTICE:  ATF running on XCZU19EG/silicon v4/RTL5.1 at 0xfffea000
NOTICE:  BL31: v2.4(release):xlnx_rebase_v2.4_2021.1_update1
NOTICE:  BL31: Built : 08:27:07, Apr 28 2021


U-Boot 2021.01 (Jun 01 2021 - 11:54:06 +0000)

Board: Xilinx ZynqMP
DRAM:  3.4 GiB
PMUFW:	v1.1
EL Level:	EL2
Chip ID:	zu19eg
NAND:  0 MiB
MMC:   mmc@ff160000: 0, mmc@ff170000: 1
Loading Environment from FAT... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Bootmode: SD_MODE1
Reset reason:	EXTERNAL 
Net:   
ZYNQ GEM: ff0b0000, mdio bus ff0b0000, phyaddr 1, interface rgmii-id
eth0: ethernet@ff0b0000
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot.scr
2594 bytes read in 15 ms (168 KiB/s)
## Executing script at 20000000
Trying to load boot images from mmc1
22712832 bytes read in 1463 ms (14.8 MiB/s)
## Flattened Device Tree blob at 00100000
   Booting using the fdt blob at 0x100000
   Loading Device Tree to 000000005dd05000, end 000000005dd12adc ... OK

Starting kernel ...

unable to select a mode : -110
device_remove: Device '[email protected]' failed to remove, but children are gone
[    0.000000][    T0] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000][    T0] Linux version 5.10.0-xilinx-v2021.1 (oe-user@oe-host) (aarch64-xilinx-linux-gcc (GCC) 10.2.0, GNU ld (GNU Binutils) 2.35.1) #1 SMP Fri Jun 4 15:57:16 UTC 2021
[    0.000000][    T0] Machine model: xlnx,zynqmp
[    0.000000][    T0] earlycon: cdns0 at MMIO 0x00000000ff000000 (options '115200n8')
[    0.000000][    T0] printk: bootconsole [cdns0] enabled
[    0.000000][    T0] efi: UEFI not found.
[    0.000000][    T0] Reserved memory: created DMA memory pool at 0x0000000060000000, size 512 MiB
[    0.000000][    T0] OF: reserved mem: initialized node buffer@0x60000000, compatible id shared-dma-pool
[    0.000000][    T0] Reserved memory: created DMA memory pool at 0x0000000500000000, size 1520 MiB
[    0.000000][    T0] OF: reserved mem: initialized node buffer@0x500000000, compatible id shared-dma-pool
[    0.000000][    T0] Reserved memory: created DMA memory pool at 0x000000055f000000, size 16 MiB
[    0.000000][    T0] OF: reserved mem: initialized node buffer@0x55F000000, compatible id shared-dma-pool
[    0.000000][    T0] cma: Reserved 512 MiB at 0x000000003dc00000
[    0.000000][    T0] Zone ranges:
[    0.000000][    T0]   DMA32    [mem 0x0000000000000000-0x00000000ffffffff]
[    0.000000][    T0]   Normal   [mem 0x0000000100000000-0x000000087bffffff]
[    0.000000][    T0] Movable zone start for each node
[    0.000000][    T0] Early memory node ranges
[    0.000000][    T0]   node   0: [mem 0x0000000000000000-0x000000005fefffff]
[    0.000000][    T0]   node   0: [mem 0x0000000800000000-0x000000087bffffff]
[    0.000000][    T0] Zeroed struct page in unavailable ranges: 256 pages
[    0.000000][    T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000087bffffff]
[    0.000000][    T0] psci: probing for conduit method from DT.
[    0.000000][    T0] psci: PSCIv1.1 detected in firmware.
[    0.000000][    T0] psci: Using standard PSCI v0.2 function IDs
[    0.000000][    T0] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000][    T0] psci: SMC Calling Convention v1.2
[    0.000000][    T0] percpu: Embedded 22 pages/cpu s49624 r8192 d32296 u90112
[    0.000000][    T0] Detected VIPT I-cache on CPU0
[    0.000000][    T0] CPU features: detected: ARM erratum 845719
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 886788
[    0.000000][    T0] Kernel command line: earlycon console=ttyPS0, 115200 clk_ignore_unused root=/dev/mmcblk0p2 rw rootwait cma=512M
[    0.000000][    T0] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear)
[    0.000000][    T0] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000][    T0] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000][    T0] software IO TLB: mapped [mem 0x0000000039c00000-0x000000003dc00000] (64MB)
[    0.000000][    T0] Memory: 2911152K/3603456K available (14144K kernel code, 1188K rwdata, 4160K rodata, 2560K init, 588K bss, 168016K reserved, 524288K cma-reserved)
[    0.000000][    T0] rcu: Hierarchical RCU implementation.
[    0.000000][    T0] rcu: 	RCU event tracing is enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000][    T0] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000][    T0] GIC: Adjusting CPU interface base to 0x00000000f902f000
[    0.000000][    T0] GIC: Using split EOI/Deactivate mode
[    0.000000][    T0] irq-xilinx: mismatch in kind-of-intr param
[    0.000000][    T0] irq-xilinx: /amba_pl@0/interrupt-controller@80000000: num_irq=32, sw_irq=0, edge=0x1
[    0.000000][    T0] random: get_random_bytes called from start_kernel+0x31c/0x524 with crng_init=0
[    0.000000][    T0] arch_timer: cp15 timer(s) running at 33.33MHz (phys).
[    0.000000][    T0] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x7b0074340, max_idle_ns: 440795202884 ns
[    0.000003][    T0] sched_clock: 56 bits at 33MHz, resolution 30ns, wraps every 2199023255543ns
[    0.008982][    T0] Console: colour dummy device 80x25
[    0.013777][    T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 66.66 BogoMIPS (lpj=133332)
[    0.024744][    T0] pid_max: default: 32768 minimum: 301
[    0.030158][    T0] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.038075][    T0] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.047562][    T1] rcu: Hierarchical SRCU implementation.
[    0.052584][    T1] EFI services will not be available.
[    0.057334][    T1] smp: Bringing up secondary CPUs ...
[    0.062735][    T0] Detected VIPT I-cache on CPU1
[    0.062774][    T0] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.063155][    T0] Detected VIPT I-cache on CPU2
[    0.063179][    T0] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.063550][    T0] Detected VIPT I-cache on CPU3
[    0.063573][    T0] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.063619][    T1] smp: Brought up 1 node, 4 CPUs
[    0.102680][    T1] SMP: Total of 4 processors activated.
[    0.108044][    T1] CPU features: detected: 32-bit EL0 Support
[    0.113840][    T1] CPU features: detected: CRC32 instructions
[    0.119667][    T1] CPU: All CPU(s) started at EL2
[    0.124404][   T11] alternatives: patching kernel code
[    0.130399][    T1] devtmpfs: initialized
[    0.138172][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.143867][    T1] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.164270][    T1] pinctrl core: initialized pinctrl subsystem
[    0.164911][    T1] DMI not present or invalid.
[    0.169224][    T1] NET: Registered protocol family 16
[    0.175219][    T1] DMA: preallocated 512 KiB GFP_KERNEL pool for atomic allocations
[    0.181951][    T1] DMA: preallocated 512 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.190448][    T1] audit: initializing netlink subsys (disabled)
[    0.196607][   T30] audit: type=2000 audit(0.132:1): state=initialized audit_enabled=0 res=1
[    0.196973][    T1] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.212354][    T1] ASID allocator initialised with 65536 entries
[    0.218481][    T1] Serial: AMBA PL011 UART driver
[    0.247175][    T1] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.248924][    T1] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.256282][    T1] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.263635][    T1] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    1.315825][    T1] cryptd: max_cpu_qlen set to 1000
[    1.340274][   T86] DRBG: Continuing without Jitter RNG
[    1.419759][    T1] raid6: neonx8   gen()  2144 MB/s
[    1.487813][    T1] raid6: neonx8   xor()  1596 MB/s
[    1.555879][    T1] raid6: neonx4   gen()  2185 MB/s
[    1.623939][    T1] raid6: neonx4   xor()  1564 MB/s
[    1.692016][    T1] raid6: neonx2   gen()  2075 MB/s
[    1.760066][    T1] raid6: neonx2   xor()  1432 MB/s
[    1.828138][    T1] raid6: neonx1   gen()  1773 MB/s
[    1.896193][    T1] raid6: neonx1   xor()  1219 MB/s
[    1.964263][    T1] raid6: int64x8  gen()  1437 MB/s
[    2.032315][    T1] raid6: int64x8  xor()   771 MB/s
[    2.100399][    T1] raid6: int64x4  gen()  1601 MB/s
[    2.168449][    T1] raid6: int64x4  xor()   817 MB/s
[    2.236528][    T1] raid6: int64x2  gen()  1394 MB/s
[    2.304581][    T1] raid6: int64x2  xor()   749 MB/s
[    2.372654][    T1] raid6: int64x1  gen()  1029 MB/s
[    2.440709][    T1] raid6: int64x1  xor()   517 MB/s
[    2.440752][    T1] raid6: using algorithm neonx4 gen() 2185 MB/s
[    2.446084][    T1] raid6: .... xor() 1564 MB/s, rmw enabled
[    2.451706][    T1] raid6: using neon recovery algorithm
[    2.457535][    T1] iommu: Default domain type: Translated 
[    2.462734][    T1] SCSI subsystem initialized
[    2.467073][    T1] usbcore: registered new interface driver usbfs
[    2.473098][    T1] usbcore: registered new interface driver hub
[    2.479073][    T1] usbcore: registered new device driver usb
[    2.484803][    T1] mc: Linux media interface: v0.10
[    2.489697][    T1] videodev: Linux video capture interface: v2.00
[    2.495862][    T1] EDAC MC: Ver: 3.0.0
[    2.499972][    T1] zynqmp-ipi-mbox mailbox@ff990400: Registered ZynqMP IPI mbox with TX/RX channels.
[    2.508982][    T1] FPGA manager framework
[    2.512984][    T1] Advanced Linux Sound Architecture Driver Initialized.
[    2.519894][    T1] Bluetooth: Core ver 2.22
[    2.523868][    T1] NET: Registered protocol family 31
[    2.528953][    T1] Bluetooth: HCI device and connection manager initialized
[    2.535962][    T1] Bluetooth: HCI socket layer initialized
[    2.541496][    T1] Bluetooth: L2CAP socket layer initialized
[    2.547210][    T1] Bluetooth: SCO socket layer initialized
[    2.552995][    T1] clocksource: Switched to clocksource arch_sys_counter
[    2.559626][    T1] VFS: Disk quotas dquot_6.6.0
[    2.564115][    T1] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    2.575986][    T1] NET: Registered protocol family 2
[    2.576949][    T1] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear)
[    2.585829][    T1] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    2.594549][    T1] TCP bind hash table entries: 32768 (order: 7, 524288 bytes, linear)
[    2.602687][    T1] TCP: Hash tables configured (established 32768 bind 32768)
[    2.609554][    T1] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    2.616913][    T1] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear)
[    2.624792][    T1] NET: Registered protocol family 1
[    2.629925][    T1] RPC: Registered named UNIX socket transport module.
[    2.636223][    T1] RPC: Registered udp transport module.
[    2.641584][    T1] RPC: Registered tcp transport module.
[    2.646941][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    2.654620][    T1] PCI: CLS 0 bytes, default 64
[    2.684469][    T1] Initialise system trusted keyrings
[    2.684599][    T1] workingset: timestamp_bits=46 max_order=20 bucket_order=0
[    2.691760][    T1] NFS: Registering the id_resolver key type
[    2.696784][    T1] Key type id_resolver registered
[    2.701617][    T1] Key type id_legacy registered
[    2.706312][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    2.713655][    T1] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    2.757781][    T1] NET: Registered protocol family 38
[    2.757831][    T1] xor: measuring software checksum speed
[    2.766898][    T1]    8regs           :  2363 MB/sec
[    2.771259][    T1]    32regs          :  2799 MB/sec
[    2.776893][    T1]    arm64_neon      :  2380 MB/sec
[    2.777779][    T1] xor: using function: 32regs (2799 MB/sec)
[    2.783495][    T1] Key type asymmetric registered
[    2.788247][    T1] Asymmetric key parser 'x509' registered
[    2.793804][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[    2.801829][    T1] io scheduler mq-deadline registered
[    2.807017][    T1] io scheduler kyber registered
[    2.813724][    T1] ps_pcie_dma init()
[    2.839911][    T1] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    2.842385][    T1] Serial: AMBA driver
[    2.847609][   T12] cacheinfo: Unable to detect cache hierarchy for CPU 0
[    2.856328][    T1] brd: module loaded
[    2.860631][    T1] loop: module loaded
[    2.861483][    T1] mtdoops: mtd device (mtddev=name/number) must be supplied
[    2.867882][    T1] libphy: Fixed MDIO Bus: probed
[    2.872522][    T1] tun: Universal TUN/TAP device driver, 1.6
[    2.877043][    T1] CAN device driver interface
[    2.882241][    T1] usbcore: registered new interface driver asix
[    2.887551][    T1] usbcore: registered new interface driver ax88179_178a
[    2.894275][    T1] usbcore: registered new interface driver cdc_ether
[    2.900761][    T1] usbcore: registered new interface driver net1080
[    2.907077][    T1] usbcore: registered new interface driver cdc_subset
[    2.913649][    T1] usbcore: registered new interface driver zaurus
[    2.919889][    T1] usbcore: registered new interface driver cdc_ncm
[    2.927066][    T1] usbcore: registered new interface driver uas
[    2.932178][    T1] usbcore: registered new interface driver usb-storage
[    2.939419][    T1] rtc_zynqmp ffa60000.rtc: registered as rtc0
[    2.944703][    T1] rtc_zynqmp ffa60000.rtc: setting system clock to 2103-12-17T11:29:02 UTC (4227334142)
[    2.954245][    T1] i2c /dev entries driver
[    2.959913][    T1] usbcore: registered new interface driver uvcvideo
[    2.964758][    T1] USB Video Class driver (1.1.1)
[    2.970005][    T1] Bluetooth: HCI UART driver ver 2.3
[    2.974624][    T1] Bluetooth: HCI UART protocol H4 registered
[    2.980412][    T1] Bluetooth: HCI UART protocol BCSP registered
[    2.986393][    T1] Bluetooth: HCI UART protocol LL registered
[    2.992174][    T1] Bluetooth: HCI UART protocol ATH3K registered
[    2.998244][    T1] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    3.005182][    T1] Bluetooth: HCI UART protocol Intel registered
[    3.011217][    T1] Bluetooth: HCI UART protocol QCA registered
[    3.017109][    T1] usbcore: registered new interface driver bcm203x
[    3.023423][    T1] usbcore: registered new interface driver bpa10x
[    3.029653][    T1] usbcore: registered new interface driver bfusb
[    3.035794][    T1] usbcore: registered new interface driver btusb
[    3.041947][    T1] usbcore: registered new interface driver ath3k
[    3.048133][    T1] EDAC MC: ECC not enabled
[    3.052411][    T1] EDAC DEVICE0: Giving out device to module edac controller cache_err: DEV edac (POLLED)
[    3.062055][    T1] EDAC DEVICE1: Giving out device to module zynqmp-ocm-edac controller zynqmp_ocm: DEV ff960000.memory-controller (INTERRUPT)
[    3.074971][    T1] sdhci: Secure Digital Host Controller Interface driver
[    3.081530][    T1] sdhci: Copyright(c) Pierre Ossman
[    3.086545][    T1] sdhci-pltfm: SDHCI platform and OF driver helper
[    3.093207][    T1] ledtrig-cpu: registered to indicate activity on CPUs
[    3.099535][    T1] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping ....
[    3.106649][    T1] zynqmp_firmware_probe Platform Management API v1.1
[    3.113104][    T1] zynqmp_firmware_probe Trustzone version v1.0
[    3.176248][  T199] alg: No test for xilinx-zynqmp-aes (zynqmp-aes)
[    3.176893][    T1] zynqmp_aes firmware:zynqmp-firmware:zynqmp-aes: AES Successfully Registered
[    3.185721][  T200] alg: No test for xilinx-keccak-384 (zynqmp-keccak-384)
[    3.192544][  T201] alg: No test for xilinx-zynqmp-rsa (zynqmp-rsa)
[    3.198742][    T1] usbcore: registered new interface driver usbhid
[    3.204821][    T1] usbhid: USB HID core driver
[    3.212004][    T1] ARM CCI_400_r1 PMU driver probed
[    3.212469][    T1] fpga_manager fpga0: Xilinx ZynqMP FPGA Manager registered
[    3.221775][    T1] usbcore: registered new interface driver snd-usb-audio
[    3.229008][    T1] pktgen: Packet Generator for packet performance testing. Version: 2.75
[    3.237008][    T1] Initializing XFRM netlink socket
[    3.241390][    T1] NET: Registered protocol family 10
[    3.246831][    T1] Segment Routing with IPv6
[    3.250914][    T1] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    3.257672][    T1] NET: Registered protocol family 17
[    3.262440][    T1] NET: Registered protocol family 15
[    3.267542][    T1] can: controller area network core
[    3.272577][    T1] NET: Registered protocol family 29
[    3.277656][    T1] can: raw protocol
[    3.281286][    T1] can: broadcast manager protocol
[    3.286134][    T1] can: netlink gateway - max_hops=1
[    3.291219][    T1] Bluetooth: RFCOMM TTY layer initialized
[    3.296692][    T1] Bluetooth: RFCOMM socket layer initialized
[    3.302490][    T1] Bluetooth: RFCOMM ver 1.11
[    3.306899][    T1] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    3.312857][    T1] Bluetooth: BNEP filters: protocol multicast
[    3.318745][    T1] Bluetooth: BNEP socket layer initialized
[    3.324364][    T1] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    3.330939][    T1] Bluetooth: HIDP socket layer initialized
[    3.336671][    T1] 9pnet: Installing 9P2000 support
[    3.341515][    T1] Key type dns_resolver registered
[    3.346541][    T1] registered taskstats version 1
[    3.351179][    T1] Loading compiled-in X.509 certificates
[    3.357580][    T1] Btrfs loaded, crc32c=crc32c-generic
[    3.370397][   T31] ff000000.serial: ttyPS0 at MMIO 0xff000000 (irq = 55, base_baud = 6249999) is a xuartps

The board doesn't seem to be printing any kernel logs after the UART output.
Can someone take a look and help me in resolving this issue?

Thanks & Regards,
Saikiran Belana

FSBL build fails if RF Data Converter Block is not instantiated in Block Design of ZCU111

Affected line of code:

meta-petalinux/recipes-bsp/fsbl/fsbl_%.bbappend

Line 10 in 68cb2ce

install -m 0644 ${XSCTH_WS}/${XSCTH_PROJ}_bsp/${XSCTH_PROC}/libsrc/rfdc*/src/xrfdc_g.c ${STAGING_RFDC_DIR}

I am trying to build a project with yocto and the machine "zcu111-zynqmp".
I wanted to start with a rather empty hardware design and only instantiated a zynqmp core (which works e.g. for the ZCU102).
Synthesis and implementation work fine. But when Yocto performs the task "do_shared_workdir" of the fsbl it fails with the following error:

ERROR: fsbl-2018.2+gitAUTOINC+6e82c0183b-r0 do_shared_workdir: Function failed: do_shared_workdir (log file is located at /.../build/tmp/work/zcu111_zynqmp-xilinx-linux/fsbl/2018.2+gitAUTOINC+6e82c0183b-r0/temp/log.do_shared_workdir.17801)
ERROR: Logfile of failure stored in: /.../build/tmp/work/zcu111_zynqmp-xilinx-linux/fsbl/2018.2+gitAUTOINC+6e82c0183b-r0/temp/log.do_shared_workdir.17801
Log data follows:
| DEBUG: Executing shell function do_shared_workdir
| install: cannot stat ‘/.../build/tmp/work/zcu111_zynqmp-xilinx-linux/fsbl/2018.2+gitAUTOINC+6e82c0183b-r0/build/fsbl_bsp/psu_cortexa53_0/libsrc/rfdc*/src/xrfdc_g.c’: No such file or directory
| WARNING: /.../build/tmp/work/zcu111_zynqmp-xilinx-linux/fsbl/2018.2+gitAUTOINC+6e82c0183b-r0/temp/run.do_shared_workdir.17801:1 exit 1 from 'install -m 0644 /.../build/tmp/work/zcu111_zynqmp-xilinx-linux/fsbl/2018.2+gitAUTOINC+6e82c0183b-r0/build/fsbl_bsp/psu_cortexa53_0/libsrc/rfdc*/src/xrfdc_g.c /.../build/tmp/work-shared/zcu111-zynqmp/rfdc-source'
| ERROR: Function failed: do_shared_workdir (log file is located at /.../build/tmp/work/zcu111_zynqmp-xilinx-linux/fsbl/2018.2+gitAUTOINC+6e82c0183b-r0/temp/log.do_shared_workdir.17801)
ERROR: Task (/.../poky/../sources/meta-xilinx-tools/recipes-bsp/fsbl/fsbl_git.bb:do_shared_workdir) failed with exit code '1'

It seems like the FSBL requires libraries that are only generated when the RF Data Converter Block is instantiated in the block design. In this matter, it seems like an unresolved dependency of the FSBL.

In contrast, if I implement the Data Converter Block in a very basic way (all ADC/DACs turned off, only AXI and CLK connected), the whole project builds without any error messages. See this block design:

But running it on the ZCU111, it turns out the the FSBL starts but never triggers the second stage. I suspect that this might be due to the Data Converter Block which is correctly connected in a hardware sense but not in the sense the FSBL expect it to be? Is there a particular reason why the FSBL requires the RFdc?

[Issue report and suggest] check_init() with Ubuntu 20.04 Rootfs "/sbin/init"

Hi there,
We updated the kernel from petelinux 2020 to 2021 with Ubuntu rootfs which released for KV260.

The check_init() function was added by 2021, we got a problem at check_init() where was at /scripts/functions.sh in ramdisk. Put differently, at here

Root cause:
if you checked the path "/rootfs/sbin/init", it means "/rootfs/sbin/lib/systemd", the checking always return 1 to umount $path here

and why it not happen with petalinux rootfs?
buz checked the path "/rootfs/sbin/inin", it means "/rootfs/sbin/init.sysvinit".

That's all.

If so, we suggest considering the situation for using Ubuntu rootfs user.

Thank you so much!

Upgrade recipes-core/runx to support kernel version 6+

Hello,

I ran Petalinux 2023.2 and found that recipes-core/runx is outdated, targeting old kernel version 5.

This is affecting and disrupting the installation of packagegroup-petalinux-ocicontainers.

Do you have any schedule to upgrade runx to support kernel version 6.1.30 for Petalinux 2023.2 and onwards?

Thanks in advance!
David.

The recipe for distcc cannot be build on R2018.2.

Hello there,

I'm hoping that this is the correct place for this issue.
Earlier on, I tried building a yocto recipe for the ZCU106 based on this layer, and it failed at building distcc as shown:

| In file included from /usr/include/python2.7/Python.h:8:0,
|                  from /home/brainiarc7/source.build/zcu106/build/tmp/work/aarch64-xilinx-linux/distcc/3.2-maint-r0/git/include_server/c_extensions/distcc_pump_c_extensions_module.c:24:
| /usr/include/python2.7/pyconfig.h:12:12: fatal error: aarch64-linux-gnu/python2.7/pyconfig.h: No such file or directory
|  #  include <aarch64-linux-gnu/python2.7/pyconfig.h>
|             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| compilation terminated.
| error: command 'aarch64-xilinx-linux-gcc' failed with exit status 1
| Makefile:570: recipe for target 'include-server' failed
| make: *** [include-server] Error 1
| ERROR: oe_runmake failed

On the host system, all python related dependencies, ie python-dev, are installed.

How can I fix this error?

Thanks.