Hey everyone.
I successfully flashed my aio whoop board from namelessrc from 4.0.x to 3.5.7 and now I can’t connect in normal mode.

I downgraded to get smart audio working on an AKK nano vtx that only works with smart audio. I’ve had this problem before when bf 4.0.x had a different smart Audi to bf 3.5.x. In the past I have downgraded and got the vtx to work.

In this case the target for the namelessrc aio whoop board is matekf411.

I launch the board in boot mode and can flash the board ok. Remove power and connect USB again and it won’t connect in regular mode to configure it.

I used zadig to get it going in boot mode but it only worked when I pressed the boot button at power on. Other fc boards haves worked in the past by just typing BL in the cli and it has entered the mode ok.

My thought is that I’ve screwed up the usb driver connection by loading zadig and stm etc.

Is there anything anyone recommends I do to clean up my software install to be able to connect again to the namelessrc aio whoop board?

I had it working ok before the downgrade to 3.5.7 and configured it and all was ok, modes, serial rx, everything ok - I just wanted to get smart audio going for the Vtx.

Any suggestions? Sorry for the ramble.

Cheers,

ph2t.

What BFC version are you using?

When you in the FC normally, does a COM get assigned to your FC? What does the device manager populates when you plug in your FC?

Hi voodoo, thank you for the response. I think it’s the laptop as I plugged into wifeys and it’s ok.

Also tried a hobby wing stack in my five inch and that had the same problems.

I am reimaging my laptop at work and will give it a go tonight, should be fine.

Cheers,ph2t.

I think it is probably a driver issue. Let me know if you are still having issue.

All sorted, once I reimaged my laptop (a bit of a nuke option I know but it's a work laptop and the data is all cloud) it was fine. No need for USB drivers and COM3 appeared in BFC OK.

thankyou,
ph2t.

Very good