1 of 1 people found this helpful
Starting with PetaLinux 2019.2 Xilinx made the change that user's custom additions to the <>/project-spec/meta-user/recipes-core/images/petalinux-user-image.bb file are no longer supported. Apparently this was some sort of violation of yocto rules to use .bb files for kconfig options. Instead users must now create a <>/project-spec/meta-user/conf/user-rootfsconfig file with contents that look similar to this:
#Note: Mention Each package in individual line
#These packages will get added into rootfs menu entry
More information about this change can be found in Appendix A of Xilinx UG1144.
Yes that works, thanks for help!
I have small problem with visibility of meta-user packages.
I have copied all "project-spec/meta-user/*" files from BSP 2019.1 to 2019.2 and I can't see any new fields in "petalinux-config -c rootfs", but if I add contents of "/project-spec/meta-user/recipes-core/images/petalinux-user-image.bb(meta-user copied)" to "/project-spec/meta-plnx-generated/recipes-core/images/petalinux-image.bbappend (meta-plnx-generated autogenerated)" petalinux builds fine. But this is uncomfortable for use and is just bad because it resets after any change to sys-root.
The question is how can I make those packages visible in rootfs? There should be new row with userapps, wifi drivers etc. What I'm missing? Avnet speedway workshop miss those details and I couldn't find solution there.
Thanks for help!
Minized BSP 2019.2 Vitis Ready + WIFI it uses /run/media/mmcblk1p2 as root filesystem (extract whole root image there from tar.gz), put rest of generated petalinux files to /run/media/mmcblk1p1
Also this BSP can have many, many flaws that I'm unaware of so use it with caution and at your own risk