If this method doesn’t work for you, check with the seller or manufacturer for support.
If you have trouble flashing firmware, play around with the settings, maybe the baud rate is wrong (some boards need 256000), maybe it’s a driver issue. Select “Full Chip Erase” to erase – it will restore the MSP setting for UART1Īfter the flash you should be able to connect it to the configurator again.Select “Flash on Connect”, if you have trouble with flashing: your FC board will be flashed automatically when you connect it to your computer.For example, here are the bootloader pins on the Naze32 you need to short before flashing firmware.Īnd here are the settings in Betaflight or Cleanflight Firmware Flasher. Some boards might have a “boot” button, some have solder pads, it depends. If it was a Data port settings that causes the flight controller to stop talking to Betaflight/Cleanflight, you will have to erase all settings on the board too. Solution is simple, short the bootloader pins and re-flash firmware. On some boards where USB port is shared with UART1, and if you disabled MSP Data on UART1, you won’t be able to connect to the computer using USB again Most modern FC has resolved this issue by separating USB and UART’s by using “USB VCP – virtual com port”.Flashed wrong firmware target to the flight controller, e.g.The issues we have are more like “locking ourselves out”. Actually the word “brick” is a wrong choice, you can’t technically brick a flight controller.