Installing Rotorflight Firmware - rotorflight/rotorflight GitHub Wiki

❗ This page is outdated

Rotorflight Wiki is replaced by www.rotorflight.org.


Install Rotorflight Configurator

Start by downloading and installing the latest Rotorflight Configurator release. This walk-through uses Windows, but it should also work on Linux or macOS.

Install Drivers

On Windows, install the STM USB Drivers from the links on the Rotorflight Configurator page.

Back up Betaflight Config

Rotorflight is based on Betaflight and uses the Betaflight configuration as its base. You should make a copy of the configuration that the flight controller (FC) shipped with. Back up the Betaflight configuration as shown in Back up and restore.

Flash Firmware to FC

Connect the FC to your computer with an USB data cable. Now you are ready to install the Rotorflight firmware to your FC. There are five different versions of the firmware, each version targeting a specific microprocessor: F405, F411, F7X2, F745, and H743. Your FC must use one of those processors. Besides firmware, each FC has it's own configuration. The configuration specifies the FC board, e.g. what pads are used for what.

Step 1.

  • Identify the Betaflight target. This can be found in the dump file specified by board_name saved in your backup or on the manufacturers website.

Step 1

Step 2.

  • Open the Rotorflight configurator and click on [Update Firmware]
  • Chose All release and Snapshots from the dropdown
  • Select the Target you identified in Step 1.
  • Select Full chip Erase. This will remove all previous configurations.
  • Click on [Load firmware[online]]

Step 3.

  • Check and confirm the target board is correct.
  • Click on [Flash Firmware]

Step 4.

  • When the programming is successful click on [Connect].
  • Click [Apply Custom Defaults] from the popup. The FC will now reboot.

Step 5.

  • Configure the pin remapping. There are two options for this:
  1. If you have one of the boards listed in the Boards and Configuration Files section of the wiki (e.g. Matek F722 wpx) you can use a pre-configured custom defaults config file. These files have already had pins remapped for servos and motors. Choose a pin configuration (e.g. (a), (b) etc) that suits your helicopter best and either the Motorised Tail (MT) or Servo Tail (ST) as required. These files can be downloaded from the Rotorflight-targets repo. See the Custom Defaults page for more info. If this is your first Rotorflight controller or have no experience remapping pins then we recommend this method. If you have a different board and wish to use this method please ask on the Discord discussion and we can build one.

  2. The second option is to manually re-map your pins to add your servos and motors, or by using the Custom defaults remapping spreadsheet.

Troubleshooting

'Initiating reboot to bootloader' hangs

If you're on Windows and it hangs while displaying Initiating reboot to bootloader, you'll need to install the proper driver for the STM32 BOOTLOADER device.

  • Make sure the device STM32 BOOTLOADER is installed and showing up in the Device Manager, either under Other Devices or under Universal Serial Bus devices. Select View > Show Hidden Devices in order to see all installed devices.
    • You might need to uninstall all STM Device in DFU Mode devices under Universal Serial Bus Controllers before Windows will install the STM32 BOOTLOADER device. Make sure to check Delete the driver software for this device.
  • In the Configurator, go to the CLI and type dfu. This puts the FC in Device Firmware Update mode.
  • Start Zadig (see download link on the Welcome tab in the Configurator), select Options > List all Devices, select STM32 BOOTLOADER and change the driver to WinUSB. Flash firmware should now work.

Zadig

Error 'Rebooting device to bootloader: FAILED'

If you receive the error Rebooting device to bootloader: FAILED then you will need to manually place the FC into bootloader mode. Do this by holding down the BOOT button while connecting it to your computer.

Help... that didn't work. Its bricked!

Ok, so after rebooting you are no longer able to connect to the FC via USB. This can happen if your configuration file is not correct (USB becomes unalocated) or if you have loaded the incorrect firmware for the processor type. Don't worry: the bootloader can't be bricked, it's in ROM. You can always reload the firmware via the DFU (device firmware update) mode. Most flight controllers have a 'boot' button or pins which are used to enter DFU mode. Generally you can just enter DFU mode by pushing the button or bridging the boot pins as you plug the USB in (while the Rotorflight Configurator is open).

Boot Pins

Rotorflight Configurator will display DFU - STM32 BOOTLOADER at the top of the page after a successful DFU connection. Click on the Update Firmware and follow the steps above to re-flash the firmware as required.

Boot Pins

Next: Proceed to Manual Setup.

⚠️ **GitHub.com Fallback** ⚠️