This version (09 Apr 2019 12:12) was approved by aardelean.The Previously approved version (09 Apr 2019 12:10) is available.Diff

Building with buildroot

Aside from building the Linux kernel manually, there is also the possibility of building the ADI Linux kernel with the ADI buildroot repository.

Ideally, you should already be familiar with buildroot, but even if not, the steps in this guide should be pretty straight forward.

The starting point is to clone the ADI buildroot repository

git clone

Building for Microblaze

First make sure that the GNU toolchain for Microblaze is in the shell path.


export PATH="/opt/Xilinx/SDK/2018.2/gnu/microblaze/linux_toolchain/lin64_le/bin:$PATH"
Note: There are 2 toolchains for GCC. The recommended ones, should be under /opt/Xilinx/SDK/2018.2/gnu/microblaze/linux_toolchain/. Also, if this is being run on a 32-bit Linux system, the path should be /opt/Xilinx/SDK/2018.2/gnu/microblaze/linux_toolchain/lin64_le/bin

And also make sure that the the directory to the Vivado SDK is correct. The current example assumes that it is Vivado 2018.2 and it's installed in /opt/Xilinx/SDK/

Building for Microblaze - rootfs only

If building just the rootfs, go into the cloned buildroot directory

cd <buildroot>
make microblaze_adi_rootfs_defconfig

Building for Microblaze - simpleImage.<board>

If building an entire simpleImage that can be ran on a board:

cd <buildroot>
make microblaze_adi_defconfig
make BR2_LINUX_KERNEL_INTREE_DTS_NAME=kcu105_fmcdaq2
kcu105_fmcdaq2 is an example. Valid device-tree names can be found in or in the list below

A list of supported images for Microblaze:

  • kc705
  • kc705_fmcdaq2
  • kc705_fmcjesdadc1
  • kc705_fmcomms1
  • kc705_fmcomms2-3
  • kc705_fmcomms4
  • kcu105_adrv9371x
  • kcu105
  • kcu105_fmcdaq2
  • kcu105_fmcdaq3
  • kcu105_fmcomms2-3
  • kcu105_fmcomms4
  • vc707_ad6676evb
  • vc707
  • vc707_fmcadc2
  • vc707_fmcadc5
  • vc707_fmcdaq2
  • vc707_fmcjesdadc1
  • vc707_fmcomms1
  • vc707_fmcomms2-3
  • vc707_fmcomms4

Build output & device images

They are always present under:


For Microblaze it's simpleImage.<board-name> (example: simpleImage.kcu105_fmcdaq2)

resources/tools-software/linux-build/generic/buildroot.txt · Last modified: 09 Apr 2019 12:12 by aardelean