Welcome to Firefly
English
Firefly Docsss
Last Updated: 2026-11-18 14:24:01

USB Firmware Upgrade

Introduction

This section describes how to flash firmware from a host to the storage of the Firefly-R3572A motherboard through a Type-C data cable. Choose the upgrade method according to the host OS and the firmware type.

Resources

Contact the sales team (sales@t-firefly.com) for the download links of the firmware, AndroidTool, the RK USB driver, Linux_Upgrade_Tool, adb/fastboot and SD_Firmware_Tool.

Preparatory Tools

  • Firefly-R3572A motherboard
  • 12V/3A power adapter
  • Firmware (update.img or partition images)
  • A host PC (Windows or Linux)
  • A working Type-C data cable (connects the board Type-C OTG port to the host)

Prepare Firmware

Firmware can be obtained by compiling the SDK, or as a public release (unified firmware) from the sales team. There are generally two forms:

  • A single unified firmware

    A unified firmware packs the partition table, bootloader, U-Boot, kernel, system and all other files into one file. All Firefly official releases use the unified firmware format. Upgrading with a unified firmware updates the data and partition table of all partitions and erases all data on the board.

  • Multiple partition images

    Independent files for each function, such as the partition table, bootloader and kernel, generated during development. Partition images can update only selected partitions while keeping the data of other partitions intact, which is convenient for debugging.

Tip

The unified firmware unpack/pack tool converts a unified firmware into partition images, and merges partition images back into a unified firmware.

Install the Upgrade Tool

Windows

  • Install the RK USB driver

Download Release_DriverAssistant.zip, extract it, and run DriverInstall.exe. To make all devices use the newer driver, choose "Driver Uninstall" first, then "Driver Install".

  • Run RKDevTool.exe from AndroidTool

Note

To avoid flashing problems caused by tool versions, use the tool bundled inside the public firmware archive.

AndroidTool can also be extracted separately; run RKDevTool.exe from the RKDevTool_Release_v2.xx directory (on Windows 7/8, right-click and choose "Run as administrator"). The interface is shown below:

Linux

No device driver is needed on Linux.

  • Linux_Upgrade_Tool

Extract Linux_Upgrade_Tool_xxxx.zip and install it for easy invocation:

unzip Linux_Upgrade_Tool_xxxx.zip
cd Linux_UpgradeTool_xxxx
sudo mv upgrade_tool /usr/local/bin
sudo chown root:root /usr/local/bin/upgrade_tool
sudo chmod a+x /usr/local/bin/upgrade_tool
  • Linux_adb_fastboot

Extract it and install the tools:

sudo mv adb /usr/local/bin
sudo chown root:root /usr/local/bin/adb
sudo chmod a+x /usr/local/bin/adb
sudo mv fastboot /usr/local/bin
sudo chown root:root /usr/local/bin/fastboot
sudo chmod a+x /usr/local/bin/fastboot

Enter Upgrade Mode

There are two upgrade modes: Loader mode and MaskRom mode. Connect the device and put the board into an upgradable mode before flashing.

Loader Mode

Enter Loader mode by hardware

The board provides Recovery, MaskRom, Reset and Power buttons; their locations are shown below (bottom side of the board).

Connect the device and enter Loader mode with the RECOVERY button:

  • Disconnect the power adapter.
  • Connect one end of the Type-C data cable to the host and the other to the board Type-C OTG port (see the Interface Description).
  • Hold the RECOVERY (recovery) button on the board.
  • Connect the power.
  • Release the RECOVERY button after about two seconds.

Enter Loader mode by software

With the Type-C data cable connected, run the following command in the serial debug terminal or adb shell:

reboot loader

Check Loader mode

Windows

AndroidTool shows Found One LOADER Device at the bottom:

If the tool does not show LOADER after the steps above, check whether Windows reports new hardware and configures the driver. Open Device Manager; a new Rockusb Device appears as shown below. If not, return to the driver installation step.

Linux

Running upgrade_tool shows a Loader entry among the connected devices:

firefly@T-chip:~/severdir/down_firmware$ sudo upgrade_tool
List of rockusb connected
DevNo=1 Vid=0x2207,Pid=0x330c,LocationID=106    Loader
Found 1 rockusb,Select input DevNo,Rescan press <R>,Quit press <Q>:q

MaskRom Mode

MaskRom mode is the last resort for a bricked device. Forcing the device into MaskRom involves hardware operations and carries some risk, so try it only when the device cannot enter Loader mode. The principle is to short the eMMC data pins to ground manually, so the system considers the eMMC data invalid and clears it.

Warning

Read carefully and proceed with caution.

Steps:

  1. Disconnect the power.
  2. Hold the MaskRom button on the board (location shown below, bottom side).
  3. Keep the button held, connect the power, and release it after about 3 seconds.

The device is now in MaskRom mode, and the tool shows:

Flash the Firmware

Windows

Flash the unified firmware update.img

  1. Switch to the Upgrade Firmware tab.
  2. Click Firmware and open the firmware file; the tool displays detailed firmware information.
  3. Click Upgrade to start.
  4. If the upgrade fails, click EraseFlash to erase the Flash, then upgrade again.

Flash partition images

  1. Switch to the Download Image tab.
  2. Check the partitions to flash (multiple selection is supported).
  3. Confirm that the image paths are correct; click the blank cell to the right of a path to reselect it if needed.
  4. Click Run to start. The device reboots automatically when the upgrade finishes.

Linux

Flash the unified firmware update.img

sudo upgrade_tool uf update.img

Note

If the upgrade fails, erase the Flash first and then upgrade again.

# The ef argument for erasing flash needs a loader file or the corresponding update.img
sudo upgrade_tool ef update.img   # update.img is the firmware to flash
# Flash again
sudo upgrade_tool uf update.img

On this page