Linux Images

The images that are currently available for the bblue, cb20 and x86-rt can be downloaded from the meta-ost Gitlab package registry.

Please note, that these images are built for development, see Development vs Production. For production images you have to built it with a full yocto installation, see Setup and Building or use the eSDK, see SDK's.

The images for bblue and x86-rt are provided in gzipped and need to be decompressed using gunzip before use:

gunzip ost-image-*.wic.gz

Note that gunzip will remove the original .wic.gz file and only the .wic file will be available after. gzip and gunzip should come preinstalled on most distributions, otherwise search for the gzip package in your distro's repositories.

Images for cb20 are provided as *Tezi*.tar file. You have to unpack it before it is recognized by the easy installer.

tar -xvf *Tezi*.tar

Linux script example for .wic image flashing onto an external storage device, e.g. an external SD card. Beware: sdb has to be replaced with the correct device. Use lsblk command to discover the correct device!. sdX where X is a small letter starting from a usually represents a SATA or USB drive, names starting with nvme represent NVME SSDs and SD cards usually start with mmcblk. These names represent the device as found in /dev, so sda is found under /dev/sda. lsblk uses a tree to show devices and their partitions. For example sda1 is the first partition on sda and nvme1n1p1 is the first partition of nvme1n1.

: Writing the image to the USB Stick will erase all content! Make absolutely sure you have identified the correct device! dd will not hesitate to override your OS drive if you tell it to do!

#!/bin/sh
umount /dev/sdb*
wipefs -a /dev/sdb
dd if=ost-ros-image-melodic-bblue.wic of=/dev/sdb bs=1M status=progress
eject /dev/sdb

The process for installing images is dependent on the target hardware. Hence, see section „Installing Images“ in

See General Network Settings for help to setup necessary network connections.