Configuring Project Components

Configuring Project Components - 2020.2 English

PetaLinux Tools Documentation Reference Guide (UG1144)

Document ID

UG1144

Release Date

2020-11-24

Version

2020.2 English

If you want to perform advanced PetaLinux project configuration such as enabling Linux kernel options or modifying flash partitions, use the petalinux-config tool with the appropriate -c COMPONENT option.

Important: Only Xilinx® drivers or optimizations in the Linux kernel configuration are supported by Xilinx technical support. For more information on Xilinx drivers for Linux, see https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841873/Linux+Drivers.

The examples below demonstrate how to use petalinux-config to review or modify your PetaLinux project configuration.

Change into the root directory of your PetaLinux project.
```
$ cd <plnx-proj-root>
```
Launch the top level system configuration menu and configure it to meet your requirements:
```
$ petalinux-config
```
Launch the Linux kernel configuration menu and configure it to meet your requirements:
```
$ petalinux-config -c kernel
```
Launch the root file system configuration menu and configure it to meet your requirements:
```
$ petalinux-config -c rootfs
```
Use --silentconfig for the components when you do not have Kconfig/Menuconfig support or to skip the launching of configuration menu
```
$ petalinux-config -c <COMPONENT> --silentconfig
```

Note: petalinux-config -c <COMPONENT> command creates the workspace directory <plnx-proj-root>/components/yocto/workspace/sources/<COMPONENT> by fetching the source. For example,

petalinux-config -c
                    u-boot

fetches the U-Boot source and create the workspace in <plnx-proj-root>/components/sources/u-boot-xlnx. You can use this in your development.

Note: Using

petalinux-config -c
                            <COMPONENT>

the component changes will be stored in workspace directory (<project-root-dir>/components/yocto/workspace). To apply workspace changes to the recipe in the meta-user user must run petalinux-devtool finish command to return their build location, for example,

petalinux-devtool
                            finish linux-xlnx
                        <plnx-proj-dir>/project-spec/meta-user

Warning Message for petalinux-config or petalinux-build Commands

The following warning message appears when you run the petalinux-config or petalinux-build for components (Ex: petalinux-build -c u-boot) and this can be ignored.

WARNING: SRC_URI is conditionally overridden in this recipe, thus several devtool-override-* branches have been created, one for each override that makes changes to SRC_URI. It is recommended that you make changes to the devtool branch first, then checkout and rebase each devtool-override-* branch and update any unique patches there (duplicates on those branches will be ignored by devtool finish/update-recipe).

Note: Please make sure board and user specific dtsi entries are added to project-spec/meta-user/recipes-bsp/device-tree/files/system-user.dtsi.

Using template flow, for zcu102 and zcu106 boards, add the following line to <plnx-proj-root>/project-spec/meta-user/recipes-bsp/fsbl/fsbl_%.bbappend for FSBL initializations.

YAML_COMPILER_FLAGS_append = " -DXPS_BOARD_ZCU102" #for zcu102
YAML_COMPILER_FLAGS_append = " -DXPS_BOARD_ZCU106" # for zcu106