This how-to describes how to build the u-boot bootloader for your target platform. Building the U-Boot bootloader is a part of the Xilinx design flow described in Getting Started. U-Boot depends upon an externally build device tree compiler (dtc) in order to build successfully. Please build the dtc tool before proceeding with the steps described below.

Task Dependencies (Pre-requisites)

Tools Required

Input Files Required

  • (MicroBlaze only)
  • xparameters.h (MicroBlaze, PPC only)

Output Files Produced

  • u-boot
  • mkimage

Task Description

All commands have to be executed in your u-boot source directory.
The first step is to configure the sources for the intended target. Xilinx u-boot supports the following targets:
U-Boot target
Zynq UltraScale+ MPSoC ZCU102
Zynq ZC702
Zynq ZC706
Zynq Zed Board
Zynq MicroZedBoard
Zynq PicoZedBoard

To build U-Boot for ZC702 execute:
make zynq_zc702_config
To build U-Boot for ZCU102 execute:
make xilinx_zynqmp_zcu102_rev1_0_config
After the build process completes the target u-boot elf-file is created in the top level source directory, named 'u-boot'. Additionally in the tools/ directory the 'mkimage' utility is created, which is used in other tasks to wrap images into u-boot format.
To make mkimage available in other steps, it is recommended to add the tools directory to your $PATH.
cd tools
export PATH=`pwd`:$PATH

U-Boot for MicroBlaze

The Xilinx U-Boot project is based on the source code from

The devices that have been tested include UART lite, UART 16550, Linear flash, EMAC lite, LL TEMAC with PLB DMA, and AXI EMAC with AXI DMA. The timer counter and interrupt controller were also tested.
Tests were done on Spartan 605 (PLB and AXI) and Kintex 705 (AXI) evaluation platforms using XPS 14.2 and 14.3.

The hardware project

U-Boot requires some minimal hardware configuration. Make sure the following peripherals are included in the system:
MicroBlaze processor configured for '(Low-end) Linux with MMU'
external memory controller
serial output configured to use interrupts
timer configured to use interrupts
interrupt controller
U-Boot includes capabilities of writing to/reading from flash and also transferring files over a network if the available hardware is present:
ethernet lite configured to use interrupts
ethernet configured to use interrupts and DMA
Additional peripherals and features are considered outside the scope of this page.

Building U-Boot

Creating the BSP required by U-Boot
To build U-Boot correctly, some information about the system will need to be provided to the U-Boot build tree. This information is generated by the U-Boot BSP.

First, download the U-Boot BSP source Once it has been installed and the project has been exported to SDK, the U-Boot BSP can be created for the system.

In order for the U-Boot BSP to generate the necessary settings for U-Boot, it needs to know which specific peripherals should be used for some corresponding tasks. These selections are made in the fields/drop-down menus located in the 'Settings' of the newly created U-Boot BSP. For example:
Once the U-Boot BSP has been compiled in SDK, the generated files, and xparameters.h, can be found at <sdk_workspace>/uboot_bsp_0/microblaze_0/libsrc/uboot_v*/ .

Downloading the source tree
The U-Boot source tree can be downloaded from the Xilinx Git server. The repository is u-boot-xlnx and the branch is master:
linux-host> git clone git://
linux-host> cd u-boot-xlnx
Compiling U-Boot
The U-Boot compilation will use the definitions and flags defined in and xparameters.h . Import these two files generated by the U-Boot BSP in SDK into the U-Boot directory for MicroBlaze located at <u-boot-xlnx>/board/xilinx/microblaze-generic/ .

Xilinx's MicroBlaze GNU toolchain will be used to cross-compile U-Boot for MicroBlaze. Instructions on obtaining and setting up the newest cross-compilation toolchain for MicroBlaze may be found at Microblaze GNU Tools.

Now that U-Boot and the toolchain are configured correctly, we can cross-compile U-Boot:
linux-host> cd <u-boot-xlnx>
linux-host> export BUILD_DIR=$PWD/build
linux-host> make microblaze-generic_config
linux-host> make

Loading and running U-Boot

Downloading U-Boot to MicroBlaze
Once the bitstream containing at least a minimally configured hardware system has been downloaded to the FPGA, XMD is used to download the cross-compiled U-Boot to the MicroBlaze soft processor:
XMD> connect mb mdm
XMD> dow <u-boot-xlnlx>/build/u-boot
XMD> run
U-Boot commands
The list of U-boot commands can be accessed while in the U-Boot prompt. Type "help" or "?" for a complete listing of available commands.

Documentation on U-Boot may be found at .

Running Linux using U-Boot

Preparing the Linux images for U-Boot
Specific details on building the kernel for MicroBlaze are contained in the Build Kernel page.
Instructions to obtain a root filesystem can be found at the Build and Modify a Root File System page.

The kernel and the root filesystem must be wrapped with a U-Boot header in order for U-Boot to accept these files. The mkimage utility is used for this purpose, however, it is not part of the MicroBlaze GNU tools. It is part of U-Boot itself and if U-Boot has been compiled as specified on this page, it will be found under <u-boot-xlnx>/build/tools/ .

When building linux.bin, as explained in the Build Kernel page, the kernel build process automatically creates an additional image, with the ".ub" suffix. linux.bin.ub is the Linux binary image wrapped with a U-Boot header. The Linux compilation process will automatically invoke mkimage, therefore, it is important to include the path to the U-Boot tools in the PATH environment variable.

The root filesystem also needs to be wrapped with a U-Boot header as follows:
mkimage -A microblaze -O linux -T ramdisk -C gzip -d ramdisk.image.gz uramdisk.image.gz

Booting Linux
XMD or TFTP may be used to download Linux to the FPGA (memory). U-Boot can then use these files to boot Linux. Once the kernel, root filesystem, and device tree images are present in memory, the command to boot Linux is:
U-Boot> bootm <addr of kernel> <addr of rootfs> <addr of device tree blob (dtb)>

Note: Make sure the kernel and root filesystem images are wrapped by with the U-Boot header. The device tree blob does not need to be wrapped with the U-Boot header.

Build Steps

Related Links