ardupilot/Tools/AP_Bootloader
Andrew Tridgell a002040146 AP_Bootloader: use new check_limit_flash_1M()
use common function
2022-10-09 09:47:02 +11:00
..
AP_Bootloader.cpp Tools: add LED notification for bad firmware 2022-08-30 10:51:06 +10:00
README.md AP_Bootloader: added board_types.txt 2020-06-17 14:16:47 +10:00
app_comms.h AP_Bootloader: use AP_CheckFirmware 2022-08-15 09:18:34 +10:00
bl_protocol.cpp Tools: add LED notification for bad firmware 2022-08-30 10:51:06 +10:00
bl_protocol.h Tools: add LED notification for bad firmware 2022-08-30 10:51:06 +10:00
board_types.txt Tools: allocate board ID for AtomRCF405 2022-09-09 07:14:51 +10:00
can.cpp AP_Bootloader: use AP_CheckFirmware 2022-08-15 09:18:34 +10:00
can.h AP_Bootloader: use AP_CheckFirmware 2022-08-15 09:18:34 +10:00
mcu_f1.h AP_Bootloader: added CAN support for AP_Periph 2019-08-27 10:29:56 +10:00
mcu_f3.h AP_Bootloader: support STM32F303 MCU 2019-11-01 10:53:53 +11:00
mcu_f4.h AP_Bootloader: use new check_limit_flash_1M() 2022-10-09 09:47:02 +11:00
mcu_f7.h AP_Bootloader: added mcu files 2018-06-22 08:06:41 +10:00
mcu_g4.h AP_Bootloader: fixed G4 MCU descriptions 2021-07-30 10:20:52 +10:00
mcu_h7.h AP_Bootloader: use new check_limit_flash_1M() 2022-10-09 09:47:02 +11:00
mcu_l4.h AP_Bootloader: support L496 MCUs 2021-09-24 18:08:00 +10:00
support.cpp AP_Bootloader: use new check_limit_flash_1M() 2022-10-09 09:47:02 +11:00
support.h AP_Bootloader: use new check_limit_flash_1M() 2022-10-09 09:47:02 +11:00
wscript AP_Bootloader: use AP_CheckFirmware 2022-08-15 09:18:34 +10:00

README.md

ArduPilot Bootloader

This is the bootloader used for STM32 boards for ArduPilot. To build the bootloader do this:

 ./waf configure --board BOARDNAME --bootloader
 ./waf bootloader

the bootloader will be in build/BOARDNAME/bin. If you have the intelhex module installed it will build in both bin format and hex format. Both are usually uploaded with DFU. The elf file will be in build/BOARDNAME/AP_Bootloader for loading with gdb.

The --bootloader option tells waf to get the hardware config from the hwdef-bl.dat file for the board. It will look in libraries/AP_HAL_CHibiOS/hwdef/BOARDNAME/hwdef-bl.dat

The bootloader protocol is compatible with that used by the PX4 project for boards like the Pixhawk. For compatibility purposes we maintain a list of board IDs in the board_types.txt file in this directory.

the board IDs in that file match the APJ_BOARD_ID in the hwdef.dat and hwdef-bl.dat files

The bootloader can load from USB or UARTs. The list of devices to load from is given in the SERIAL_ORDER option in hwdef-bl.dat