From 9ffc0f5a3a17373c42507a398fd562e032fed0c8 Mon Sep 17 00:00:00 2001 From: Andrew Tridgell Date: Thu, 7 Nov 2019 15:49:38 +1100 Subject: [PATCH] AP_Periph: updated README --- Tools/AP_Periph/README.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/Tools/AP_Periph/README.md b/Tools/AP_Periph/README.md index 3830bd9475..9c4d898f88 100644 --- a/Tools/AP_Periph/README.md +++ b/Tools/AP_Periph/README.md @@ -10,7 +10,7 @@ supported by ArduPilot. That means you can add support for a new UAVCAN peripheral based on the STM32 by just writing a simple hwdef.dat that defines the pinout of your device. -Currently we have three targets building for AP_Periph firmwares: +Currently we have four targets building for AP_Periph firmwares: - A STM32F103 128k flash part made by mRobotics (target f103-GPS) - A STM32F412 512k flash part made by CUAV (target CUAV_GPS) @@ -79,3 +79,10 @@ To build the bootloader use this: the resulting bootloader will be in Tools/bootloaders +# Firmware Builds + +Firmware targets are automatically built and distributed on the +ArduPilot firmware server on firmware.ardupilot.org. These firmwares +can be loaded using Mission Planner or the UAVCAN GUI Tool. Parameters +for peripherals can be changed using the Mission Planner SLCAN support +or using UAVCAN GUI Tools.