This page is intended to be a collection place for tips and tricks related to Yocto layers and how Yocto works under Petalinux.
Table of Contents
Documentation
The first place you should start to better understand many details of the Yocto project is the Yocto project website.
Working with a User Space Yocto Layer
This tip has been adapted to PetaLinux using the meta-example layer available here meta-example Code Block |
---|
|
$ git clone https://github.com/DynamicDevices/meta-example |
This example layer is providing 3 build recipes, bbexample, bbexample-rt and bbexample-lt respectively fetching the source code from a git tree, a remote tar file and a local tar file
Override syntax changes from Yocto honister/PetaLinux 2022.1
From 2022 release, the : character replaces the use of _ to refer to an override, most commonly when making a conditional assignment of a variable.
Please refer to /wiki/spaces/XWUC/pages/2329444389for more details.
To help with migration of layers, a script has been provided in OE-Core. Once configured with the overrides used by a layer, this can be run as:
With in PetaLinux:
Code Block |
---|
|
$ cd petalinux<plnx-build proj-croot>
bbexample
$ petalinux-build -c bbexample-rt
$ petalinux-build -c bbexample-lt |
Configuring the layer path in the PetaLinux build system
Move to your PetaLinux project directory, add the layer path in below config option.
Code Block |
---|
cd <plnx-proj-root>
petalinux-config --> Yocto Settings --> User Layers --> (/absolute_path_to_meta_layer/meta-example) user layer 0
--> () user layer 1 |
Move to your Yocto project build directory, edit the conf/bblayers.conf file and add your layer path to BBLAYERS$PETALINUX/components/yocto/buildtools/sysroots/x86_64-petalinux-linux/usr/bin/python3 components/yocto/layers/core/scripts/contrib/convert-overrides.py <meta-layer-path> |
With in Yocto:
Code Block |
---|
|
$ cd <yocto-proj-dir>
$ sources/core/scripts/contrib/convert-overrides.py <meta-layer-path> |
Note |
---|
To execute above convert-overrides.py you need python3 should be installed on host machine. |
Working with a User Space Yocto Layer
This tip has been adapted to PetaLinux using the meta-example layer available here meta-example Code Block |
---|
|
BBLAYERS$ :=git " \
${SDKBASEMETAPATH}/layers/poky/meta \
${SDKBASEMETAPATH}/layers/poky/meta-poky \
/absolute_path_to_meta_layer/meta-example \
" |
The recipe we are going to build is https://github.com/DynamicDevices/meta-example/blob/master/recipes-example/bbexample/bbexample-lt_1.0.bbThe recipe bbexample-lt is using some variables1. SRC_URI Space-delimited list of URIs to download source code, patches, and other files from git, local absolute path, https, ftp etc.2. PN is the Package Name. The value of this variable is derived by BitBake from the base name of the recipe file.3. PV is the Package Version. which is derived by BitBake from the base name of the recipe file Code Block |
---|
|
# Use local tarball
SRC_URI = "file://bbexample-${PV}.tar.gz" |
The recipe bbexample-lt can invoked using the following command Code Block |
---|
|
$ petalinux-build -c bbexample-lt |
here is the command output Code Block |
---|
|
$ petalinux-build -c bbexample-lt
[INFO] building bbexample-lt
[INFO] sourcing bitbake
INFO: bitbake bbexample-lt
Loading cache: 100% |###############################################################################################################################################################################| ETA: 00:00:00
Loaded 2941 entries from dependency cache.
Parsing recipes: 100% |#############################################################################################################################################################################| Time: 00:00:01
Parsing of 2328 .bb files complete (2294 cached, 34 parsed). 2943 targets, 196 skipped, 0 masked, clone https://github.com/DynamicDevices/meta-example |
This example layer is providing 3 build recipes, bbexample, bbexample-rt and bbexample-lt respectively fetching the source code from a git tree, a remote tar file and a local tar file Code Block |
---|
|
$ petalinux-build -c bbexample
$ petalinux-build -c bbexample-rt
$ petalinux-build -c bbexample-lt |
Configuring the layer path in the PetaLinux build system
Move to your PetaLinux project directory, add the layer path in below config option.
Code Block |
---|
cd <plnx-proj-root>
petalinux-config --> Yocto Settings --> User Layers --> (/absolute_path_to_meta_layer/meta-example) user layer 0
--> () user layer 1 |
Move to your Yocto project build directory, edit the conf/bblayers.conf file and add your layer path to BBLAYERS Code Block |
---|
|
BBLAYERS := " \
${SDKBASEMETAPATH}/layers/poky/meta \
${SDKBASEMETAPATH}/layers/poky/meta-poky \
/absolute_path_to_meta_layer/meta-example \
" |
The recipe we are going to build is https://github.com/DynamicDevices/meta-example/blob/master/recipes-example/bbexample/bbexample-lt_1.0.bbThe recipe bbexample-lt is using some variables1. SRC_URI Space-delimited list of URIs to download source code, patches, and other files from git, local absolute path, https, ftp etc.2. PN is the Package Name. The value of this variable is derived by BitBake from the base name of the recipe file.3. PV is the Package Version. which is derived by BitBake from the base name of the recipe file Code Block |
---|
|
# Use local tarball
SRC_URI = "file://bbexample-${PV}.tar.gz" |
The recipe bbexample-lt can invoked using the following command Code Block |
---|
|
$ petalinux-build -c bbexample-lt |
here is the command output Code Block |
---|
|
$ petalinux-build -c bbexample-lt
[INFO] building bbexample-lt
[INFO] sourcing bitbake
INFO: bitbake bbexample-lt
Loading cache: 100% |###############################################################################################################################################################################| ETA: 00:00:00
Loaded 2941 entries from dependency cache.
Parsing recipes: 100% |#############################################################################################################################################################################| Time: 00:00:01
Parsing of 2328 .bb files complete (2294 cached, 34 parsed). 2943 targets, 196 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: Preparing RunQueue
NOTE: Checking sstate mirror object availability (for 38 objects)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Tasks Summary: Attempted 872 tasks of which 857 didn't need to be rerun and all succeeded.
INFO: Copying Images from deploy to images
[INFO] successfully built bbexample-lt |
You have now successfully built the layer but you still need to include the binary produced into the kernel root file system
There are two options in order to do so
1. Edit your project
<BUILD_DIR>/
conf/local.conf file for YOCTO project
<plnx-proj-root>/meta-user/conf/petalinuxbsp.conf file for PetaLinux project and add
Code Block |
---|
|
# Use Below syntax For 2022.1 Release onwards
IMAGE_INSTALL_:append = " bbexample-lt"
# Use Below syntax For 2021.2 and Old Releases
IMAGE_INSTALL_append = " bbexample-lt" |
2. Adding a package to an image via a
.bbappendYou may wish to add specific packages to specific images, which is generally viewed as better practice. We are using
core-image-minimal bitbake recipe for this tip by creating file
core-image-minimal.bbappend. This .bbappend file is extending the original core-image-minimal recipe in order to include the layer build output into the Linux root file system.
Code Block |
---|
|
recipes-core/images/core-image-minimal.bbappend |
core-image-minimal.bbappend file content
Code Block |
---|
|
IMAGE_INSTALL += " bbexample-lt" |
1. Rebuild your layer
Code Block |
---|
|
$ petalinux-build -c bbexample_lt -x cleansstate |
2. Rebuild your kernel
Code Block |
---|
|
$ petalinux-build -c kernel |
3. Start qemu
Code Block |
---|
|
$ petalinux-boot --qemu --kernel |
4. Log on qemu and start the application
Code Block |
---|
|
root@plnx_arm:/# /usr/bin/bbexample
Hello Yocto World...
Hello World (from a shared library!) |
Patching the Linux Kernel of a PetaLinux Project
1. Copy the patch to project file
<plnx-proj-root>/project-spec/meta-user/recipes-kernel/linux/linux-xlnx directory.
2. Modify project file
<plnx-proj-root>/project-spec/meta-user/recipes-kernel/linux/linux-xlnx_%.bbappend to use the patch file by adding the patch file name to the SRC_URI
_append variable. If the variable does not exist in the file then add a new line with
For 2022.1 release onwards :
Code Block |
---|
|
SRC_URI:append = " file://0001-linux-driver-fix.patch"
FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:" |
For 2021.2 and old release :
Code Block |
---|
|
SRC_URI_append = " file://0001-linux-driver-fix.patch"
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" |
3. Make sure the priority for the meta-user layer is 7 in the project file <plnx-proj-root>/project-spec/meta-user/conf/layer.conf .
...
Any patches in the project will not be applied to an external source tree for the Linux kernel or u-boot. The user should apply patches to the external source tree. |
How to Modify inittab or getty in a PetaLinux Project
1. Create a sysvinit directory in meta-user layer as
Code Block |
---|
|
$ mkdir -p <plnx-proj-root>/project-spec/meta-user/recipes-core/sysvinit/sysvinit-inittab |
2. Create a sysvinit-inittab_%.bbappend file and your own inittab file or your inittab patch
Code Block |
---|
|
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-core/sysvinit/sysvinit-inittab_%.bbappend |
...
For 2022.1 release onwards :
Code Block |
---|
|
# For Files
SRC_URI:append = " file://inittab"
# For patches
SRC_URI:append = " file://inittab.patch" |
...
...
:prepend := "${THISDIR}/${PN}:" |
...
For 2021.2 and old release :
Code Block |
---|
|
# For Files
SRC_URI_append = " file://inittab"
# For patches
SRC_URI_append = " file://inittab.patch" |
...
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:" |
How to Patch the FSBL in a PetaLinux Project
...
1. Create a fsbl/embeddedsw and files directory in meta-user layer as
Code Block |
---|
|
$ mkdir -p <plnx-proj-root>/project-spec/meta-user/recipes-bsp/fsbl/files
## From 2021.1 onwards
$ mkdir -p <plnx-proj-root>/project-spec/meta-user/recipes-bsp/embeddedsw/ |
...
2. Copy patch files to <plnx-proj-root>/project-spec/meta-user/recipes-bsp/fsbl/files as
Code Block |
---|
|
$ cp 0001-FSBL.patch <plnx-proj-root>/project-spec/meta-user/recipes-bsp/fsbl/files
## From 2021.1 onwards
$ cp 0001-FSBL.patch <plnx-proj-root>/project-spec/meta-user/recipes-bsp/embeddedsw/files |
Note that patches should be generated based on the embeddedsw GIT repo which contains FSBL as the patches require the path into the repo to apply correctly.
3. Create a fsbl_%.bbappend file and add below content
Code Block |
---|
|
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-bsp/fsbl/fsbl_%.bbappend
## From 2021.1 onwards
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-bsp/embeddedsw/fsbl-firmware_%.bbappend |
For 2022.1 release onwards :
...
SRC_URI:append = " \
file://0001-FSBL.patch \
"
FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
#Add debug for FSBL(optional)
XSCTH_BUILD_DEBUG = "1"
#Enable appropriate FSBL debug or compiler flags
YAML_COMPILER_FLAGS:append = " -DXPS_BOARD_ZCU102" |
For 2021.2 and old release :
Code Block |
---|
|
SRC_URI_append = " \
file://0001-FSBL.patch \
"
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
#Add debug for FSBL(optional)
XSCTH_BUILD_DEBUG = "1"
#Enable appropriate FSBL debug or compiler flags
YAML_COMPILER_FLAGS_append = " -DXPS_BOARD_ZCU102" |
4. Remove the <plnx-proj-root>/components/plnx_workspace and clean your project workspace before rebuilding FSBL components
Code Block |
---|
|
$ petalinux-build -x |
...
...
...
...
...
...
...
onwards "petalinux-build -x mrproper" command will remove <plnx-proj-root>/components/plnx_workspace directory
$ rm -rf <plnx-proj-root>/components/plnx_workspace |
...
5. Rebuilding FSBL components
Code Block |
---|
|
$ petalinux-build - |
...
How to Patch the PMU Firmware/PLM/PSM Firmware in a PetaLinux Project
1. Create a pmu/pmu-firmware and files directory in meta-user layer as
Code Block |
---|
|
#For v2018.1 release onwards
$ mkdir -p <plnx-proj-root>/ |
...
project-spec/meta-user/recipes-bsp/pmu-firmware/files
#For 2021.1 release onwards
$ |
...
...
...
Code Block |
---|
|
$ petalinux-build -c bootloader |
How to Patch the PMU Firmware in a PetaLinux Project
...
...
project-spec/meta-user/recipes-bsp/embeddedsw/files |
2. Copy patch files to <plnx-proj-root>/project-spec/meta-user/recipes-bsp/pmu/files
...
as
Code Block |
---|
|
#For v2018.1 release onwards
$ |
...
...
support.patch <plnx-proj-root>/project-spec/meta-user/recipes-bsp/ |
...
...
3. Create a corresponding bbappend file to that recipe as below.
...
#For v2018.1 or later PetaLinux releases only
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-bsp/pmu |
...
-firmware/<bbappend file name>
#For |
...
...
...
...
...
vim <plnx-proj-root>/project-spec/meta-user/recipes-bsp/ |
...
embeddedsw/<bbappend file name> |
For 2022.1 release onwards :
...
...
Patch for PMUFW
SRC_URI:append = " file://0001-support.patch"
FILESEXTRAPATHS:prepend := "${THISDIR}/files:" |
For 2021.2 and old release :
Code Block |
---|
|
# Patch for PMUFW
|
...
...
SRC_URI_append = " file://0001-support.patch"
FILESEXTRAPATHS_prepend := "${THISDIR}/files:" |
5. Rebuilding PMUFW components
Code Block |
---|
|
$ petalinux-build -c pmufw (or)
$ petalinux-build -c psmfw (or)
$ petalinux-build -c plm |
Configuring the FSBL component in a PetaLinux Project
1. Create a fsbl bbappend file and add below content Code Block |
---|
|
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-bsp/fsbl/fsbl_%.bbappend
# From 2021.1 onwards
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-bsp/embeddedsw/fsbl-firmware_%.bbappend |
2. To enable debugs in FSBL: Code Block |
---|
|
#Add debug for FSBL
XSCTH_BUILD_DEBUG = "1" |
3. To add compiler flags in FSBL: Code Block |
---|
|
#Add compiler flags for FSBL
#For v2022.1 or later PetaLinux releases
YAML_COMPILER_FLAGS:append = " -DFSBL_PROT_BYPASS"
#For v2021.2 and old PetaLinux releases
YAML_COMPILER_FLAGS_append = " -DENABLEDFSBL_PROT_EM"
# Note: This is not required if you are using Yocto
# CAUTION!: EXTERNALXSCTSRC and EXTERNALXSCTSRC_BUILD is required only for 2018.2 and below petalinux releases
EXTERNALXSCTSRC = ""
EXTERNALXSCTSRC_BUILD = "" |
4. Remove the <plnx-proj-root>/components/plnx_workspace and clean your project workspace before rebuilding PMUFW components
4. To add BSP flags(secure mode) in FSBL:
Code Block |
---|
|
#Add BSP flags for FSBL
YAML_BSP_CONFIG += "secure_mode"
YAML_BSP_CONFIG[secure_mode] = "set,true" |
5. Build the FSBL
Code Block |
---|
|
$ petalinux-build -x mrproper
#Note: Inc fsbl |
Configuring the PMUFW component in a PetaLinux Project
1. Create a pmu-firmware_%.bbappend file and add below content
Code Block |
---|
|
#For v2018.1 or later PetaLinux release "petalinux-build -x mrproper" command will remove releases only
$ vim <plnx-proj-root>/components/plnx_workspace directory
$ rm -rf /project-spec/meta-user/recipes-bsp/pmu-firmware/pmu-firmware_%.bbappend
# From 2021.1 onwards
$ vim <plnx-proj-root>/components/plnx_workspace |
5. Rebuilding PMUFW componentsproject-spec/meta-user/recipes-bsp/embeddedsw/pmu-firmware_%.bbappend |
Code Block |
---|
|
$#Add petalinux-build -c pmufw |
Configuring the FSBL and PMUFW Debugs in a PetaLinux Project
Create a fsbl bbappend file and add below content Code Block |
---|
|
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-bsp/fsbl/fsbl_%.bbappend
# From 2021.1 onwards
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-bsp/embeddedsw/fsbl-firmware_%.bbappend |
To enable debugs in FSBL:debug for PMUFW
XSCTH_BUILD_DEBUG = "1" |
3. To add compiler flags in PMUFW, see PMU FW Build Flags:
Code Block |
---|
|
#Add debugcompiler flags for FSBL
XSCTH_BUILD_DEBUG = "1" |
To add compiler flags in FSBL: Code Block |
---|
|
#Add compiler flags for FSBL PMUFW
# From 2022.1 onwards
YAML_COMPILER_FLAGS:append = " -DDEBUG_MODE -DXPFW_DEBUG_DETAILED"
# For 2021.2 and old PetaLinux releases
YAML_COMPILER_FLAGS_append = " -DFSBL_PROT_BYPASS"DDEBUG_MODE -DXPFW_DEBUG_DETAILED" |
4. To add BSP flags(secure mode) in
FSBLPMUFW:
Code Block |
---|
|
#Add BSP flags for FSBLPMUFW
YAML_BSP_CONFIG += "secure_mode"
YAML_BSP_CONFIG[secure_mode] = "set,true" |
Create a pmu-firmware_%.bbappend file and add below content Code Block |
---|
|
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-bsp/pmu/pmu-firmware_%.bbappend
#For v2018.1 or later PetaLinux releases only
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-bsp/pmu-firmware/pmu-firmware_%.bbappend |
To enable debugs in PMUFW refer this https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/18841724/PMU+Firmware page for DEBUG flags list
5. To add BSP flags(debug mode) in PMUFW: For example if you want to enable https://github.com/Xilinx/embeddedsw/blob/release-2018.3/lib/sw_apps/zynqmp_pmufw/misc/xfpga_config.h#L34 debug is Xil BSP libraries
Code Block |
---|
|
#Add debugBSP flags for PMUFW
XSCTHYAML_BUILDBSP_DEBUGCONFIG += "1" |
To add compiler flags in PMUFW, see PMU FW Build Flags: Info |
---|
Note that the method of loading the PMUFW can prevent early prints (during code initialization) from being output. See PMU Firmware > Using FSBL to load PMUFW for additional details.debug_mode"
YAML_BSP_CONFIG[debug_mode] = "set,true" |
6. By pass PMUFW debug logs on different UART console: Code Block |
---|
|
#Add compiler flags for PMUFW# From 2022.1 PetaLinux Release onwards
YAML_COMPILERSERIAL_FLAGSCONSOLE_appendSTDIN:zynqmp = " -DDEBUG_MODE -DXPFW_DEBUG_DETAILED" |
To add BSP flags(secure mode) in PMUFW: Code Block |
---|
|
#Add BSP flags for PMUFW
YAML_BSP_CONFIG += "secure_mode"
YAML_BSP_CONFIG[secure_mode] = "set,true" |
To add BSP flags(debug mode) in PMUFW: For example if you want to enable https://github.com/Xilinx/embeddedsw/blob/release-2018.3/lib/sw_apps/zynqmp_pmufw/misc/xfpga_config.h#L34 debug is Xil BSP librariespsu_uart_1"
YAML_SERIAL_CONSOLE_STDOUT:zynqmp = "psu_uart_1"
# For 2021.2 and old releases
YAML_SERIAL_CONSOLE_STDIN_zynqmp = "psu_uart_1"
YAML_SERIAL_CONSOLE_STDOUT_zynqmp = "psu_uart_1" |
7. Build the PMUFW Code Block |
---|
|
$ petalinux-build -c pmufw |
Configuring the PLM component in a PetaLinux Project
1. Create a plm-firmware_%.bbappend file and add below content
Code Block |
---|
|
#Add$ BSP flags for PMUFW
YAML_BSP_CONFIG += "debug_mode"
YAML_BSP_CONFIG[debug_mode] = "set,true" |
By pass PMUFW debug logs on different UART console:vim <plnx-proj-root>/project-spec/meta-user/recipes-bsp/embeddedsw/plm-firmware_%.bbappend |
2. To add BSP flags(to enable USB boot mode) in PLM: For more option see https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/2037088327/Versal+Platform+Loader+and+Manager#PLM-Build-Flags
Code Block |
---|
|
YAML_SERIAL_CONSOLE_STDIN_forcevariable = "psu_uart_1"
YAML_SERIAL_CONSOLE_STDOUT_forcevariable = "psu_uart_1" |
Remove the <plnx-proj-root>/components/plnx_workspace and clean you project workspace before rebuilding FSBL or PMUFW components Code Block |
---|
|
$ petalinux-build -x mrproper
#Note: In v2018.1 or later PetaLinux release "petalinux-build -x mrproper" command will remove <plnx-proj-root>/components/plnx_workspace directory
$ rm -rf <plnx-proj-root>/components/plnx_workspace
$ petalinux-build#Add BSP flags for PLM. Here USB boot mode is enabled and debug level changed to level0 (minimal)
#Alternatively, each of these two parameters can be configured separately
YAML_BSP_CONFIG += "plm_usb_en plm_dbg_lvl"
YAML_BSP_CONFIG[plm_usb_en] = "set,true"
YAML_BSP_CONFIG[plm_dbg_lvl] = "set,level0" |
3. To build PLM
Code Block |
---|
|
$ petalinux-build -c plm |
How to Update psu_init Files in PetaLinux Project
Info |
---|
Note: PSU_INIT files are generated based on HDF or XSA parsing, Hence these files can't be patched on top of embedded_sw repo using Yocto SRC_URI variable. Alternatively we can update these files by editing <plnx-proj-root>/project-spec/hw-description/psu_init.c and copy to FSBL build workspace during do_compile_prepend bitbake task. |
1. Modify <plnx-proj-root>/project-spec/hw-description/psu_init.c file as per your requirement
2. Create a FSBL bbappend file under <plnx-proj-root>/project-spec/meta-user/recipes-bsp/embeddedsw/fsbl-firmware_%.bbappend and add below content to update psu_init.c changes to FSBL
Code Block |
---|
|
# For 2018.2 and below versions
do_compile_prepend(){
install -m 0644 ${TOPDIR}/../project-spec/hw-description/psu_init.c ${TOPDIR}/../components/plnx_workspace/fsbl/fsbl_hwproj/psu_init.c
}
# For 2018.3 and later versions we removed FSBL and PMUFW external workspace from <plnx-proj-root>/components/plnx_workspace directory
# to align Yocto patching mechanism. Hence we are copying the files to build workspace(${B})
# https://github.com/Xilinx/meta-xilinx-tools/blob/rel-v2018.3/classes/xsctbase.bbclass#L14
do_compile_prepend(){
install -m 0644 ${TOPDIR}/../project-spec/hw-description/psu_init.c ${B}/fsbl/psu_init.c
} |
How to Add Pre-built Libraries in PetaLinux or Yocto Projects
1. Create an application/recipe and copy prebuilt library and header files with the following commands. Assuming prebuilt library name is libcpsample.so.1.0.1. In PetaLinux Flow:
Code Block |
---|
|
$ petalinux-create -t apps --template install --name libcpsample --enable
$ cp libcpsample.so.1.0.1 <plnx-proj-root>/project-spec/meta-user/recipes-apps/libcpsample/files
$ cp cpsample.h <plnx-proj-root>/project-spec/meta-user/recipes-apps/libcpsample/files |
(or) You can use the below single command to achieve the above functionality. Code Block |
---|
|
$ petalinux-create -t apps --template install --name libcpsample --enable --srcuri "<path-to-dir>/libcpsample.so.1.0.1 <path-to-dir>/cpsample.h>" |
In Yocto Flow:
Code Block |
---|
|
$ mkdir -p <layer-path>/recipes-apps/libcpsample/files
$ touch <layer-path>/recipes-apps/libcpsample/libcpsample.bb
$ cp libcpsample.so.1.0.1 <layer-path>/recipes-apps/libcpsample/files
$ cp cpsample.h <layer-path>/recipes-apps/libcpsample/files |
2. Add the below content to recipe(bb) fileto update psu_init.c changes to FSBL
Code Block |
---|
|
# For 2018.2 and below versions
do_compile_prepend(){
install -m 0644 ${TOPDIR}/../project-spec/hw-description/psu_init.c ${TOPDIR}/../components/plnx_workspace/fsbl/fsbl_hwproj/psu_init.c
}
# For 2018.3 and later versions we removed FSBL and PMUFW external workspace from <plnx-proj-root>/components/plnx_workspace directory
# to align Yocto patching mechanism. Hence we are copying the files to build workspace(${B})
# https://github.com/Xilinx/meta-xilinx-tools/blob/rel-v2018.3/classes/xsctbase.bbclass#L14
do_compile_prepend(){
install -m 0644 ${TOPDIR}/../project-spec/hw-description/psu_init.c ${B}/fsbl/psu_init.c
}
# For 2022.1 release onwards
do_compile:prepend(){
install -m 0644 ${TOPDIR}/../project-spec/hw-description/psu_init.c ${B}/fsbl/psu_init.c
} |
How to Add Pre-built Libraries in PetaLinux or Yocto Projects
1. Create an application/recipe and copy prebuilt library and header files with the following commands. Assuming prebuilt library name is libcpsample.so.1.0.1. In PetaLinux Flow:
Code Block |
---|
|
$ petalinux-create -t apps --template install --name libcpsample --enable
$ cp libcpsample.so.1.0.1 <plnx-proj-root>/project-spec/meta-user/recipes-apps/libcpsample/files
$ cp cpsample.h <plnx-proj-root>/project-spec/meta-user/recipes-apps/libcpsample/files |
(or) You can use the below single command to achieve the above functionality. Code Block |
---|
|
$ petalinux-create -t apps --template install --name libcpsample --enable --srcuri "<path-to-dir>/libcpsample.so.1.0.1 <path-to-dir>/cpsample.h>" |
In Yocto Flow:
Code Block |
---|
|
$ mkdir -p <layer-path>/recipes-apps/libcpsample/files
$ touch <layer-path>/recipes-apps/libcpsample/libcpsample.bb
$ cp libcpsample.so.1.0.1 <layer-path>/recipes-apps/libcpsample/files
$ cp cpsample.h <layer-path>/recipes-apps/libcpsample/files |
2. Add the below content to recipe(bb) file
For 2022.1 PetaLinux release onwards:
Code Block |
---|
|
#
# This file is the libcpsample recipe.
#
SUMMARY = "Sample pre-built library copy to rootfs"
SECTION = "libs"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
SRC_URI = " \
file://libcpsample.so.1.0.1 \
file://cpsample.h \
"
S = "${WORKDIR}"
# Add dependency libraries if any
# for example DEPENDS = "libpcap"
# If you need to create a symbolic link using the pre-built libraries you should use oe_soinstall.
# This copies libraries to "{TARGET_ROOTFS}/usr/lib" directory and create a symlink as
# lrwxrwxrwx libcpsample.so.1.0 -> libcpsample.so.1.0.1
# -rwxr-xr-x libcpsample.so.1.0.1
do_install() {
install -d ${D}${libdir}
oe_soinstall ${S}/libcpsample.so.1.0.1 ${D}${libdir}
install -d -m 0655 ${D}${includedir}/CPSAMPLE
install -m 0644 ${S}/*.h ${D}${includedir}/CPSAMPLE/
}
# Inhibit warnings about files being stripped
INSANE_SKIP:${PN} = "ldflags"
INSANE_SKIP:${PN} = "already-stripped"
# If you don't have .h file to copy to /usr/include add something like below
# FILES:${PN} = "${libdir}/*.so.*"
FILES:${PN} = "${libdir}/*.so.* ${includedir}/*"
FILES:${PN}-dev = "${libdir}/*.so" |
For 2021.2 and Below PetaLinux releases:
Code Block |
---|
|
#
# This file is the libcpsample recipe.
#
SUMMARY = "Sample pre-built library copy to rootfs"
SECTION = "libs"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
SRC_URI = " \
file://libcpsample.so.1.0.1 \
file://cpsample.h \
"
S = "${WORKDIR}"
# Add dependency libraries if any
# for example DEPENDS = "libpcap"
# If you need to create a symbolic link using the pre-built libraries you should use oe_soinstall.
# This copies libraries to "{TARGET_ROOTFS}/usr/lib" directory and create a symlink as
# lrwxrwxrwx libcpsample.so.1.0 -> libcpsample.so.1.0.1
# -rwxr-xr-x libcpsample.so.1.0.1
do_install() {
install -d ${D}${libdir}
oe_soinstall ${S}/libcpsample.so.1.0.1 ${D}${libdir}
install -d -m 0655 ${D}${includedir}/CPSAMPLE
install -m 0644 ${S}/*.h ${D}${includedir}/CPSAMPLE/
}
# Inhibit warnings about files being stripped
INSANE_SKIP_${PN} = "ldflags"
INSANE_SKIP_${PN} = "already-stripped"
# If you don't have .h file to copy to /usr/include add something like below
# FILES_${PN} = "${libdir}/*.so.*"
FILES_${PN} = "${libdir}/*.so.* ${includedir}/*"
FILES_${PN}-dev = "${libdir}/*.so" |
4. Build the pre-built library recipe Code Block |
---|
|
$ petalinux-build -c rootfs |
Creating Libraries in a PetaLinux Project
1. Create a library using PetaLinux tools Code Block |
---|
|
$ petlainux-create -t apps --template c --name libsample --enable |
2. Modify the libsample.bb recipe file <plnx-proj-root>/project-spec/meta-user/recipes-apps/libsample/libsample.bb as For 2022.1 PetaLinux release onwards:
Code Block |
---|
|
#
# This file is the libsample recipe.
#
SUMMARY = "Simple libsample application"
SECTION = "libs"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
SRC_URI = " \
file://sample.c \
file://sample.h \
file://Makefile \
"
S = "${WORKDIR}"
PACKAGE_ARCH = "${MACHINE_ARCH}"
PROVIDES = "sample"
TARGET_CC_ARCH += "${LDFLAGS}"
do_install() {
install -d ${D}${libdir}
install -d ${D}${includedir}
oe_libinstall -so libsample ${D}${libdir}
# This is optional and depends if you have any headers to copied along with libraries
# This example includes sample.h to to copied to <TARGET_ROOTFS>/usr/lib/SAMPLE/sample.h
install -d -m 0655 ${D}${includedir}/SAMPLE
install -m 0644 ${S}/*.h ${D}${includedir}/SAMPLE/
}
FILES:${PN} = "${libdir}/*.so.* ${includedir}/*"
FILES:${PN}-dev = "${libdir}/*.so" |
For 2021.2 and Below PetaLinux releases: Code Block |
---|
|
#
# This file is the libcpsamplelibsample recipe.
#
SUMMARY = "SampleSimple pre-built library copy to rootfslibsample application"
SECTION = "libs"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI = " \
file://libcpsample.so.1.0.1 \ file://cpsamplesample.hc \
" S = "${WORKDIR}" # Add dependency libraries if any
# for example DEPENDS = "libpcap" file://sample.h \
# If you need to create a symbolic link using the pre-built libraries you should use oe_soinstall.
# This copies libraries to "{TARGET_ROOTFS}/usr/lib" directory and create a symlink as
# lrwxrwxrwx libcpsample.so.1.0 -> libcpsample.so.1.0.1
# -rwxr-xr-x libcpsample.so.1.0.1file://Makefile \
"
S = "${WORKDIR}"
PACKAGE_ARCH = "${MACHINE_ARCH}"
PROVIDES = "sample"
TARGET_CC_ARCH += "${LDFLAGS}"
do_install() {
install -d ${D}${libdir}
install oe_soinstall-d ${S}/libcpsample.so.1.0.1D}${includedir}
oe_libinstall -so libsample ${D}${libdir}{libdir}
# This is optional and depends if you have any headers to copied along with libraries
# This example includes sample.h to to copied to <TARGET_ROOTFS>/usr/lib/SAMPLE/sample.h
install -d -m 0655 ${D}${includedir}/CPSAMPLESAMPLE
install -m 0644 ${S}/*.h ${D}${includedir}/CPSAMPLESAMPLE/
}
# Inhibit warnings about files being stripped
INSANE_SKIP_${PN} = "ldflags"
INSANE_SKIP_${PN} = "already-stripped"
# If you don't have .h file to copy to /usr/include add something like below
# FILES_${PN} = "${libdir}/*.so.*"
FILES_${PN} = "${libdir}/*.so.* ${includedir}/*"
FILES_${PN}-dev = "${libdir}/*.so" |
4. Build the pre-built library recipe Code Block |
---|
|
$ petalinux-build -c rootfs |
Creating Libraries in a PetaLinux Project
1. Create a library using PetaLinux tools Code Block |
---|
|
$ petlainux-create -t apps --template c --name libsample --enable |
2. Modify the libsample.bb recipe file <plnx-proj-root>/project-spec/meta-user/recipes-apps/libsample/libsample.bb as Code Block |
---|
|
#
# This file is the libsample recipe.
#
SUMMARY = "Simple libsample application"
SECTION = "libs"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI = " \
file://sample.c \
file://sample.h \
file://Makefile \
"
S = "${WORKDIR}"
PACKAGE_ARCH = "${MACHINE_ARCH}"
PROVIDES = "sample"
TARGET_CC_ARCH += "${LDFLAGS}"
do_install() {
install -d ${D}${libdir}
install -d ${D}${includedir}
oe_libinstall -so libsample ${D}${libdir}
# This is optional and depends if you have any headers to copied along with libraries
# This example includes sample.h to to copied to <TARGET_ROOTFS>/usr/lib/SAMPLE/sample.hFILES_${PN} = "${libdir}/*.so.* ${includedir}/*"
FILES_${PN}-dev = "${libdir}/*.so" |
3. Modify the <plnx-proj-root>/project-spec/meta-user/recipes-apps/libsample/files/Makefile generated from PetaLinux tools as Code Block |
---|
|
APP = sample
LIBSOURCES=*.c
OUTS = *.o
NAME := sample
MAJOR = 1.0
MINOR = 1
VERSION = $(MAJOR).$(MINOR)
all: lib$(NAME).so
lib$(NAME).so.$(VERSION): $(OUTS)
$(CC) $(LDFLAGS) $(OUTS) -shared -Wl,-soname,lib$(NAME).so.$(MAJOR) -o lib$(NAME).so.$(VERSION)
lib$(NAME).so: lib$(NAME).so.$(VERSION)
rm -f lib$(NAME).so.$(MAJOR) lib$(NAME).so
ln -s lib$(NAME).so.$(VERSION) lib$(NAME).so.$(MAJOR)
ln -s lib$(NAME).so.$(MAJOR) lib$(NAME).so
%.o: %.c
$(CC) $(CFLAGS) -c -fPIC $(LIBSOURCES)
clean:
rm -rf *.o *.so *.so.* |
4. Build the library recipe Code Block |
---|
|
$ petalinux-build -c libsample |
Creating Apps(which uses libraries) in PetaLinux Project
1. Create a library using PetaLinux tools Code Block |
---|
|
$ petlainux-create -t apps --template c --name sampleapp --enable |
2. Modify the sampleapp.bb recipe file <plnx-proj-root>/project-spec/meta-user/recipes-apps/sampleapp/sampleapp.bb as For 2022.1 PetaLinux release onwards:
Code Block |
---|
|
#
# This file is the sampleapp recipe.
#
SUMMARY = "Simple sampleapp application"
SECTION = "PETALINUX/apps"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
SRC_URI = " \
file://sampleapp.c \
"
S = "${WORKDIR}"
DEPENDS += " libsample"
#This uses libsample.so.1.0.1 (-lsample)
do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} -o sampleapp sampleapp.c -lsample
}
do_install() {
install -d ${D}${bindir}
install -d -m 0755 0655sampleapp ${D}${includedir}/SAMPLE
install -m 0644 ${S}/*.h ${D}${includedir}/SAMPLE/
}
FILES_${PN} = "${libdir}/*.so.* ${includedir}/*"
FILES_${PN}-dev = "${libdir}/*.so" |
3. Modify the <plnx-proj-root>/project-spec/meta-user/recipes-apps/libsample/files/Makefile generated from PetaLinux tools as Code Block |
---|
|
APP = sample
LIBSOURCES=*.c
OUTS = *.o
NAME := sample
MAJOR = 1.0
MINOR = 1
VERSION = $(MAJOR).$(MINOR)
all: lib$(NAME).so
lib$(NAME).so.$(VERSION): $(OUTS)
$(CC) $(LDFLAGS) $(OUTS) -shared -Wl,-soname,lib$(NAME).so.$(MAJOR) -o lib$(NAME).so.$(VERSION)
lib$(NAME).so: lib$(NAME).so.$(VERSION)
rm -f lib$(NAME).so.$(MAJOR) lib$(NAME).so
ln -s lib$(NAME).so.$(VERSION) lib$(NAME).so.$(MAJOR)
ln -s lib$(NAME).so.$(MAJOR) lib$(NAME).so
%.o: %.c
$(CC) $(CFLAGS) -c -fPIC $(LIBSOURCES)
clean:
rm -rf *.o *.so *.so.* |
4. Build the library bindir}
}
FILES:${PN} += "sampleapp" |
For 2021.2 and Below PetaLinux releases:
Code Block |
---|
|
#
# This file is the sampleapp recipe.
#
SUMMARY = "Simple sampleapp application"
SECTION = "PETALINUX/apps"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
SRC_URI = " \
file://sampleapp.c \
"
S = "${WORKDIR}"
DEPENDS += " libsample"
#This uses libsample.so.1.0.1 (-lsample)
do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} -o sampleapp sampleapp.c -lsample
}
do_install() {
install -d ${D}${bindir}
install -d -m 0755 sampleapp ${D}${bindir}
}
FILES_${PN} += "sampleapp" |
3. Modify the <plnx-proj-root>/project-spec/meta-user/recipes-apps/libsample/files/sampleapp.c generated from PetaLinux tools as Code Block |
---|
|
#include <stdio.h>
#include <SAMPLE/sample.h> // From above libs <TARGET_ROOTFS>/usr/lib/SAMPLE/sample.h
int main(int argc, char **argv)
{
printf("Hello World!\n");
sample_hello();
return 0;
} |
4. Build the apps recipe
Code Block |
---|
|
$ petalinux-build -c libsample |
Creating Apps(which uses libraries) in PetaLinux ProjectHow to Auto Run Application at Startup
1. Create a library using PetaLinux tools
Code Block |
---|
|
$ petlainuxpetalinux-create -t apps --template cinstall -n myapp-nameinit sampleapp --enable |
2.
Modify the sampleapp.bb recipe Create the file <plnx-proj-root>/project-spec/meta-user/recipes-apps/myapp-init/files/myapp-init.service.
Code Block |
---|
|
[Unit]
Description=myapp-init
[Service]
ExecStart=/usr/bin/myapp-init
StandardOutput=journal+console
[Install]
WantedBy=multi-user.target |
3. Edit the file <plnx-proj-root>/project-spec/meta-user/recipes-apps/
sampleappmyapp-init/
sampleappmyappinit.bb
as. The file should look like the following:
For 2022.1 PetaLinux release onwards:
Code Block |
---|
|
#
# This#this file is the sampleappmyapp-init recipe.
#
SUMMARY = "Simple sampleapp application"
SECTION = "PETALINUX/apps"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302myapp-init application"
SECTION = "PETALINUX/apps"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
SRC_URI = "file://myapp-init \
file://myapp-init.service \
"
S = "${WORKDIR}"
FILESEXTRAPATHS_:prepend := "${THISDIR}/files:"
SRC_URIinherit update-rc.d systemd
INITSCRIPT_NAME = "myapp-init"
\INITSCRIPT_PARAMS = "start 99 S ."
SYSTEMD_PACKAGES = file://sampleapp.c \
"${PN}"
SYSTEMD_SERVICE:${PN} = "myapp-init.service"
SYSTEMD_AUTO_ENABLE:${PN} = "enable"
do_install() {
" S =if "${WORKDIR}"
DEPENDS += " libsample"
#This uses libsample.so.1.0.1 (-lsample)
do_compile() {
${CC} ${CFLAGS} ${LDFLAGS} -o sampleapp sampleapp.c -lsample
}
do_install() {${@bb.utils.contains('DISTRO_FEATURES', 'sysvinit', 'true', 'false', d)}; then
install -d ${D}${sysconfdir}/init.d/
install -d ${D}${bindir} install -d -m 0755 sampleapp${WORKDIR}/myapp-init ${D}${bindirsysconfdir}/init.d/
} FILES_${PN} += "sampleapp" |
3. Modify the <plnx-proj-root>/project-spec/meta-user/recipes-apps/libsample/files/sampleapp.c generated from PetaLinux tools as Code Block |
---|
|
#include <stdio.h> #include <SAMPLE/sample.h> // From above libs <TARGET_ROOTFS>/usr/lib/SAMPLE/sample.h fi
int main(int argc, char **argv)
{install -d ${D}${bindir}
printf("Hello World!\n");
sample_hello(); install -m 0755 ${WORKDIR}/myapp-init ${D}${bindir}/
return 0; } |
4. Build the apps recipe Code Block |
---|
|
$ petalinux-build -c sampleapp |
How to Auto Run Application at Startup
1. Create a library using PetaLinux tools
Code Block |
---|
|
$ petalinux-create -t apps --template install -n myapp-init --enable |
2. Edit the file <plnx-proj-root>/project-spec/meta-user/recipes-apps/myapp-init/myappinit.bb. The file should look like the following install -d ${D}${systemd_system_unitdir}
install -m 0644 ${WORKDIR}/myapp-init.service ${D}${systemd_system_unitdir}
}
FILES:${PN} += "${@bb.utils.contains('DISTRO_FEATURES','sysvinit','${sysconfdir}/*', '', d)}" |
For 2021.2 and Below PetaLinux releases:
Code Block |
---|
|
#this file is the myapp-init recipe.
#
SUMMARY = "Simple myapp-init application"
SECTION = "PETALINUX/apps"
LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://${COMMON_LICENSE_DIR}/MIT;md5=0835ade698e0bcf8506ecda2f7b4f302"
SRC_URI = "file://myapp-init \
"
S = "${WORKDIR}"
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
inherit update-rc.d
INITSCRIPT_NAME = "myapp-init"
INITSCRIPT_PARAMS = "start 99 S ."
do_install() {
install -d ${D}${sysconfdir}/init.d
install -m 0755 ${S}/myapp-init ${D}${sysconfdir}/init.d/myapp-init
}
FILES_${PN} += "${sysconfdir}/*"
|
34. To run myapp as daemon, edit the file <plnx-proj-root>/project-spec/meta-user/recipes-apps/myapp-init/files/myapp-init.
Note |
---|
Below step required only if you are using SYSTEMV as INITMANAGER. |
Code Block |
---|
|
#!/bin/sh
DAEMON=/usr/bin/myapp-init
start ()
{
echo " Starting myapp-init"
start-stop-daemon -S -o --background -x $DAEMON
}
stop ()
{
echo " Stoping myapp-init"
start-stop-daemon -K -x $DAEMON
}
restart()
{
stop
start
}
[ -e $DAEMON ] || exit 1
case "$1" in
start)
start; ;;
stop)
stop; ;;
restart)
restart; ;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
esac
exit $? |
4. Build the project
Code Block |
---|
|
petalinux-build |
How to Auto Mount SD card in Yocto Recipes
1. Create a base-files directory in meta-user layer as
Code Block |
---|
|
$ mkdir -p <plnx-proj-root>/project-spec/meta-user/recipes-core/base-files |
2. Create a base-files_%.bbappend file and add below content
Code Block |
---|
|
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-core/base-files/base-files_%.bbappend
#base-files_%.bbappend content
dirs755 += "/media/card"
do_install_append() {
sed -i '/mmcblk0p1/s/^#//g' ${D}${sysconfdir}/fstab
} |
3. Rebuild rootfs
Code Block |
---|
|
$ petalinux-build |
Method 1: Append auto eth1 to existing interfaces file
1. Create a init-ifupdown directory in meta-user layer as
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ mkdir -p <plnx-proj-root>/project-spec/meta-user/recipes-core/init-ifupdown/ |
2. Create a
init_ifupdown_%.bbappend file and add below content
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-core/init-ifupdown/init-ifupdown_%.bbappend
# init-ifupdown_%.bbappend content
_%.bbappend content
#For 2022.1 release onwards
do_install:append() {
sed -i '/iface eth0 inet dhcp/ a auto eth1' ${D}${sysconfdir}/network/interfaces
}
#For 2021.2 and old releases
do_install_append() {
sed -i '/iface eth0 inet dhcp/ a auto eth1' ${D}${sysconfdir}/network/interfaces
} |
3. Rebuild rootfs
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ petalinux-build |
Method 2: Use your own interfaces file
1. Create a init-ifupdown directory in meta-user layer as
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ mkdir -p <plnx-proj-root>/project-spec/meta-user/recipes-core/init-ifupdown/files |
2. Create your own network interface file as show below
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-core/init-ifupdown/files/myinterfaces
# myinterfaces content
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
auto lo
iface lo inet loopback
# Wireless interfaces
iface wlan0 inet dhcp
wireless_mode managed
wireless_essid any
wpa-driver wext
wpa-conf /etc/wpa_supplicant.conf
iface atml0 inet dhcp
# Wired or wireless interfaces
auto eth0
iface eth0 inet dhcp
# Add auto config for eth1
auto eth1
iface eth1 inet dhcp
# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.0
network 192.168.7.0
gateway 192.168.7.1
# Bluetooth networking
iface bnep0 inet dhcp |
3. Create a init_ifupdown_%.bbappend file and add below content
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-core/init-ifupdown/init-ifupdown_%.bbappend
# init-ifupdown_%.bbappend content
SRC_URI += " \
file://myinterfaces \
"
# For 2022.1 release onwards
FILESEXTRAPATHS:prepend := "${THISDIR}/files:"
# For 2021.2 and old releases
FILESEXTRAPATHS_prepend := "${THISDIR}/files:"
# Overwrite interface file with myinterface file in rootfs
# For 2022.1 release onwards
do_install:append() {
install FILESEXTRAPATHS_prepend := "-m 0644 ${THISDIRWORKDIR}/files:"
# Overwrite interface file with myinterface file in rootfs
myinterfaces ${D}${sysconfdir}/network/interfaces
}
#For 2021.2 and old releases
do_install_append() {
install -m 0644 ${WORKDIR}/myinterfaces ${D}${sysconfdir}/network/interfaces
} |
4. Rebuild rootfs
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ petalinux-build |
...
Create a petalinux-user-image.bbappend file in meta-user layer as show below if doesn't exists(Note: Don't use project-spec/meta-user/recipes-core/images/petalinux-image-full.bbappend(2018.3 or later) or petalinux-image.bbappend(2018.2 or below))
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-core/images/petalinux-user-image.bbappend |
Create a post process function as shown below in petalinux-user-image.bbappend
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
title | petalinux-user-image.bbappend |
---|
|
# petalinux-user-image.bbappend content
# Auto DHCP for second network interface
rootfs_postprocess_function() {
if [ -e ${IMAGE_ROOTFS}/etc/network/interfaces ]; then
sed -i '/iface eth0 inet dhcp/ a auto eth1' ${IMAGE_ROOTFS}/etc/network/interfaces
fi
}
auto eth1' ${IMAGE_ROOTFS}/etc/network/interfaces
fi
}
# For 2022.1 PetaLinux release onwards:
ROOTFS_POSTPROCESS_COMMAND:append = " \
rootfs_postprocess_function; \
"
For 2021.2 and Below PetaLinux releases:
ROOTFS_POSTPROCESS_COMMAND_append = " \
rootfs_postprocess_function; \
" |
Clean petalinux-user-image sstate and rebuild petalinux-user-image recipe.
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ petalinux-build -x cleansstate
$ petalinux-build |
...
- First step is to find the recipe directory hierarchy, search the recipe in http://layers.openembedded.org/layerindex/branch/thud/recipes/
- sysvinit is categorized in meta/recipes-core/sysvinit
Create a directory recipes-core/sysvinit directory in <plnx-porj-root>/project-spec/meta-user
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ mkdir -p <plnx-proj-root>/project-spec/meta-user/recipes-core/sysvinit |
Create a sysvinit_%.bbappend file. Note: The % wildcard is actually allow matching of the name and version up to the point of encountering the %. This approach will allow for matching of the major or major.minor. version of recipes.
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ vim <plnx-proj-root>/project-spec/meta-user/recipes-core/sysvinit/sysvinit_%.bbappend |
Now enable verbose for sysvinit recipe (refer http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-core/sysvinit/sysvinit/rcS-default?h=thud#n15)
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
title | sysvinit_%.bbappend |
---|
|
# sysvinit_%.bbappend content/openembedded-core/tree/meta/recipes-core/sysvinit/sysvinit/rcS-default?h=thud#n15)
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
title | sysvinit_%.bbappend |
---|
|
# sysvinit_%.bbappend content
# For 2022.1 PetaLinux release onwards:
do_install:prepend () {
sed -i 's/VERBOSE=no/VERBOSE=yes/' ${WORKDIR}/rcS-default
}
# For 2021.2 and Below PetaLinux releases:
do_install_prepend () {
sed -i 's/VERBOSE=no/VERBOSE=yes/' ${WORKDIR}/rcS-default
} |
Clean and rebuild sysvinit
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ petalinux-build -c sysvinit -x cleanall
$ petalinux-build -c sysvinit |
...
By default hwcodecs are enabled in petalinux project when zynqmp ev device xsa is parsed while creating the project. To disable hwcodecs add below variable in <plnx-proj-root>/project-spec/meta-user/conf/petaliuxbsp.conf
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
# For 2022.1 PetaLinux release onwards:
IMAGE_FEATURES:remove = "hwcodecs"
# For 2021.2 and Below PetaLinux releases:
IMAGE_FEATURES_remove = "hwcodecs" |
Clean and rebuild complete project.
Code Block |
---|
language | bash |
---|
theme | Midnight |
---|
|
$ petalinux-build -x mrproper
$ petalinux-build |
...