Build an Automotive Grade Linux image
HERE OTA Connect lets you easily manage OTA updates to embedded devices running custom-built Yocto images. It works great with Automotive Grade Linux, so building an AGL image is one easy way to get started. If your planned project is automotive, AGL is a great choice to start out with. Out of the box, HERE OTA Connect works with AGL builds for QEMU and Raspberry Pi Model 3.
You’ll need a build machine with the following:
On a Debian-based system, you should be able to install all the required packages with the following command:
sudo apt-get install gawk wget git-core diffstat unzip texinfo gcc-multilib build-essential chrpath socat cpio python python3 python3-pip python3-pexpect python-dev xz-utils debianutils iputils-ping cpu-checker default-jre parted
Many/most distros that aren’t on the officially supported list will still work just fine—feel free to give it a try with whatever you’re running.
Although the Yocto project as a whole does support architectures other than x86-64 for the build machine, one of the layers we’ll be using only supports x86-64.
You can run this all inside a VM, but a Yocto build is a pretty resource-intensive process, so generally we don’t recommend it. Make sure your VM meets the following requirements:
At least 6GB of RAM
At least 150GB of disk space.
100GB of free disk space
Download the latest version directly from Google, or
install it from your distro’s packages if available (
sudo apt-get install repo)
Also, make sure that you’ve generated your provisioning credentials first.
First, clone a manifest file for AGL Electric Eel:
mkdir myproject cd myproject repo init -b eel -m default.xml -u https://gerrit.automotivelinux.org/gerrit/AGL/AGL-repo.git repo sync
This will download the basic Yocto layers you need. Generally, HERE Technologies recommends using AGL’s latest point release.
Now you can run the following script to get the environment set up:
source meta-agl/scripts/aglsetup.sh -m <target-architecture> agl-demo agl-appfw-smack agl-sota (1)
The environment setup script will have created a build directory and placed you in it. It also generates a configuration file, located at
conf/local.conf. This file is where we’ll make our modifications to the base config.
To connect with your HERE OTA Connect account, you’ll need the provisioning credentials bundle you downloaded earlier. Add the following line to your local.conf to supply those credentials to the build:
SOTA_PACKED_CREDENTIALS = "/path/to/your/credentials.zip"
Set image name
When you build a filesystem image, it gets automatically uploaded to OTA Connect. By default, the image will be named
<machine-name>-ota, and you’ll see the various versions of the image under that name. You can also choose to set your own name as follows:
OSTREE_BRANCHNAME = "my-super-great-project"
Persistent Yocto shared state cache and download directory
Yocto caches its build artefacts to speed up future builds. By default, these are stored under the build directory of the current project. However, if you’re planning to build several different projects that have some shared base files, you might want them to share their cache directories, both to save space and speed up your builds. You can do that as follows:
SSTATE_DIR = "/path/to/your/shared-sstate" DL_DIR = "/path/to/your/shared-download"
Add extra packages
There are quite a lot of packages available to install that aren’t installed by default. You can add extra packages to your image with IMAGE_INSTALL_append; for example, this will install vim:
IMAGE_INSTALL_append = " vim " (1)
|1||Note the spaces before and after the package name. This option dumbly appends a string to an install list, so we wrap it in spaces to make sure we don’t alter the list in unexpected ways.|
You can get a list of all the available packages in the layers you have configured with
Now you’re ready to build an image.
This step will take a while. If you used the build mirror, it might be as little as 10-15 minutes. Building everything from scratch, it will likely take a few hours.
The build process creates disk images as an artefact. The exact image you’ll need will vary depending on the architecture you’re building for, but it will be located in the
/tmp/deploy/images directory under your build directory. We recommend using Etcher to write the image, or following the normal flashing procedure for your device if applicable.
You can also write the image using
You’ll probably also want to resize the main partition to fill all of the space on the boot media:
sudo parted -s /dev/sdX resizepart 2 '100%' (1) sudo resize2fs /dev/sdX2 (1)
|1||Where /dev/sdX is the device you wrote the image to.|
You should now be able to boot your device and have it show up in your OTA Connect account.
agl-demo-platformtarget for Raspberry Pi 3 creates an image at