FLY-LLL Flux Buffer Firmware Flashing
This page applies to devices with firmware versions lower than v2.0.0. For v2.0.0 and above, you can update directly through the web tool without entering DFU. Please refer to Firmware Update.
Check Firmware Version
After connecting the device via the FLY-LLL Flux Buffer Configuration Tool, you can view the current firmware version in "Device Information".
Enter DFU Flash Mode
Before starting, completely turn off the printer and disconnect power from the control board. Do not plug or unplug the Type-C data cable, manage wiring, or touch terminals while powered on.
The control board is located on the buffer assembly. Refer to the silkscreen on the board for the Type-C port and button locations. You can enter DFU using either of the following methods:
-
Method 1:
- Connect the control board to the computer using a Type-C data cable that supports data transfer.
- Press and hold the BOOT button on the board (silkscreened as
BOOT0on some batches), then briefly press RESET (NRST). - Release RESET first, then release BOOT.
-
Method 2:
- Press and hold BOOT first.
- Connect the Type-C data cable between the control board and the computer. Release BOOT once the computer recognizes the device.
The channel buttons on the control board cannot substitute for BOOT / RESET. Please operate only after confirming the silkscreen labels. If DFU still cannot be recognized after multiple attempts, power off first and check the data cable and buttons.
After entering DFU, 0483:df11 should appear in lsusb on the computer. If it does not appear, please repeat the entry steps above.
Flash Firmware
- WIN Flashing
- Linux Flashing
- FLYOS Flashing
Please download the complete firmware with Bootloader:
.txt 或其他扩展名。- STM32CubeProgrammer
- DFU-AUTO
Before connecting or reconnecting the USB cable, completely turn off the printer and disconnect all other power supplies. Do not let the tool board be powered simultaneously through the printer power supply and the USB interface.
The USB interfaces on some computers may cause unstable flashing due to driver or signal compatibility issues. If the connection fails, try using a different USB interface on the computer or use a reliable-quality USB dock; when the error shown below appears, also check the USB connection and driver first.
- Download and install
SetupSTM32CubeProgrammerand the STM32 DFU driver from the auxiliary software download page. - Save the firmware downloaded on this page to a location on your computer that is easy to find.
Windows may hide file extensions. In File Explorer, check "File name extensions" to confirm that the firmware is still .bin or .hex, and do not change the file extension.
- Confirm that the device has entered DFU flashing mode according to the product tutorial, then connect it to the computer using a USB cable that supports data transfer.
- Open STM32CubeProgrammer, select USB mode, refresh the device list, and connect.
- If no error pop-up appears, the connection is successful.
- Click the download icon on the left, and check the flashing options as shown in the figure below.
- Click
Browseand select the firmware to be flashed.
- When flashing
.binfirmware, setStart addressto0x08000000; when using.hexfirmware, keep the address included in the file.
- Click
Start automatic modeto begin flashing.
- When the success prompt appears, the firmware flashing is complete.
Before connecting or reconnecting the USB cable, completely power off the printer and disconnect other power sources. Do not let the toolboard be powered simultaneously by both the printer power supply and the USB interface.
- Download and run FLY DFU-AUTO.
- If the "Driver Status" shows unavailable, click "Install Driver" to complete the WinUSB driver installation.
- Click "Browse" to select the
.binfirmware file to be flashed.
Windows may hide file extensions. In File Explorer, check "File name extensions" to confirm the firmware remains as .bin. Do not modify the file extension.
- Click "Start Flashing", monitor progress through the run log, and wait for the flashing process to complete.
Detailed Tutorial: FLY DFU-AUTO Download and Usage
- Install flashing tool.sudo apt updatesudo apt install dfu-util -y
- Confirm the device has entered DFU flashing mode.lsusb
If you can see 0483:df11, it means DFU flashing mode has been entered successfully.
Loading... - Pull/update firmware repository.git clone https://cnb.cool/3dmellow/FLY-Firmware ~/FLY-Firmwarecd ~/FLY-Firmware && git pull --ff-only
- Flash firmware.
FLY-LLL-FLUX-BUFFER-V2.0.8-mergedBL.binsudo dfu-util -a 0 -d 0483:df11 --dfuse-address 0x08000000 -D ~/FLY-Firmware/ExtensionBoard/LLL-FLUX-BUFFER/mergedBL/FLY-LLL-FLUX-BUFFER-V2.0.8-mergedBL.bin - If File downloaded successfully appears, flashing is successful.Loading...
- FLY host computer usually has dfu-util built-in, no need to install flashing tool again.
- Confirm the device has entered DFU flashing mode.lsusb
If you can see 0483:df11, it means DFU flashing mode has been entered successfully.
Loading... - Pull/update firmware repository.git clone https://cnb.cool/3dmellow/FLY-Firmware /data/FLY-Firmwareln -s /data/FLY-Firmware /root/FLY-Firmwarecd /data/FLY-Firmware && git pull --ff-only
- Flash firmware.
FLY-LLL-FLUX-BUFFER-V2.0.8-mergedBL.binsudo dfu-util -a 0 -d 0483:df11 --dfuse-address 0x08000000 -D /data/FLY-Firmware/ExtensionBoard/LLL-FLUX-BUFFER/mergedBL/FLY-LLL-FLUX-BUFFER-V2.0.8-mergedBL.bin - If File downloaded successfully appears, flashing is successful.Loading...
DFU flashing must use the complete firmware in the mergedBL directory. The application firmware in Product-Firmware does not include the Bootloader and cannot be used for DFU flashing on this page.
Do not disconnect the Type-C connection or operate the control board buttons during flashing, otherwise flashing may fail.
Next Steps
After flashing is complete, the device will restart and gain web update capability. When upgrading the main firmware later, simply refer to Firmware Update; there is no need to enter DFU again.
If the device still fails to start after DFU flashing is complete, power off and power on again first, then check whether the Type-C data cable, BOOT / RESET operation, and firmware file match.