Hi Mender community,
I’m working on integrating Mender into a custom Yocto project based on Xilinx PetaLinux 2020.2, which uses Yocto Project Dunfell (3.1). I’m trying to add Mender support to a minimal image (petalinux-image-minimal) targeting a custom board. I’m facing multiple issues and would appreciate guidance from others who may have successfully done this with Xilinx-based workflows.
Environment Details:
Yocto Base: PetaLinux 2020.2 (Dunfell 3.1)
Mender Layer: meta-mender (branch: dunfell)
Image: petalinux-image-minimal
Kernel: linux-xlnx_2020.2.bb
U-Boot: Customized u-boot-xlnx from GitHub, patched for Mender
Build Host: Ubuntu 20.04 (VM)
Current Status:
- Cloned
meta-menderintosources/and addedmeta-mender-coretobblayers.conf. - Configured
local.confwith recommended Mender variables (e.g.,MENDER_STORAGE_DEVICE,MENDER_FEATURES_ENABLE, etc.). - Patched and pinned
u-boot-xlnxto a specific tag:xlnx_rebase_v2020.01_2020.2 - Added required device tree entry for the kernel via
KERNEL_DEVICETREE.
Error:
No rule to make target ‘arch/arm/boot/dts/morey-ngx-t-revb-system.dtb’
Any help or pointers would be greatly appreciated. Let me know if specific logs or files would help clarify.
— Alex Tollola
#
# This file is your local configuration file and is where all local user settings
# are placed. The comments in this file give some guide to the options a new user
# to the system might want to change but pretty much any configuration option can
# be set in this file. More adventurous users can look at local.conf.extended
# which contains other examples of configuration which can be placed in this file
# but new users likely won't need any of them initially.
#
# Lines starting with the '#' character are commented out and in some cases the
# default values are provided as comments to show people example syntax. Enabling
# the option is a question of removing the # character and making any change to the
# variable as required.
# BASE = "${COREBASE}/../.."
#
# Machine Selection
#
# You need to select a specific machine to target the build with. There are a selection
# of emulated machines available which can boot and run in the QEMU emulator:
#
# This sets the default machine if no other machine is selected:
MACHINE ??= "morey-ngx-t-revb"
#
# Where to place downloads
#
# During a first build the system will download many different source code tarballs
# from various upstream projects. This can take a while, particularly if your network
# connection is slow. These are all stored in DL_DIR. When wiping and rebuilding you
# can preserve this directory to speed up this part of subsequent builds. This directory
# is safe to share between multiple builds on the same machine too.
#
# The default is a downloads directory under TOPDIR which is the build directory.
DL_DIR ?= "/home/${USER}/Yocto_downloads"
#
# Where to place shared-state files
#
# BitBake has the capability to accelerate builds based on previously built output.
# This is done using "shared state" files which can be thought of as cache objects
# and this option determines where those files are placed.
#
# You can wipe out TMPDIR leaving this directory intact and the build would regenerate
# from these files if no changes were made to the configuration. If changes were made
# to the configuration, only shared state files where the state was still valid would
# be used (done using checksums).
#
# The default is a sstate-cache directory under TOPDIR.
#
# SSTATE_DIR ?= "${BASE}/sstate-cache"
#
# Where to place the build output
#
# This option specifies where the bulk of the building work should be done and
# where BitBake should place its temporary files and output. Keep in mind that
# this includes the extraction and compilation of many applications and the toolchain
# which can use Gigabytes of hard disk space.
#
# The default is a tmp directory under TOPDIR.
#
#TMPDIR = "${TOPDIR}/tmp"
#
#TMPDIR_versal = "${TOPDIR}/tmp-versal"
#
# Default policy config
#
# The distribution setting controls which policy settings are used as defaults.
# The default value is fine for general Yocto project use, at least initially.
# Ultimately when creating custom policy, people will likely end up subclassing
# these defaults.
#
DISTRO ?= "petalinux"
#
# Package Management configuration
#
# This variable lists which packaging formats to enable. Multiple package backends
# can be enabled at once and the first item listed in the variable will be used
# to generate the root filesystems.
# Options are:
# - 'package_deb' for debian style deb files
# - 'package_ipk' for ipk files are used by opkg (a debian style embedded package manager)
# - 'package_rpm' for rpm style packages
# E.g.: PACKAGE_CLASSES ?= "package_rpm package_deb package_ipk"
# We default to rpm:
PACKAGE_CLASSES ?= "package_rpm"
#
# SDK/ADT target architecture
#
# This variable specifies the architecture to build SDK/ADT items for and means
# you can build the SDK packages for architectures other than the machine you are
# running the build on (i.e. building i686 packages on an x86_64 host).
# Supported values are i686 and x86_64
SDKMACHINE ?= "x86_64"
#
# Extra image configuration defaults
#
# The EXTRA_IMAGE_FEATURES variable allows extra packages to be added to the generated
# images. Some of these options are added to certain image types automatically. The
# variable can contain the following options:
# "dbg-pkgs" - add -dbg packages for all installed packages
# (adds symbol information for debugging/profiling)
# "dev-pkgs" - add -dev packages for all installed packages
# (useful if you want to develop against libs in the image)
# "ptest-pkgs" - add -ptest packages for all ptest-enabled packages
# (useful if you want to run the package test suites)
# "tools-sdk" - add development tools (gcc, make, pkgconfig etc.)
# "tools-debug" - add debugging tools (gdb, strace)
# "eclipse-debug" - add Eclipse remote debugging support
# "tools-profile" - add profiling tools (oprofile, exmap, lttng, valgrind)
# "tools-testapps" - add useful testing tools (ts_print, aplay, arecord etc.)
# "debug-tweaks" - make an image suitable for development
# e.g. ssh root access has a blank password
# There are other application targets that can be used here too, see
# meta/classes/image.bbclass and meta/classes/core-image.bbclass for more details.
# We default to enabling the debugging tweaks.
EXTRA_IMAGE_FEATURES = "debug-tweaks"
#
# Additional image features
#
# The following is a list of additional classes to use when building images which
# enable extra features. Some available options which can be included in this variable
# are:
# - 'buildstats' collect build statistics
# - 'image-mklibs' to reduce shared library files size for an image
# - 'image-prelink' in order to prelink the filesystem image
# - 'image-swab' to perform host system intrusion detection
# NOTE: if listing mklibs & prelink both, then make sure mklibs is before prelink
# NOTE: mklibs also needs to be explicitly enabled for a given image, see local.conf.extended
USER_CLASSES ?= "buildstats image-mklibs"
#
# Runtime testing of images
#
# The build system can test booting virtual machine images under qemu (an emulator)
# after any root filesystems are created and run tests against those images. To
# enable this uncomment this line. See classes/testimage(-auto).bbclass for
# further details.
#TEST_IMAGE = "1"
#
# Interactive shell configuration
#
# Under certain circumstances the system may need input from you and to do this it
# can launch an interactive shell. It needs to do this since the build is
# multithreaded and needs to be able to handle the case where more than one parallel
# process may require the user's attention. The default is iterate over the available
# terminal types to find one that works.
#
# Examples of the occasions this may happen are when resolving patches which cannot
# be applied, to use the devshell or the kernel menuconfig
#
# Supported values are auto, gnome, xfce, rxvt, screen, konsole (KDE 3.x only), none
# Note: currently, Konsole support only works for KDE 3.x due to the way
# newer Konsole versions behave
#OE_TERMINAL = "auto"
# By default disable interactive patch resolution (tasks will just fail instead):
PATCHRESOLVE = "noop"
#
# Disk Space Monitoring during the build
#
# Monitor the disk space during the build. If there is less that 1GB of space or less
# than 100K inodes in any key build location (TMPDIR, DL_DIR, SSTATE_DIR), gracefully
# shutdown the build. If there is less that 100MB or 1K inodes, perform a hard abort
# of the build. The reason for this is that running completely out of space can corrupt
# files and damages the build in ways which may not be easily recoverable.
# It's necesary to monitor /tmp, if there is no space left the build will fail
# with very exotic errors.
BB_DISKMON_DIRS = "\
STOPTASKS,${TMPDIR},1G,100K \
STOPTASKS,${DL_DIR},1G,100K \
STOPTASKS,${SSTATE_DIR},1G,100K \
STOPTASKS,/tmp,100M,100K \
ABORT,${TMPDIR},100M,1K \
ABORT,${DL_DIR},100M,1K \
ABORT,${SSTATE_DIR},100M,1K \
ABORT,/tmp,10M,1K"
#
# Shared-state files from other locations
#
# As mentioned above, shared state files are prebuilt cache data objects which can
# used to accelerate build time. This variable can be used to configure the system
# to search other mirror locations for these objects before it builds the data itself.
#
# This can be a filesystem directory, or a remote url such as http or ftp. These
# would contain the sstate-cache results from previous builds (possibly from other
# machines). This variable works like fetcher MIRRORS/PREMIRRORS and points to the
# cache locations to check for the shared objects.
# NOTE: if the mirror uses the same structure as SSTATE_DIR, you need to add PATH
# at the end as shown in the examples below. This will be substituted with the
# correct path within the directory structure.
#SSTATE_MIRRORS ?= "\
#file://.* http://someserver.tld/share/sstate/PATH;downloadfilename=PATH \n \
#file://.* file:///some/local/dir/sstate/PATH"
XILINX_VER_MAIN = "2020.2"
# Uncomment below lines to provide path for custom xsct trim
# This is required for building Versal based devices, please fetch the
# xsct-trim from Xilinx lounge area
#
#EXTERNAL_XSCT_TARBALL = "/proj/yocto/xsct-trim/2020.2_xsct_daily_latest"
#VALIDATE_XSCT_CHECKSUM = '0'
# XILINX_VIVADO_DESIGN_SUIT should point to the Vivado installation directly if you are using xilinx-mcs recipe in meta-xilinx-tools
#XILINX_VIVADO_DESIGN_SUIT = "/proj/xbuilds/2018.3_daily_latest/installs/lin64/Vivado/2018.3"
# INHERIT += "externalsrc"
# PREFERRED_PROVIDER_virtual/kernel = "linux-xlnx-dev"
# EXTERNALSRC_pn-linux-xlnx-dev = "${BASE}/sources/linux"
# RM_WORK_EXCLUDE += "linux-xlnx-dev"
# PREFERRED_PROVIDER_virtual/bootloader = "u-boot-xlnx-dev"
# EXTERNALSRC_pn-u-boot-xlnx-dev = "${BASE}/sources/u-boot"
# RM_WORK_EXCLUDE += "u-boot-xlnx-dev"
#Add below lines to use runqemu for ZU+ machines
PMU_FIRMWARE_DEPLOY_DIR = "${DEPLOY_DIR_IMAGE}"
PMU_FIRMWARE_IMAGE_NAME = "pmu-firmware-${MACHINE}"
# CONF_VERSION is increased each time build/conf/ changes incompatibly and is used to
# track the version of this file when it was generated. This can safely be ignored if
# this doesn't mean anything to you.
CONF_VERSION = "1"
PNBLACKLIST[qemu-native]="blacklist"
PNBLACKLIST[nativesdk-qemu]="blacklist"
# Adding a hostname to the target machine
hostname_pn-base-files = "ngp-lhp-user-670"
# Reduce processing
BB_NUMBER_THREADS = "4"
PARALELL_MAKE = "-j 1"
####################################
# Mender Client Integration (Zynq)
####################################
# 1. Enable Mender integration
INHERIT += "mender-full"
# 2. Unique artifact name (shown in Mender UI)
MENDER_ARTIFACT_NAME = "Sentinel release-1"
# 3. Set correct bootloader and disable GRUB/EFI (Zynq uses U-Boot)
MENDER_FEATURES_ENABLE_append = " mender-uboot"
MENDER_FEATURES_DISABLE_append = " mender-grub"
# 4. Set storage device (mmcblk0 is typical for SD/eMMC on Zynq)
MENDER_STORAGE_DEVICE = "/dev/mmcblk0"
MENDER_UBOOT_STORAGE_INTERFACE = "mmc"
MENDER_UBOOT_STORAGE_DEVICE = "0"
# Optional: if you want to customize partition sizes
MENDER_PARTITION_ALIGNMENT = "4194304"
MENDER_BOOT_PART_SIZE_MB = "64"
MENDER_DATA_PART_SIZE_MB = "1024"
MENDER_STORAGE_TOTAL_SIZE_MB = "2048"
# 5. Tell Yocto to use U-Boot as bootloader
PREFERRED_PROVIDER_virtual/bootloader = "u-boot-xlnx"
PREFERRED_PROVIDER_virtual/kernel = "linux-xlnx"
PREFERRED_PROVIDER_u-boot-fw-utils = "u-boot-xlnx"
# 6. Use systemd (required for Mender service)
DISTRO_FEATURES_append = " systemd"
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
# VIRTUAL-RUNTIME_initscripts = "" # Usually not needed if systemd is used
# 7. Mender server setup (hosted.mender.io)
MENDER_SERVER_URL = "https://hosted.mender.io"
MENDER_TENANT_TOKEN = ""
# Optional: Add debugging tools to image
EXTRA_IMAGE_FEATURES += "debug-tweaks"
# Optional: Select package format (rpm is default for PetaLinux)
PACKAGE_CLASSES ?= "package_rpm"
KERNEL_DEVICETREE = "morey-ngx-t-revb-system.dtb"
PACKAGECONFIG_remove_pn-gpsd = "pps"
LCONF_VERSION = "7"
BBPATH = "${TOPDIR}"
BSPDIR := "${@os.path.abspath(os.path.join("${TOPDIR}", os.pardir))}"
BBFILES ?= ""
BBLAYERS ?= " \
${BSPDIR}/sources/core/meta \
${BSPDIR}/sources/core/meta-poky \
${BSPDIR}/sources/meta-openembedded/meta-perl \
${BSPDIR}/sources/meta-openembedded/meta-python \
${BSPDIR}/sources/meta-openembedded/meta-filesystems \
${BSPDIR}/sources/meta-openembedded/meta-gnome \
${BSPDIR}/sources/meta-openembedded/meta-multimedia \
${BSPDIR}/sources/meta-openembedded/meta-networking \
${BSPDIR}/sources/meta-openembedded/meta-webserver \
${BSPDIR}/sources/meta-openembedded/meta-xfce \
${BSPDIR}/sources/meta-openembedded/meta-initramfs \
${BSPDIR}/sources/meta-openembedded/meta-oe \
${BSPDIR}/sources/meta-clang \
${BSPDIR}/sources/meta-browser \
${BSPDIR}/sources/meta-qt5 \
${BSPDIR}/sources/meta-xilinx/meta-xilinx-bsp \
${BSPDIR}/sources/meta-xilinx/meta-xilinx-pynq \
${BSPDIR}/sources/meta-xilinx/meta-xilinx-contrib \
${BSPDIR}/sources/meta-xilinx-tools \
${BSPDIR}/sources/meta-petalinux \
${BSPDIR}/sources/meta-virtualization \
${BSPDIR}/sources/meta-openamp \
${BSPDIR}/sources/meta-jupyter \
${BSPDIR}/sources/meta-vitis-ai \
${BSPDIR}/sources/meta-morey-bsp \
${BSPDIR}/sources/meta-morey-linux \
${BSPDIR}/sources/meta-morey-dbms \
${BSPDIR}/sources/meta-laird-cp/meta-summit-radio-pre-3.4 \
${BSPDIR}/sources/meta-morey-middleware \
${BSPDIR}/sources/meta-morey-applications \
${BSPDIR}/sources/meta-morey-customer-applications \
${BSPDIR}/sources/meta-mender/meta-mender-core \
"
BBLAYERS_NON_REMOVABLE ?= " \
${BSPDIR}/sources/poky/meta \
"