riotboot_tinyusb_dfu is a variation of riotboot that adds USB device firmware upgrade (DFU) based on the tinyUSB device stack package. It uses a board's USB interface to allow firmware upgrades from inside the bootloader.
At startup, the DFU mode is entered when either
riotbootsupport, see riotboot.
riotboot_tinyusb_dfu bootloader can be flashed using a regular programmer like any other application:
Depending on your setup, you may need to select the right
PROGRAMMER (and its details) in addition to your board.
A device in riotboot DFU mode can be recognized in the USB device list by its VID/PID pair 1209:7d02:
When running in DFU mode, the bootloader allows writing to either of the two firmware slots.
When the device is attached and in DFU mode (or the current firmware uses the
tinyusb_dfu module), new firmware can be flashed to slot 0 using:
Instead of setting
USB_PID, the variable
DFU_USB_ID could also be used to specify the DFU device to be used.
Note that when building and flashing a different slot (e.g.
flash-slot1), not only is the image built for that slot, but also
dfu-util gets passed
--alt 1 (via the
DFU_ALT build variable) to store it in the right place.
When RIOT applications are built with
USEMODULE=tinyusb_dfu, they implement what is called "runtime mode" in DFU.
In runtime mode, it is visible to the
dfu-util that they are upgradable. On firmware upgrades, the build system can send a command via USB to enter DFU mode. This can also be done manually using
|TinyUSB specific DFU definitions. |