Hello All,

Flight controller model - https://betafpv.com/products/f4-1s-brush...-no-rx-osd
Betalight currently installed - BTFL 3.5.0
Target: MATEKF411
Issue - bootloader mode not getting activated when I issue command bl in betalight cli.

I have this old FC from old 1s whoop lying around with a R-XSR wired to it. I connected it to computer and it got detected and in betaflight Receiver tab working correctly.
I want to reprupse this FC as my wireless controller for FPL simulator.
This one currently as old version of betaflight (3.5.0), which support only 6 channels in windows game controller. I know that, this is fixed 4.0 above betaflight versions.
So I am trying to upgrade it.

Whenever I issue command bl in betaflight cli, I hear the usb sound, but in betaflight its not showing as DFU.

When normally connects, its come under COM10
when bl command issued, its not coming under Ports in device manager, rather under Sound, video and game controllers as "Guillemot STM DFU Device". I think this is my issue.

   

Any thoughts?


Note: I ran impulse RC driver fix and zadig few times back and forth and trying to fix it, which even made the FC not detectable in normal mode. With great difficulty I was able to fix the normal mode drivers.

Hold down the physical boot button on the FC while plugging in a USB cable. It's the gold coloured micro button on the top of the FC near the edge of the board. Hopefully that will then properly get it into DFU mode.

(22-Apr-2023, 08:54 AM)SnowLeopardFPV Wrote: Hold down the physical boot button on the FC while plugging in a USB cable. It's the gold coloured micro button on the top of the FC near the edge of the board. Hopefully that will then properly get it into DFU mode.

Tried that already, still detected as "Guillemot STM DFU Device" under Sound, video and game controllers.

Try manually removing the Guillemot driver from your computer. Oscar has some steps for how to do that at the link below...

https://oscarliang.com/fc-driver-issues-...-Installed

(22-Apr-2023, 09:30 AM)SnowLeopardFPV Wrote: Try manually removing the Guillemot driver from your computer. Oscar has some steps for how to do that at the link below...

https://oscarliang.com/fc-driver-issues-...-Installed

That worked. Thank you.