At the moment I have the latest/dev firmware on it while I’m configuring. Don’t want to fly on that really though… but I also don’t want to brick my FC as it sounds like others above may have done?
I tried flashing the firmware and not connecting until it had been rebooted, and that worked. It will connect if you don’t reboot it, but only the first time. Thanks
I just bought this FC and flashed it with the 4.3.5 firmware from their website through Inav and it worked. Tried disconnecting-reconnecting, plug-unplug the cable multiple times and it still works in mission planner.
Any resolution to this? I have iNav installed right now, but want to move over to my usual Arduplane setup - but if there’s still an issue I’ll wait of course.
I have a SpeedyBee F405Wing running 4.5.0Dev and one running on 4.4.0 Stable, both with no issues flying VTOL aircraft. I had to load with iNav firmware flasher as the Betaflight flasher complained about address not available.
In my case i forgot to unplug the GPS module from one of the COM ports (can’t remember which one it was), which was colliding with entering the DFU mode, so i think, if you unplug things from the corresponding COM port, there should be no issue updating.