Repository navigation
Bootloaders STM32duino bootloader
USB DFU bootloader for STM32F1 boards.
| Type | Monolithic bootloader (type3) |
| Upstream | https://github.com/rogerclarkmelbourne/STM32duino-bootloader |
| CVEs attributed | 0 |
| Vulnerability-fixing commits | 0 naming a CVE, 0 keyword-matched |
| CVEs with a linked fix | 0 |
Enumerates as a DFU device for upload, then jumps to the sketch.
Type 3: reset to application.
See Boot-Stages for the eight-stage model these phases map onto.
- reset into bootloader -- Occupies the first 8 or 16 KB of STM32F1 flash.
- button/flag check -- Checks the BOOT jumper, a button, or a magic value left in a backup register by the application.
- USB DFU enumeration -- Enumerates as a USB DFU device using the bundled ST USB library.
- download -- Receives the application image over DFU and writes it to the application offset.
- application jump -- Relocates the vector table to the application offset and jumps.
The bootloader and the Arduino core agree on a flash offset (0x8002000 or 0x8005000) and on the backup-register magic value that means "reset into DFU" -- that pair is the entire interface. Because the vector table has to be moved, the application must set VTOR to the same offset, which is why an image built for the wrong offset simply hangs.
Nothing is passed to the application. There is no verification of what was downloaded; the USB DFU path is open whenever the device is in bootloader mode, which is the characteristic exposure of this class of hobbyist bootloader.
None detected. That means no matching pattern was found in its build configuration or source, not that the project is insecure -- a small MCU bootloader may simply have nothing to configure.
git -C oss-bootloaders submodule update --init type3/STM32duino-bootloader
./scripts/analysis/run-tool.sh codeql STM32duino-bootloaderSee Tools for what each tool applies to.