Prepare the dfu-util.exe flash command, but don't run it yet:ĭfu-util.exe -R -a 2 -d 1EAF:0003 -D ""Į.g.: dfu-util.exe -R -a 2 -d 1EAF:0003 -D "C:\Temp\Multi-STM_TXFLASH_INV_OPENTX-v1.2.1.67.bin" Open a Command Prompt and change to the 'tools' sub-folder in the Flash Multi folderĬd "C:\Program Files (x86)\FlashMulti\tools" Solutionĭownload or compile the correct, USB-enabled, firmware
Luckily, the USB bootloader always starts the module up briefly in DFU mode, and we can take advantage of that to re-flash it. Most likely you have flashed a non-USB enabled firmware over the USB port, making the USB port (and the module) inoperable. This program is Free Software and has ABSOLUTELY NO WARRANTY Lost Device after reset, assuming prod_id was incremented by oneNo DFU capable USB device foundĭfu-util - (C) 2007-2008 by OpenMoko Inc. If your module isn't working, it shows up in Device Manager as Maple DFU, and attempting to re-flash it via the native USB port fails with verbose output like this: Module stuck in DFU mode after flashing and cannot be re-flashed BOOT0 mode) when it is powered up from the USB port. The JP4IN1 will only go into 'flashing mode' (i.e. If the module is in the radio, make sure that the radio is switched off. Set the right-hand driver selector to libusbK (v3.0.7.0)įlashing fails when flashing a JP4IN1 in the radio In the drop-down device list select Maple 003 or Maple DFU, whichever is listed Run Zadig from the location where you installed or extracted it Run this command, substituting COMX for your COM portĭevice Manager should now show the Maple DFU device Plug your MULTI-Module in, noting the COM port which appears in Device Manager
Opentx zadig driver install#
Opentx zadig driver drivers#
Opentx zadig driver update#
Use the latest version of Flash Multi to update the DFU drivers. Filter on vendor = 0x1eaf product = 0x0003
0 kommentar(er)
