You are browsing documentation for a version other than the latest stable release. Switch to the latest stable release, 1.6.
This section provides a reference of variables Mender use during the Yocto Project build process.
The variables are either specific to- and defined by Mender, as shown by the MENDER_ prefix, or defined by the Yocto Project and used by Mender.
Together with IMAGE_BOOTLOADER_FILE, this sets the offset where the bootloader should be placed, counting from the start of the storage medium. The offset is specified in units of 512-byte sectors. Obviously this needs to be non-zero, or the partition table itself would be overwritten.
Together with IMAGE_BOOTLOADER_BOOTSECTOR_OFFSET, this specifies a file that you would like to write directly into the boot sector, in the intervening space between the partition table and the first partition.
Influences which file system type Mender will build for the rootfs partitions in the .sdimg file. Mender will pick the first of the file system types ext2/ext3/ext4 listed in this variable as the file system for rootfs in the generated .sdimg file. See File system types for more information.
The size of the generated rootfs. This will be the size that is shipped in a .mender update. This variable is a standard Yocto Project variable and is influenced by several other factors. See the Yocto Project documentation for more information.
Note that this variable has no effect when generating an SD card image (sdimg), since in that case the size is determined automatically. See MENDER_STORAGE_TOTAL_SIZE_MB for more information.
Flags added to this variable will be used as extra arguments to the mender-artifact tool when creating the .mender artifact. For example:
MENDER_ARTIFACT_EXTRA_ARGS_append = " -v 1"The above example builds an artifact with the version 1 format.
The name of the image or update that will be built. This is what the device will report that it is running, and different updates must have different names. This variable must be defined or the build will fail.
Can be set to a private key which will be used to sign the update artifact. The default is empty, which means the artifact won't be signed.
The signature can also be added or changed outside the build process, by using the mender-artifact tool's -k option. For more information, see the section on modifying Mender artifacts.
If set, this will add the given public verification key to the client configuration, which means that the client will reject updates which are not signed by the corresponding private key (see MENDER_ARTIFACT_SIGNING_KEY).
More specifically, it will add the key to the root filesystem under /etc/mender/artifact-verify-key.pem, and add a ArtifactVerifyKey entry to mender.conf, pointing to this key. Using MENDER_ARTIFACT_VERIFY_KEY is recommended when the key is hosted in a file external to the build system / Yocto Project layer.
An alternative way to specify a verification key is to include a file named artifact-verify-key.pem in SRC_URI. This is a better approach if the key is hosted inside a Yocto Project layer, as opposed to living externally on the local host somewhere. Otherwise it has the same effect as defining MENDER_ARTIFACT_VERIFY_KEY.
Note that you cannot both use MENDER_ARTIFACT_VERIFY_KEY and have artifact-verify-key.pem in SRC_URI at the same time.
The partition Mender uses as the boot partition. See More detailed storage configuration for more information.
Filesystem type of boot partition. This configuration is only used in fstab. Most filesystems can be auto detected, but some can not and hence this variable exists to override the auto detection.
The size of the boot partition in the generated .sdimg file. See Configuring the partition sizes for more information.
The partition Mender uses as the persistent data partition. See More detailed storage configuration for more information.
Filesystem type of data partition. This configuration is only used in fstab. Most filesystems can be auto detected, but some can not and hence this variable exists to override the auto detection.
The size of the persistent data partition in the generated .sdimg file. See Configuring the partition sizes for more information.
As the name indicates, this variable is only relevant if you are building Mender with the meta-mender-demo layer. If set to an IP address, this variable sets the hostname resolution of the API gateway and the storage proxy (docker.mender.io and s3.docker.mender.io) to that address. The default is empty, which reverts to querying DNS (but note that the Docker setup comes with its own DNS server).
A string that defines the type of device this image will be installed on. This variable is only relevant when building a complete partitioned image (.sdimg suffix). Once a device is flashed with this, it will not change, even if the device is updated.
It defaults to the value of ${MACHINE}.
A space separated string of device types that determine which types of devices this update is suitable for. This complements the MENDER_DEVICE_TYPE variable, and is only relevant when building a .mender update, not when building a .sdimg partitioned image.
It defaults to the value of ${MACHINE}.
Features appended to this variable will be disabled in the build. See the section on features for more information.
Features appended to this variable will be enabled in the build. See the section on features for more information.
The MTD part name where UBI volumes are stored.
Defaults to empty when building .sdimg.
Defaults to ubi when building .ubimg.
A rough estimate of space lost due to partition alignment, expressed in MB. The
.sdimg build process will calculate that automatically using a simple
heuristic: 4 * 1024 * MENDER_PARTITION_ALIGNMENT_KB (accounts for boot partition, two
rootfs partitions and a data partition).
Alignment of partitions used when building .sdimg image, expressed in kiB.
Default value is 8192.
The partition Mender uses as the first (A) rootfs partition. See More detailed storage configuration for more information.
Alternative name for MENDER_ROOTFS_PART_A. Used if you need two different references to MENDER_ROOTFS_PART_A.
Example:
# will only accept a UBI volume name (but we normally work with index numbers e.g. `mender_boot_part`)
ubifsmount ubi0:rootfsaDefaults to the value of ${MENDER_ROOTFS_PART_A} when building .sdimg.
Defaults to ${MENDER_STORAGE_DEVICE}:rootfsa when building .ubimg.
The partition Mender uses as the second (B) rootfs partition. See More detailed storage configuration for more information.
Defaults to the value of ${MENDER_ROOTFS_PART_B} when building .sdimg
Defaults to ${MENDER_STORAGE_DEVICE}:rootfsb when building .ubimg.
Variable to override the URL of the server for the client to connect to.
Default value is https://docker.mender.io
Variable to override the location of state scripts. See MENDER_STATE_SCRIPTS_DIR for more information.
Only usable inside recipes that inherit mender-state-scripts. Recipes can put
executable binaries or scripts into this location to have the scripts be
included as state scripts for the Mender artifact. This should be done inside
the do_compile task of a recipe.
If neither building nor other preprocessing is necessary then it is also
possible to list a source archive in SRC_URI that extracts directly into
${PN}-${PV}/mender-state-scripts, where $PN and ${PV} are the usual
Bitbake values of recipe name and version, respectively.
And finally, it is possible to set MENDER_STATE_SCRIPTS (note the missing
_DIR) manually to a location containing state scripts, however it is
recommended to use one of the two above methods.
The three methods should not be mixed.
The storage device holding all partitions (rootfs, boot, data) used by Mender. See Configuring storage for more information.
Total size of the medium that mender .sdimg will be written to, expressed in
MB. The size of rootfs partition will be calculated automatically by subtracting
the sizes of boot (see MENDER_BOOT_PART_SIZE_MB)
and data partitions (see MENDER_DATA_PART_SIZE_MB)
along with some predefined overhead
(see MENDER_PARTITIONING_OVERHEAD_MB)).
Default value is 1024.
Set this variable in local.conf in order to make the device recognize the organization to which it belongs. This option should always be set, except when running a custom Mender server installation with multitenancy module disabled.
Specifies the offset from the start of the raw block storage where the U-Boot
environment should be stored, expressed in bytes. The default is equal to
MENDER_PARTITION_ALIGNMENT_KB (converted to bytes), and if the value is
overridden, it must also be aligned to MENDER_PARTITION_ALIGNMENT_KB.
The storage device, as referred to by U-Boot (e.g. 1). This variable can be used in cases where the Linux kernel and U-Boot refer to the same device with different names. See U-Boot and the Linux kernel do not agree about the indexes of storage devices for more information.
The storage interface, as referred to by U-Boot (e.g. mmc). This variable can be used in cases where the Linux kernel and U-Boot refer to the same device with different names. See U-Boot and the Linux kernel do not agree about the indexes of storage devices for more information.
Controls whether to run Mender as a systemd service. See Modes of operations and Image configuration for more information.