If your board is correctly updated using the Rescue or Manual method but does not connect to the GCS, take a look at the Troubleshooting page.






Update bootloader

Rescue method



The bootloader update should not be needed, except for CC3D or Atom boards flashed using the old v3 bootloader.

Bootloader version 4 is needed for CC3D/Atom or automatic reboot do not work correctly and vehicle wizard will fails.

Bootloaders

Download the appropriate bootloader and go to the Firmware Rescue page.

Coptercontrol (CC)4bu_cc.opfw
CC3D4bu_cc3d.opfw
OPLink Mini4bu_oplinkmini.opfw
Revolution6bu_revolution.opfw
Revolution Nano6

bu_revonano.opfw

Sparky26

bu_sparky2.opfw


Please note all the files above are bu_[BOARD].opfw, if you plan to flash a .bin file the DFU method or ST-Link method should be used.

Unfortunately, the CPU used on the CC3D flight controller does not support the DFU bootloader, see this page for flashing bootloader using a FTDI connected to the main port.  Note that the page seems to be unviewable now and you may need to view it on archive.org.





Update firmware

There is three ways to update or flash a firmware:

Automatic update



This need a working firmware into the board, connecting to the GCS. This is the preferred method when all is fine.

After the board is connected to the GCS, go to the firmware page and click the 'Upgrade' or 'Upgrade&Erase' button.
The board will:

  • reboot automatically,
  • flashed using the appropriate firmware for the board,
  • reboot and erase settings if needed,
  • and finally remains connected, running the new firmware that matches your GCS.



Manual method



This is the preferred method after you flashed a bootloader, the board do not boot (because no firmware running) and there is a slow fading led blinking.

The manual method is similar to the previous automatic method but do not use the automatic reboot at start:

Steps for manual update:

  • Disconnect board from the USB port and disconnect external power (Lipo) if any.,
  • Click the 'Upgrade' or 'Upgrade&Erase' button. (Board still disconnected)
  • Connect board to the USB port

The board will:

  • be recognized just after connected to the USB port,
  • flashed using the appropriate firmware for the board,
  • reboot and erase settings if needed,
  • and finally remains connected, running the new firmware that matches your GCS.



Rescue method



Except if you need to run a custom firmware build locally, or posted in forum this method is not used.

Steps are described here: Firmware Rescue





Firmware update example (automatic)

Bootloader + firmware update example


Led behavior


If board is powered, the 'Power' led is solid green.

Normal operating mode

A slowly blinking blue LED indicates that the board is booted and running the firmware.


 






Bootloader mode

A slow fading in and out of the blue LED indicates that the board is in bootloader mode, need firmware flashing.


 





Error state

A rapidly blinking blue LED during a bootloader update indicates an invalid bootloader image was likely detected and the update hasn't been performed.