Images can be downloaded from the downloads page.

The SDK can be downloaded directly from Gitlab (see downloads) and do not need to be extracted any further.

The images however are provided in gzipped and need to be decompressed using gunzip befire use:

gunzip ost-image-*.wic.gz

Note that gunzip will remove the original .wic.gz file and as such 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 and SDKs in the tar.xz format can be extracted using the 'tar' command.

tar -vxJf <filename>

For example, to extract the Beaglebone Blue SDK provided below, use the following command in your Downloads folder:

tar -vxJf ntb-dev-image-2020.02.21-sdk.tar.xz

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

Custom Images can be built by folliwing the getting started guide up to and including „Building an Image“.

This step is optional and only needed if the images need to be in the same format as the images provided on the downloads page

The following command can be used to create tar.xz archives like provided above:

tar -C <path to target> -cvhJf ntb-dev-image-2020.02.21.tar.xz <target file/folder>

For example:

tar -C tmp/deploy/images/ -cvhJf ntb-dev-image-2020.02.21.tar.xz bblue

ntb-dev-image-1.0-rc0.tar.xz now contains a directory called bblue (since bblue was a folder originally) and all its content. If one was to use tar -C tmp/deploy -cJf ntb-dev-image-2020.02.21.tar.xz images/bblue, the archive would contain an images folder with bblue inside it.