RIOT/makefiles/boot/riotboot_dfu-util.mk

ifneq (,$(filter usbus_dfu tinyusb_dfu,$(USEMODULE)))
  ifeq (,$(filter riotboot_usb_dfu riotboot_tinyusb_dfu,$(USEMODULE)))
    # If module usbus_dfu or module tinyusb_dfu is used but neither
    # module riotboot_usb_dfu nor module riotboot_tinyusb_dfu, the
    # application uses DFU Runtime and dfu-util as programmer to flash the
    # application with the bootloader riotboot_dfu which uses the VID/PID pair
    # allocated for the RIOT bootloader https://pid.codes/1209/7D02/
    DFU_USB_ID ?= 1209:7d02
    DFU_USE_DFUSE ?= 0
  endif
endif
makefiles/boot/riotboot-dfu-util: add tinyusb_dfu support 2022-11-27 17:36:28 +01:00			`ifneq (,$(filter usbus_dfu tinyusb_dfu,$(USEMODULE)))`
			`ifeq (,$(filter riotboot_usb_dfu riotboot_tinyusb_dfu,$(USEMODULE)))`
			`# If module usbus_dfu or module tinyusb_dfu is used but neither`
			`# module riotboot_usb_dfu nor module riotboot_tinyusb_dfu, the`
makefiles: add riotboot_dfu-util.mk to override board's dfu-util config Boards that are shipped with a DFU bootloader define the `dfu-util` configuration in their `Makefile.include`. However, when `riotboot_dfu` is used as the DFU bootloader, the board's `dfu-util` configuration must be overridden by the configuration as required by `riotboot_dfu` to use it to flash applications. Therefore, all `dfu-util` configurations are defined as overridable in the board's `Makefile.include` and the configuration as required by `riotboot_dfu` is included before the board's `Makefile.include`. 2022-11-26 18:47:59 +01:00			`# application uses DFU Runtime and dfu-util as programmer to flash the`
			`# application with the bootloader riotboot_dfu which uses the VID/PID pair`
			`# allocated for the RIOT bootloader https://pid.codes/1209/7D02/`
			`DFU_USB_ID ?= 1209:7d02`
			`DFU_USE_DFUSE ?= 0`
			`endif`
			`endif`