Building Images

Note that the ost-microzed machine requires the meta-ost-xilinx layer that is part of meta-ost.

Follow the Setup and Building guide to set up the build environment. Fetch board and processor specific repositories:

• meta-arm, git://git.yoctoproject.org/meta-arm, branch scarthgap

• meta-xilinx, git://git.yoctoproject.org/meta-xilinx, branch scarthgap

• meta-xilinx-tools, https://github.com/Xilinx/meta-xilinx-tools.git, branch scarthgap

Next, add the layers to bblayers.conf

and change the machine definition in local.conf

Configuring the PL/FPGA

The ost-image for ost-microzed supports adding multiple bitstreams that can be loaded at boot through device tree overlays. Currently the image ships the flink2 and flink4 bitstreams with corresponding device tree overlays. The image also includes additional overlays to configure some of the MIO's as an I2C bus and UART for use with the Experimental System or as GPIOs for use with the RT-Board. By default the image is configured to load flink2.bit and configure MIO's 11 & 12 as I2C and 14 & 15 as UART.

Changing the HW Configuration

The overlays to load are specified in /boot/uEnv.txt in the fdt_overlays variable. This is read by u-boot on boot to configure the device tree and load the FPGA. To reconfigure the HW edit fdt_overlays as needed and reboot. 

Default: fdt_overlays=flink2.dtbo expsys.dtbo

RT Board: fdt_overlays=flink4.dtbo rtboard.dtbo

Getting Images

Prebuilt images can be obtained from our Linux Images page. Extract it and flash it onto a micro SD card.

Booting from the Image

Currently the instructions only cover booting from the micro SD card slot.

Insert the micro SD card into the board and supply it with power.

Developing for the Board

See SDK or eSDK.

Accessing the Board

The login shell can be accessed through UART1 (USB mini on the board).

The root user is also available over ssh in development images.