07-31-2019 07:18 AM
I'm trying to figure out why the petalinux-config step fails to generate meta-plnx-generated layer?
Is there someway to debug why the failure occurs by looking at a log file?
johnnie@johnnie-VirtualBox:/media/sf_PetaLinux/arty_petalinux$ petalinux-config --get-hw-description ../PetaLinux.sdk --oldconfig
WARNING: --oldconfig will be deprecated in the feature releases,Please use --silentconfig.
INFO: Getting hardware description...
INFO: Rename system_wrapper.hdf to system.hdf
[INFO] generating Kconfig for project
INFO: Updating the flash partition size to 0x200000 bytes, based on the bitstream in the HDF
[INFO] silentconfig project
[INFO] sourcing bitbake
[INFO] generating plnxtool conf
[INFO] generating meta-plnx-generated layer
ERROR: Failed to generate meta-plnx-generated layer
ERROR: Failed to config project.
ERROR: Get hw description Failed!.
08-01-2019 01:55 PM
Think I resolved the issue. I was using a VirtualBox folder share and either it didn't like the fact that it was on a NTFS partition, file ownership or file permissions.
10-22-2019 10:53 PM
I met the same issue. Looks like the reason is petalinux-config can only use python2.7, but my default link to python is python3.7 from anaconda3.
My solution is creating a virtual env by conda, and use petalinux-config in it.
conda create --name petalinux python=2.7 conda activate petalinux
04-12-2020 04:05 AM
I was using a VirtualBox folder share and either it didn't like the fact that it was on a NTFS partition, file ownership or file permissions. However, I wouldn’t rule out the python issue as described by another user.
04-19-2020 01:46 AM
I had this same problem "Failed to generate meta-plnx-generated layer" in Petalinux 2019.2.
I've tried many things, I had everything stored in ext4, I made chown and chmod 755 to whole project and did not solve the problem. Only way was to create a new project !
I was suspecting then that plnx either might didn't like finding foreign files in /meta-plnx-generated or could not delete such folder for regeneration.
I thought then that I use Atom.io, like Eclipse and others, I had whole project opened in it, and that bothers plnx. So I excluded /meta-plnx-generated, I only have now /meta-user folder as project to work with apps. Then it's not blocked anymore, works like charm.
04-28-2020 01:52 PM
05-06-2020 08:16 AM
What exactly did you do to "exclude" meta-plnx-generated? I'm having the same problem, I've checked my Python version, and I have the meta-plnx-generated directory.
05-06-2020 08:37 AM
I've just closed (removed) project inside Atom.io; then instead of adding whole petalinux project folder, I've only added /meta-user folder, so then leaving /meta-plnx-generated closed (or without reach from Atom.io).
Now I have a new insight, I think it is Atom.io Git module that surveys /meta-plnx-generated folder, because I added this folder to .gitignore file and then I was able to open whole project in my Atom instance.
So if you are not using something like Atom or Sublime, you might have a Git process surveying your /meta-plnx-generated folder.
I hope it is clear and that helps you, enjoy
05-06-2020 09:04 AM
Thanks. My solution was to run this command:
$ sudo sysctl -n -w fs.inotify.max_user_watches=524288
which I got from reading the build/config.log file. Now to find out what "watches" are...