I have a Matek F405-WMN and I cannot get it to go into DFU mode. This happened after I installed Ardupilot on it. The board went into DFU mode easily and I was able to flash the arduplane_with_bl.hex file but now when I press the DFU button and plug in my USB cable the board always boots right into Arduplane. Has anyone had problems getting their boards to go back onto DFU mode after flashing Arduplane?
Perhaps…
FAQs and user guide – Matek Systems // Red/Blue/Green LEDs light up/blink normal when FC booting, but FC can‘t connect to configurator, or can’t go into DFU mode.//
Thanks to Lano’s post. I have Omnibus F4V2 Pro that behaved the same with Ardupilot Copter 4.2.0. After I disconnect the ELRS receiver the board it can enter DFU mode again. And every time I connect the ELRS receiver back then it always fail to enter DFU mode.
Golden tip, this also definitely works for the Speedybee F405 Wing, thanks for the tip!
I have faced similar problems on a Flywoo F405HD AIO FC however this FC has an integrated ELRS Rx on UART1 - so it’s not so easy to disconnect it! I found I could virtually never get this FC into DFU mode using boot button (maybe once? And fyi I had loaded STM32 cube programmer which loads the drivers). It initially only got into dfu mode using Impulse RC Driver fixer utility or by sending a CLI boot command ( DFU in INAV). …basically software triggering of DFU seemed to work but not via the hardware button route. I then moved to MAVLINK over ELRS and it became impossible to enter DFU mode! In frustration I reverted the receiver firmware back from 3.5.4 to 3.4.0 and it happily went into DFU mode! I now find that with ELRS 3.5.4 if receiver is set to CSRF mode (via Express ELRS tools widget on tx) then Driver fixer utility will force it into dfu mode, if I set it to MAVLINK it won’t work! Has anyone else found this (excellent) AIO FC to be very flaky getting into DFU boot mode?. Flywoo seem to not recognise any potential issues from having its Rx on UART1