#Flight Controller not connecting after applying cli dump

5 messages · Page 1 of 1 (latest)

grave sun
#

Hello, I have a "DarwinFPV ELRS3.0 F411 15A Bluejay AIO" flight controller in the Darwin FPV Tiny Ape and it was working and flying fine. I flew it too long one time and after I landed it powered itself off because of low battery, when I connected a new pack no osd showed up. I connected it to betaflight and found out that it reset itself and prompted me to apply custom defaults. I continued to configure it and it was working properly when testing the motors and it seemed fine.

The issue appeared after I tried to apply a cli dump from Darwin FPV, I found 4 cli dumps on their website, 1, 2, 3, 4. I am not sure which one I used, but I think it might be number 3, and I've just realized that it might be for a slightly different flight controller model as it was under "Darwin ELRS2.0 F411 15A Bluejay AIO" in the support page.

Now the flight controller isn't recognized anymore and I get the "Unknown device (device descriptor request failed)" in device manager. I then tried to hold the bootloader button when plugging the FC to enter DFU mode but nothing shows up in device manager and no windows usb plug in sound is played. I have installed the STM32 VCP Driver, and CP210x Driver. I tried to use Zadig and ImpulseRC Driver Fixer but they don't detect the FC. I am using windows 10, and I tried all of this with another windows 11 system and multiple cables but the same behavior appears again.

I made a cli dump before applying Darwin's dump and will send it when I get back home.

#

I read somewhere that I can try and unplug everything from the flight controller to prevent "DFU hijacking" but since it's an all in one board I am not sure if that'll be possible as the spi receiver is always connected internally. So I didn't want to desolder everything else if that's not the issue.

sour walrus
#

Did you disconnect battery while try to enter DFU mode ?

grave sun
#

Yes

sour walrus
#

I just read this #simple-questions message . If there is really no better way, try remove everything and try it again.