Loading Firmware onto ChibiOS-only boards¶
Recent versions of ArduPilot (Copter-3.6, Plane-3.9, Rover-3.5) run on relatively small, non-Pixhawk, autopilots using the ChibiOS operating system. Examples of these boards include the OpenPilot RevoMini, Mateksys F405-Wing and Omnibus F4 Pro.
Installing ArduPilot to these autopilot involves:
- Installing the required driver and flashing tool
- Downloading the appropriate ArduPilot firmware
- Loading ArduPilot to the board
Instructions for ArduPilot using ChibiOS to Pixhawk autopilots can be found here.
Download and Install Zadig (Windows only)¶
Download and run Zadig (search for “Zadig 2.3” just below “Download”) to allow accessing the board using USB.
Choose “List all devices” option from options menu
Select “STM32 BOOTLOADER” from the drop-down and press the “Replace Driver” button
Optionally you may wish to check the board is visible as a USB port:
- Hold down the board’s DFU button and plug in a USB cable (attached to your PC)
- Open the windows device manager and look under “Universal Serial Bus devices” for “STM32 BOOTLOADER”
Download the ArduPilot firmware¶
- Download the ArduPilot firmware for your board from firmware.ardupilot.org. You can normally find the appropriate firmware by doing the following:
Upload ArduPilot to the board¶
Download, install and run the Betaflight Configurator.
- Select “Firmware Flasher” on the left side of the screen
- Select DFU from the top right
- Push “Load Firmware [Local]” from the bottom right and select the arduXXX_with_bl.hex file downloaded above
- Push “Flash Firmware” and after a few minutes the firmware should be loaded
We expect future versions of Mission Planner and QGroundControl will allow uploading firmware via DFU which will remove the requirement to use the Betaflight Configurator
You may now reboot the board and connect with your favourite ground station (Mission Planner, QGC, etc) and future firmware uploads should also be possible using the normal method for Pixhawk boards.