

Always reset to default with defaults in CLI after each reflashing, “full chip erase” can not erase old data completely!.use configurator 3.0 for fw 3.0.x, use configurator 4.1 for fw 4.1.x Make sure INAV firmware version is compatible with configurator version, e.g.It is related to DFU protocol used in the STM32 bootloader, not hardware and PC driver issue. If GPS or other peripherals are connected to UART1 or UART3 of F4/F7/H7 chip and these peripherals are powered ON while connecting USB.***** Installing Betaflight/INAV/ArduPilot(ChibiOS) you can easily kill chips when soldering if soldering iron is not grounded properly. some iron tips may float at arbitrary voltages unless an additional grounding wire is used. I'm on the latest betaflight client and running 4.2 on all three of my jones.***** Make sure the soldering iron you are using is ESD-safe. Most of the time this means no visible drive of any sort in my computer, sometimes it shows as drive E, which is inaccessible and cannot be opened, and very rarely (1 in 20 times) it shows up as Betaflight Flash as expected, but again, if clicked on it stalls out, fails to access and the closes and disconnects.Ĭould this be a specific incompatibility between Betaflight and windows 11?Īny advice or insights would be amazing! And if you know the fix that would just make my day.Īs a note, I've tried the following: Zadig for driver fix ImpulseRC driver fix 3 different cables Three different usb ports Windows update I messed around with usb drivers in device manager and tried and uninstall of what I think is the main USB driver jobby.


The issue is that when I try to switch any of my three flight controllers (one iflight, one t-motor, one flywoo) into mass storage mode - either through the black box button or by the msu command in the cli - betaflight closes it's connection to the board, as expected, but windows fails to recognise the flight controller flash storage as a usable volume.

Hello! I'm having one of those trawl the forums days where I cannot seem to unearth a solution to my issue.ĭespite my better judgement, I upgraded to windows 11 a month or so ago.
