It’s possible that you can brick your Naze32 flight controller due to human error (where Naze doesn’t talk to computer anymore, just timeout or says connection fail). You might still fly the multicopter as normal, but there is no way you can connect the board to Cleanflight/Baseflight configurator.
Causes I can think of are
- Flashed wrong firmware on the Naze32, e.g. flash CC3D rather than Naze.
- Disabled MSP Data on UART1 in Cleanflight Port Tab by mistake
Solution is simple, short the bootloader pins and re-flash firmware again. If it was a Data port settings that causes Naze unable to talk to Cleanflight, you will have to erase all settings on the board too while re-flashing.
Here are the pins you need to short, next to the label “Boot”.
And here are the settings in Cleanflight Firmware Flasher. Here are the stpes:
- Load the correct firmware online.
- With “Flash on Connect” checked, your Naze32 board will be flashed automatically when you connect it to your computer.
After the flash you should be able to connect it to the configurator again.