[swilker]

In an act of complete stupidity I managed to lock myself out of the usb connection.  Not 100% sure what I did, but I can no longer get Libre Pilot to connect to my CC3D via the USB.  Is there anything I can do?

[TheOtherCliff]

If that is the only problem, then unplug FC power, go to firmware page, press Rescue, plug FC into USB, wait a few seconds for Safe Boot to be available and press Safe Boot.

It will temporarily have ALL default settings, so anything you save will be default unless you change it, so only change what is broken.

Go to the Hardware page and fix and Save and reboot normally.

[swilker]

I must be missing something, here are the screen shots after safe reboot.

[TheOtherCliff]

You must fix the thing that is broken while it is in safe mode.

If you messed up the "Hardware" settings so that it doesn't have USB any more then while in safe mode just go to Hardware and it Save to restore the default settings should fix it.

[swilker]

The Other Cliff,

I can't thank you enough, but this didn't work.  The save button is greyed out.  I'm not sure it ever really connects.  Let me detail my procedure attempt.

Libre Pilot hit rescue, done
Libre Pilot says connect via usb, done
Select Safe Boot, done
Libre Pilot instructs to reconnect telemetry, done
Save button is greyed out. 
Connect via usb not an option does not see port

Thanks again, but I'm still stuck

Drew

[TheOtherCliff]

It should be that once you click "safe boot", you then go to configuration -> hardware, and press save button there.  Or change one small thing there like GPS setting or such and press save button there.

After that you can reboot normally and make changes normally.

[TheOtherCliff]

If that doesn't work, you may need to update the bootloader version.  Search on the wiki...

[Mateusz]

@swilker in your screenshoot with greyed ok button

"Serial: cuBluetooth..." does not look like valid flight controller device. Are you using Windows ? Windows tends to connect automatically to whatever you plug in.
Did you try removing all other USB devices except for flight-controller ?

I wouldn't be surprised that you can't save settings via GCS on for example logitech mouse or bluetooth speakers

In worst case if you can't figure this out, there is SBL method for CC3D which requires usb-serial adapter (3.3V logic level) and flashing ef_cc3d.bin (entire flash = bootloader+firmware).
I do that when I mess up things badly. But perhaps you don't need to do that.

[filnet]

Try _another_ USB port if that is possible and has not been tried before.

[f5soh]

According to your screenshots, seems the Rescue is working, but no firmware on board.

Another strange thing is no information from the bootloader.
Maybe try to update first the bootloader.
Download file here: https://librepilot.atlassian.net/wiki/download/attachments/4128780/bu_cc3d.opfw
Flash bootloader: https://librepilot.atlassian.net/wiki/display/LPDOC/Firmware+Rescue

Do a manual firmware update like explained here:
https://librepilot.atlassian.net/wiki/display/LPDOC/Firmware+Tab#FirmwareTab-Manualmethod

What OS are you using ?
What happens with Leds after you power on ?

[kicekilla]

I had the same issue last night with an old coptercontrol board. Seems to be stuck in boot loader mode. Fading blue led. Windows 10 won't recognize the hardware and says installing the driver failed. Tried uninstalling in device manager but t still wouldn't connect

[f5soh]

Fading led mean the firmware is not flashed. Bootloader is alone.

Do a manual update for firmware.

[kicekilla]

Fading led mean the firmware is not flashed. Bootloader is alone.

Do a manual update for firmware.

silly me, that worked. Thank you. I was just confused about windows not picking it up at all.

[TheOtherCliff]

If you flash a bootloader updater, it overwrites out the main firmware, so you MUST flash normal firmware (using rescue procedure) after flashing a bootloader updater.

[swilker]

All,

Thanks, I didn't have any time to work on this last night but will try again tonight. 

Drew