PetaLinux Project Structure - 2022.2 English

This section provides a brief introduction to the file and directory structure of a PetaLinux project. A PetaLinux project supports development of a single Linux system development at a time. A built Linux system is composed of the following components:

• Device tree
• First stage boot loader (optional)
• U-Boot
• Linux kernel
• The root file system is composed of the following components:
  • Prebuilt packages
  • Linux user applications (optional)
  • User modules (optional)

A PetaLinux project directory contains configuration files of the project, the Linux subsystem, and the components of the subsystem. The petalinux-build command builds the project with those configuration files. You can run petalinux-config to modify them. The following is an example of a PetaLinux project:

project-spec
   hw-description
   configs
   meta-user
pre-built
   linux
      implementation
      images 
      xen    
hardware
  <project-name>
components
   plnx_workspace
      device-tree
config.project
README

When the project is built, three directories are auto generated:

• <plnx-proj-root>/build for the files generated for build.
• <plnx-proj-root>/images for the bootable images.
• <plnx-proj-root>/build/tmp for the files generated by Yocto. This directory is configurable through petalinux-config.
• <plnx-proj-root>/components/yocto has Yocto eSDK. This file is generated when execute petalinux-config/petalinux-build.
• When petalinux-package --prebuilt is run, it creates a pre-built/directory in <PROJECT>/ and copies the build image files from the <PROJECT>/images/linux directory to the <PROJECT>/pre-built/linux/images/ directory.

Here is an example:

├── build
│   ├── bitbake-cookerdaemon.log
│   ├── build.log
│   ├── cache
│   ├── conf
│   ├── downloads
│   ├── misc
│   ├── sstate-cache
│   └── tmp
├── components
│   ├── plnx_workspace
│   └── yocto
├── config.project
├── hardware
│   └── project-name
├── images
│   └── linux
├── pre-built
│   └── linux
├── project-spec
│   ├── attributes
│   ├── configs
│   ├── hw-description
│   └── meta-user
└── README

The table below is an example for Zynq® UltraScale+™ MPSoC.

By default the build artifacts are removed to preserve space after petalinux-build. To preserve the build artifacts, you have to add the INHERIT_remove = "rm_work" in <plnx-proj-root>/project-spec/meta-user/conf/petalinuxbsp.conf, but it increases the project space.