In this guide we'll take Airbotics Cloud for a spin, we will:
- Build a full system image using Yocto and push it to Airbotics.
- We'll then flash the first image onto an emulated device and run it.
- We'll then make a new version of the image and push it again.
- Finally, we'll use the dashboard to update the device to the new version "over-the-air".
- A Linux-based machine with plenty of storage, compute and memory.
- ~100GB disk space
- At least 8GB of RAM
- QEMU -
sudo apt install qemu
- Androids repo tool -
sudo apt install repoor follow the instructions from repo link if an official package available from your Linux distribution isn't avaiable.
- Yocto dependencies -
sudo apt install gawk wget git 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
- A large coffee.
Let's go! 🚀
The first thing to do after creating your account is download your provisioning credentials from the dashboard. You've have to input an expiry date for them, it may take a few seconds for them to be issued.
Provisioning credentials are used to upload software images to Airbotics and to provision your robots, they come in a
For this guide we'll build a basic image on top of the referenece distribution Poky, we will build it without vim and later create a new version that does contain vim.
In the interest of moving quickly we'll make use of the updater-repo from Advanced Telematic. This repo can be used to gather all of the yocto layers we'll need to build an image for Airbotics.
Set up a project directory and then sync the required yocto layers.
repo init -u https://github.com/advancedtelematic/updater-repo.git -m dunfell.xml
repo sync -j8
At this point you should have all the required yocto layers on your host machine, including meta-updater which contains the agent, OSTree, and other magic. After this guide, you can add more layers with everything your robot needs by creating your own or importing pre-built ones.
Meta-updater includes a helper script to set up the envirnoment. From your project root run
source meta-updater/scripts/envsetup.sh qemux86-64. We are going to build an image for the QEMU emulator.
You should now find yourself in the
From here we will need to edit
airbotics-quickstart/build/conf/local.confand tell yocto where to look for our
credentials.zipwe downloaded in step 1. Open the conf file and add
SOTA_PACKED_CREDENTIALSvalue to be the absolute path pointing to wherever you download your credentials.
At this point we are finally ready to build the image with:
Note: the first time you do this it can take as long as an hour. This could be a good time to get that coffee.
When the image finishes building meta-updater will sign and upload it to Airbotics. You'll then be able to see it in the images page on the dashboard. Click into the image and change its description to something like Quickstart image v1 - does not contain vim.
More: You can read a more detailed tutorial about building images here including how to pin images to certain compatible boards.
Now that we have a shiny new image with everything our robot needs we'll flash it to our "robot". To simplify things, we're using the QEMU emulator instead of a physical board.
We'll "flash" and boot the "robot" by running the following command:
../meta-updater/scripts/run-qemu-ota --overlay quickstart-robot.cow
Once it boots the agent will automatically provision itself with Airbotics and genreate a random ID. From the command line in QEMU you can manually check which version is running with the command below:
ostree admin status
You can also confirm that vim is not found by running
vimwhich should produce a nice error message.
If you head over to the robots page of the dashboard you can see information about it your robot and confirm the correct version is running.
Great! Now we have a robot that's running an image we've built and is provisioned with Airbotics. Let's improve our software by adding vim to it. In the
airbotics-quickstart/build/conf/local.confof the meta-updater layer add the following line:
IMAGE_INSTALL_append = " vim "
and build it again using:
Note: This should take a fraction of the time that it did on the first build.
After it builds we can see it in the images page of the dashboard, let's click into it and give it a description like: Quickstart image v2 - contains vim.
So our engineers have been busy at work improving our codebase and we now have a brand new image that includes vim. Let's roll it out to our fleet.
We'll head to the rollouts page on the dashboard and create a rollout. We'll target the rollout at selected robots (just one for now) and we'll specify we want to update ECUs with the
qemu86-64hardware id to update to the update to our new image with vim. You should see a summary showing how our robot will be affected by the rollout, then you can confirm the creation of the rollout.
The final step to get the robot to update is to launch the rollout. You can do that from the Rollout Details page. At this point our robot should begin to download and install the new update. We can monitor the status of the rollout from the dashboard.
With Airbotics, updates only take place after a reboot, you can confirm that although the update has been accepted by the robot it hasn't yet been applied by running this command on the board:
ostree admin status
We can also confirm vim isn't on the robot yet.
Now Let's reboot qemu and confirm the update was applied:
sudo reboot. Once it boots you should now be able to use vim. You'll see the ECU, Robot and Rollout status has changed. Nice 😎
If you don't intend to continue to use your credentials we recommend you revoke them in Airbotics dashboard and delete them from your computer. You can also delete the images and robot.