Lorem ipsum dolor sit amet, consectetur adipiscing elit
The update sequence is kicked off by the user connecting the standalone Updater Board to the exposed USB port on the drone. The Updater Board is powered by the drone and is capable of updating the drone's onboard software. The software is bundled into Docker Images and is stored on the Updater Board. The Update sequence for the drone is as follows:
Drone Update Sequence
- The Updater Board is connected to the drone.
- The Updater Board checks for running containers that matched the Updater Board's Docker Images.
- The Updater Board stops the running containers.
- The Updater Board loads the Docker Images onto the drone.
- Using the defined Docker Compose file, the Updater Board starts the containers on the drone.
- The Updater Board disconnects from the drone.
Ground Station Update Sequence
- The Updater Board is connected to the drone.
- The Updater Board loads each hex file onto the drone.
- The drone begins sending a JSON message to each connected ground station device.
- The ground station devices establish an FTP server and wait for the drone to connect.
- The drone connects to the FTP server and sends the hex file to the ground station device where each hex file is stored within the devices' SD card.
- Once the hex file is stored, the device checks the integrity of the file.
- The device sends a JSON message to the drone indicating the file was stored successfully.
- The drone disconnects from the FTP server.
- Each device(s) enters an update sequence where the the hex file is written into a buffer on the flash memory.
- The device(s) writes the hex file to the flash memory updating the device's firmware.
- The device(s) reboot and check the integrity of the firmware.