Howdy,

    I have a couple F3EVO Brushed boards. From QX80, QX90, and purchased separately. One of them will not connect.

    I flew the boards with stock Cleanflight and only experimented with PID's.

    On one of the boards I jumped the boot loader, connected in DFU and flashed Betaflight. Easy peasy. I un-jumped the boot loader, connected and com connection was an option. Opened the FC and set it up the way I like. Fly's great.

     On another board, when I un-jump the boot loader, there is no com connection option. Can't get it to connect to configure the board. It is flashed successfully with Beatflight. I can jump the boot loader and go back to Cleanflight. When I un-jump the boot loader there is no ability to connect.

     Your thoughts and opinions would be appreciated.

so you can flash firmware, and connect to the configuartor when bootloader is shorted?
can you try flashing the firmware without the bootloader shorted?

(12-Feb-2017, 02:12 PM)Oscar Wrote:

---

so you can flash firmware, and connect to the configuartor when bootloader is shorted?
can you try flashing the firmware without the bootloader shorted?

If I try to flash firmware with the bootloader not shorted, it says failed to open serial port.

I can not connect to the configurator at all.

with the boot loader shorted, I can flash all day long. with the boot loader unshorted, I can't do anything.

It might not help, but can you try a different USB cable (or two)? (Surely you have some extras around from phones or other devices.)

I have two USB cables that work for programming. The same cables worked with this board when I was using cleanflight and adjust PID's. I use these cables with the other F3EVO boards.

Something has happened to board and I am trying to figure out how to recover it.

Have you tried different versions of betaflight? I just read of certain boards that have the vcp connection disabled by default in the latest releases... They would show the symptoms you describe. Connecting over FTDI would maybe work...

Maybe it works with an older version? 3.0.1 should be fine afaik.

Lots of "maybe", i know... really just guessing.

Ps: try disabling "full erase" too, on some of my boards that's the only thing causing trouble. And restarting configurator often is required too...

There is a problem with my computer.

The "good" board stopped connecting. I plugged it into the tablet I use for tuning in the field and it worked fine. So, I tried the "bad" board and was able to get it to connect.

The "bad" board would not save the configuration tab settings. When I clicked save and reboot, it reverted to the old settings.

I did a cli dump of the "good" board and copied that file to the "bad" board. Now it is working fine.

Both boards fly great with the stock 3.1.5 spracingf3evo firmware.

Thank you all for taking the time and trying to help. Now I need to find a computer savvy person to help unclog all this driver junk.

Again, thanks to everybody for their assistance.

Update:  Everything is working on the laptop again. I changed drivers in Zadig to USB serial and both boards connect again.