This pull request provides the feature to flash a firmware via DFU bootloader.
To flash a firmware via DFU bootloader, this logic uses WebUSB API. Actually, there are some DFU protocols, but this pull request has a logic to support ATMEL DFU (ADC_AVR). That is, ADC_8051, ADC_AVR32, ADC_XMEGA and DC_STM32 are not supported in this time. The supported MCU list are:
Basically, it can wrote same firmware binary hex file using one of bootloaders for one MCU. For example, if you have a firmware hex file and you have a MCU with ATmega32u4 which has the Catarina bootloader, you can flash it with the Catarina protocol. And, if you also have a MCU with ATmega32u4 which has the DFU bootloader, you also can flash the same hex file with the DFU protocol. Therefore, users need to select a bootloader type at flashing a firmware on the introduction dialog pane. That is, it is unnecessary to specify a bootloader type and MCU type at registering a firmware by the keyboard designer. In this pull request, I removed the UI to specify them from the firmware upload page for keyboard designers, and I added the UI to specify a bootloader type on the firmware flashing dialog for users.
Fix #664
This pull request provides the feature to flash a firmware via DFU bootloader.
To flash a firmware via DFU bootloader, this logic uses WebUSB API. Actually, there are some DFU protocols, but this pull request has a logic to support ATMEL DFU (ADC_AVR). That is, ADC_8051, ADC_AVR32, ADC_XMEGA and DC_STM32 are not supported in this time. The supported MCU list are:
Basically, it can wrote same firmware binary hex file using one of bootloaders for one MCU. For example, if you have a firmware hex file and you have a MCU with ATmega32u4 which has the Catarina bootloader, you can flash it with the Catarina protocol. And, if you also have a MCU with ATmega32u4 which has the DFU bootloader, you also can flash the same hex file with the DFU protocol. Therefore, users need to select a bootloader type at flashing a firmware on the introduction dialog pane. That is, it is unnecessary to specify a bootloader type and MCU type at registering a firmware by the keyboard designer. In this pull request, I removed the UI to specify them from the firmware upload page for keyboard designers, and I added the UI to specify a bootloader type on the firmware flashing dialog for users.