FLY-SHT36/42 Bootloader (Katapult) Recovery
FLY-SHT36/42 ships with Katapult pre-flashed. Do not re-flash the firmware on this page during normal use or Klipper firmware updates; this page is intended solely for brick recovery after bootloader corruption.
Firmware Description
Katapult was formerly known as CanBoot, and both names may appear simultaneously in older tutorials or firmware names.
Katapult is a bootloader used to boot and update Klipper:
- Katapult itself cannot be used as a Klipper MCU; after flashing, you still need to write Klipper firmware that matches the hardware and communication method.
- Supported tool boards can enter Katapult by quickly double-pressing the
RESETbutton; after entering, there is usually a status light blinking. - CAN, RS232, and USB use independent Katapult firmware; you cannot simply modify file names or mix them directly.
- For CAN firmware, you must also select the correct bus speed, with common speeds being
500Kand1M.
- This page applies to the STM32F072 version of the FLY-SHT36/42.
- This page provides Katapult firmware for two CAN rates:
500Kand1M.
Select only one firmware that matches your actual CAN network rate. The host, mainboard, and all CAN devices on the same bus must use the same rate.
Entering Flash Mode
Before starting, completely power off the printer and disconnect the power supply. Do not plug or unplug wiring, organize interface cable order, or touch terminals while powered.
The figure marks the BOOT pads:
- Keep the toolboard completely powered off.
- Use a jumper cap to short the
BOOTpads. - Connect the toolboard to your computer or host using a Type-C cable that supports data transfer.
- Once the device is recognized, remove the
BOOTjumper cap.
Flashing Firmware
- Windows
- Linux / FLYOS
Download the FLY-SHT36/42 Katapult firmware:
.txt 或其他扩展名。The firmware directory in the repository is:
FLY-Firmware/ToolBoard/SHT36
- STM32CubeProgrammer
- DFU-AUTO
Before connecting or re-plugging the USB cable, completely shut down the printer and disconnect other power sources. Do not allow the tool board to be powered simultaneously via the printer's power supply and the USB interface.
Some computer USB ports may cause unstable flashing due to driver or signal compatibility issues. If connection fails, try switching to a different USB port on the computer or use a reliable USB hub. If the error shown below appears, check the USB connection and drivers first.
- Download and install
SetupSTM32CubeProgrammerand the STM32 DFU driver from the Auxiliary Software Download Page. - Save the firmware downloaded from this page to a location on your computer that is easy to find.
Windows may hide file extensions. Please check "File name extensions" in File Explorer to confirm the firmware is still in .bin or .hex format. Do not modify the file extension.
- Confirm 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 popup appears, the connection is successful.
- Click the download icon on the left side, and check the flashing options as shown in the image below.
- Click
Browseand select the firmware to be flashed.
- When flashing
.binfirmware, setStart addressto0x08000000. When using.hexfirmware, keep the address embedded in the file.
- Click
Start automatic modeto begin flashing.
- When the success message 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
- Linux
- FLYOS
- 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_SHT36_072_CANBOOT_500K.BINsudo dfu-util -a 0 -d 0483:df11 --dfuse-address 0x08000000 -D ~/FLY-Firmware/ToolBoard/SHT36/FLY_SHT36_072_CANBOOT_500K.BINFLY_SHT36_072_CANBOOT_1M.BINsudo dfu-util -a 0 -d 0483:df11 --dfuse-address 0x08000000 -D ~/FLY-Firmware/ToolBoard/SHT36/FLY_SHT36_072_CANBOOT_1M.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_SHT36_072_CANBOOT_500K.BINsudo dfu-util -a 0 -d 0483:df11 --dfuse-address 0x08000000 -D /data/FLY-Firmware/ToolBoard/SHT36/FLY_SHT36_072_CANBOOT_500K.BINFLY_SHT36_072_CANBOOT_1M.BINsudo dfu-util -a 0 -d 0483:df11 --dfuse-address 0x08000000 -D /data/FLY-Firmware/ToolBoard/SHT36/FLY_SHT36_072_CANBOOT_1M.BIN - If File downloaded successfully appears, flashing is successful.Loading...
Finishing the Flash
After flashing is complete, disconnect the toolboard USB and external power before removing the BOOT jumper cap and restoring normal wiring. Do not plug or unplug toolboard wiring while powered.
After powering back on, the status LED will blink when Katapult starts normally: