Deploying the image¶
This section describes how to deploy the build output, a ready disk-image, to a removable media. Further information can be found in the Poky documentation.
Bmap-tools¶
Using bmap-tools¶
Use bmap-tools to write an Intel image to a disk more than twice faster than dd
. Bmap-tools, supports flashing of compressed images too.
You will need two files, both of them will be found on
/tmp/deploy/images/<architecture>/
.
The compressed image name and bmap file will have these suffixes:
<image>.rootfs.wic.bz2
<image>.rootfs.wic.bmap
To flash the image, run:
sudo bmaptool copy <compressed-image-name> --bmap <bmap-filename> <host-device>
Note
In case bmap gives the error "[Errno 16] Device or resource busy", make sure the disk partitions are unmounted.
General instructions¶
Use the dd
utility to write the image to the raw block device. For example:
dd if=<image-name> of=<host-device> bs=4M
sync
Note
The <image-name> depends on your arch and image recipe name. You can
find all images in tmp/deploy/images/<arch>/
in your build directory.
Note
The <host-device>
is the SD-card or other removable media device
on the host, e.g. /dev/mmcblk0
or /dev/sdc
. More information
on how to discover the SD-card or other media device can be found in
the following documentation.
Image names for PELUX targets¶
Intel NUC and ARP with Intel SMARC:
core-image-pelux-intel-corei7-64.wic
Raspberry Pi 3:
core-image-pelux-raspberrypi3.wic
Note
Image names depend on the built image and the image might contain suffixes such as -dev
. An image is always either a -minimal
or -qtauto-neptune
image. For software update images, a .swu
file exists.