2.1 KiB
DFU is Device Firmware Update mode - that's a way to update firmware via the same USB cable you use for rusEFI communication. stm32 DFU is part of stm32 factory bootloader and we expect that any rusEFI board could be updated/reset via same USB connector as the one you use to communicate to your rusEFI ECU. Please let us know if that's not the case!
Auto DFU is when your rusEFI console switches your rusEFI device into DFU mode
Manual DFU mode is when you hold "Program" button while powering your rusEFI in order to switch it into DFU mode. This mode is used to program brand new stm32 chips which do not have a running version of rusEFI firmware.
On a STM32F4 Discovery, entering DFU mode requires putting a jumper between the pins VDD and BOOT0, then powering or resetting the board.
Q: I have "STM32 BOOTLOADER" in Device Manager and rusEFI console does not update firmware. What's wrong?
A: As of Aug 2021 rusEFI console uses "older" ST DFU driver. You would need to remove newer "STM32 BOOTLOADER" driver. Hit "Remove Device" with "Remove Drivers" checkbox. Once you've removed newer "STM32 BOOTLOADER" driver re-install DFU driver using rusEFI console driver button. Direct driver link https://github.com/rusefi/rusefi/files/7273342/ST.Microelectronics-3.0.4.0.zip
BAD
GOOD
Q: I am using the buttons but it simply does not work?
A: We have a report of this at https://www.rusefi.com/forum/viewtopic.php?p=42317#p42317. For now please keep trying!
Q: I have a Mac? Or even better I have a Linux device?
A: rusEFI console firmware functionality currently runs on Windows only.
Q: Do you have any ST-Link provisions?
Some boards have [Tag-Connect-TC2030] upwards three of those! Some boards have an unofficial (?) ST-Link V2 pinout. Both are intended for software developers while debugging issues, those are not intended for firmware update/recovery.