Build ZynqMP / MPSoC Linux kernel and devicetree

Using a script

We provide a script that does automates the build for Zynq using the Linaro toolchain.

Attention

This script differs from the one for Zynq.

The script takes up to 3 parameters, but if left blank, it uses defaults:

  1. <local_kernel_dir> - default is linux-adi if left blank ; use this, if you want to use an already cloned kernel repo

  2. <devicetree_file> - which device tree should be exported/copied from the build. Default is xilinx/zynqmp-zcu102-rev10-ad9361-fmcomms2-3.dtb for ZynqMP

  3. <path_to_other_toolchain> - in case you have your own preferred toolchain (other than Linaro’s or AMD Xilinx’s) you can use override it with this 3rd paramameter

The script will:

  • Clone the ADI kernel tree

  • Download the Linaro GCC toolchain (if no other is specified)

  • Build the ADI kernel tree

  • Export/copy the Image file and device tree file out of the kernel build folder

Running the script in one line, with defaults:

~$

wget https://raw.githubusercontent.com/analogdevicesinc/wiki-scripts/main/linux/build_zynqmp_kernel_image.sh && \
       chmod +x build_zynqmp_kernel_image.sh && \
       ./build_zynqmp_kernel_image.sh

Building with Petalinux

Please see here: Build with Petalinux.

On the development host

Make sure you have u-boot-tools installed, to have the mkimage utility available. You can install it via your distro’s package manager.

Then

~$

git clone https://github.com/analogdevicesinc/linux.git \
            --no-single-branch --depth=10 \
            -- linux

or do a git pull in a existing cloned repository.

The depth and no-single-branch options are included to speed up the cloning by fetching only near the head of each branch/release, you may remove them to fetch all history, but bear in mind it will go from around 800MB to around 3.4GB and growing.

Checkout the Release branch

Tip

Use the latest release, if not required otherwise!

The release branches have the format <Year>_R[1|2], starting from 2014_R2.

~$

git checkout origin/2021_R1 -b 2021_R1

Branch 2021_R1 set up to track remote branch 2021_R1 from origin.
Switched to a new branch '2021_R1'

Add aarch64-linux-gnu-gcc to PATH

Using the Xilinx toolchain

~$

source $PATH_TO_XILINX/Vitis/$VITIS_VERSION/settings64.sh

~$

which aarch64-linux-gnu-gcc

$PATH_TO_XILINX/Vitis/$VITIS_VERSION/gnu/aarch64/lin/aarch64-linux/bin/aarch64-linux-gnu-gcc

Important

Find the path to the Xilinx installation folder, and then use it to replace this string: $PATH_TO_XILINX that is written above. Same goes for the $VITIS_VERSION, where you choose the Vitis version.

~$

export ARCH=arm64

~$

export CROSS_COMPILE="aarch64-linux-gnu-"

Using the Linaro toolchain

Alternatively, the Linaro toolchain/compiler can be used to compile to kernel. Linaro compilers (that work with ZYNQMP) can be downloaded from here. Always use the latest release just in case.

~$

wget https://releases.linaro.org/components/toolchain/binaries/latest-7/aarch64-linux-gnu/gcc-linaro-7.5.0-2019.12-x86_64_aarch64-linux-gnu.tar.xz

~$

tar -xvf gcc-linaro-7.5.0-2019.12-x86_64_aarch64-linux-gnu.tar.xz

~$

export ARCH=arm64

~$

export CROSS_COMPILE=$(pwd)/gcc-linaro-7.5.0-2019.12-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-

Configure the kernel

Inside the repository, generate the configuration file before building the kernel tree.

~$

make adi_zynqmp_defconfig

#
# configuration written to .config
#

Build the kernel via ‘make’. This is the same for all Xlinx ZYNQMP MPSoC FPGAs.

~$

make -j5 Image UIMAGE_LOADADDR=0x8000

  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/basic/bin2c

[ -- snip --]

  CC      init/version.o
  LD      init/built-in.o
  KSYM    .tmp_kallsyms1.o
  KSYM    .tmp_kallsyms2.o
  LD      vmlinux
  SORTEX  vmlinux
  SYSMAP  System.map
  OBJCOPY arch/arm64/boot/Image

Build the devicetree FCMOMMS2/3

Build the one that fits your FPGA carrier and FMC card

device tree

board

chip

zynqmp-zcu102-rev10-ad9361-fmcomms2-3.dts

ZCU102 Rev. 1.0
AD-FMCOMMS2-EBZ or
AD-FMCOMMS3-EBZ board

zynqmp-zcu102-rev10-ad9364-fmcomms4.dts

ZCU102 Rev. 1.0
AD-FMCOMMS4-EBZ or
AD-FMCOMMS4-EBZ board

zynqmp-zcu102-revB-ad9361-fmcomms2-3.dts

ZCU102 Rev.B
AD-FMCOMMS2-EBZ or
AD-FMCOMMS3-EBZ board

zynqmp-zcu102-revB-ad9364-fmcomms4.dts

ZCU102 Rev.B
AD-FMCOMMS4-EBZ board

The device tree zynqmp-zcu102-revA.dts can also be used for any ZCU102 FPGA that uses an SD card for boot up. Building the device tree uses ‘make’ by turning the .dts file to a .dtb. The command is simply ‘make’ plus the device tree name with a .dtb file extension.

~$

make xilinx/zynqmp-zcu102-rev10-ad9361-fmcomms2-3.dtb

DTC     arch/arm64/boot/dts/xilinx/zynqmp-zcu102-rev10-ad9361-fmcomms2-3.dtb

Copy the generated files to your SD Card

The output files for building the kernel and device tree are uImage and <device_tree_name>.dtb. Refer to the code below to find their respective output directories. Take note that the device tree file needs to be renamed to devicetree.dtb. See SD Card flashing for more information in configuring the SD card.

~$

cp arch/arm64/boot/Image /media/michael/BOOT/

~$

cp arch/arm64/boot/dts/xilinx/zynqmp-zcu102-revB-ad9361-fmcomms2-3.dtb /media/michael/BOOT/system.dtb

Common Issues

This sections goes through common issues related to the Linux Kernel on the ZynqMP.

DisplayPort - no picture?

The default configuration for most of the projects is to use the HDMI output, and that is what the configuration is set up for.

For DisplayPort projects, you may need to add a custom xorg.conf file.

printf 'Section "Device"
  Identifier "myfb"
  Driver "fbdev"
  Option "fbdev" "/dev/fb0"
EndSection' > /etc/X11/xorg.conf

After following that, the board should be rebooted.

You can find a list with tested monitors here. Resolution or image problems may appear if there is used a monitor that was not tested.