Katapult firmware

Katapult firmware notes

tip

Katapult was originally named CanBoot, and later renamed to katapult.

• Katapult firmware is a type of bootloader that can be used in conjunction with Klipper. After burning the firmware using methods like DFU, you can use commands to update the firmware with one click.
• Advantage: Quickly double-clicking the reset button or quickly cutting power twice will enter the Katapult firmware, at which point there will be an LED flashing on the mainboard.
• Katapult firmware can only be used to burn firmware and cannot connect to Klipper!!!
• Katapult firmware supports three connection methods for connecting to the host computer, and the firmwares for these three methods are independent of each other.
  • CAN connection
    • Advantage: After compiling the KLIPPER firmware, you can directly update the firmware using a command, and it has strong interference resistance.
    • Disadvantage: You need to know the firmware compilation rate in advance.
  • RS232 connection
    • Advantage: After compiling the KLIPPER firmware, you can update the firmware using a command, and it has very strong interference resistance.
    • Disadvantage: You cannot use a command to update the firmware with one click; you need to manually enter the Katapult firmware.
  • USB connection
    • Advantage: After compiling the KLIPPER firmware, you can directly update the firmware using a command.
    • Disadvantage: A long data cable is prone to interference, which may lead to disconnection.

tip

• SHT36 V2 can only use CAN connection
• This provides CAN firmware at 500K and 1M speeds

Notes

• APMF072 can only use computer to burn firmware
• STM32F103 can only use host software to update firmware

Enter programming mode

tip

The one circled is the BOOT switch

• STM32F103 does not need to perform this step！！！！
• With the mainboard completely powered off, press the BOOT button and connect one end of the data cable to the mainboard and the other end to your device
  

Burn firmware

STM32F072 using windows burning tutorial

• Katapult firmware for SHT36_V2
  • Click the download link below
  • Loading...

Notes

• USB3.0 may not be able to burn, please try to use the USB2.0 of the computer for burning
• If there is no USB2.0 interface, please use an extension dock
• If it still cannot be burned, please use the host software for burning

1. Burning tool Download address
2. Need to download SetupSTM32CubeProgrammer and STM32 DFU driver
3. Copy the compiled firmware (klipper.bin) or the pre-compiled Katapult firmware to any directory on the computer
4. Use a Type-C data cable to connect the mainboard to the computer, and make sure it has entered the dfu burning mode
5. In STM32CubeProgrammer, select USB mode, refresh, and connect
   
6. If no error pop-up appears, the connection is successful.
   Warning

   If the content shown in the figure below appears, it is a computer or software problem. Please use the host software for burning:Host software burning tutorial

   
7. Click the left download icon and select the ones below
   
8. Click the Browse indicated by the arrow, then select the firmware you want to burn
   
9. Select Start address and input 0x08000000
   
10. Click Start automatic mode at the bottom to start burning the firmware
    
11. If the following prompt appears, it means the firmware has been burned successfully
    

STM32F072 using host software burning tutorial

1. Install the burning tool

• No need to install the burning tool for the FLY upper computer
• If you need to install, please note: The upper computer needs to be connected to the internet to install normally
• If already installed, no need to install

sudo apt update
sudo apt install dfu-util -y

2. Execute the following command to check if the connection is successful.

lsusb

• If there is no DFU device, please try to re-enter burning mode
• Due to system version issues, other names may be displayed. If 0483:df11 is shown, it indicates that the burning mode has been entered

3. Pull the pre-compiled firmware

• These are all pre-compiled firmwares
• Please note: The upper computer needs to be connected to the internet to install
• The upper computer needs to execute the command below to download the firmware package (if unable to get the file due to network issues on the upper computer, please contact the administrator in the after-sales group)

cd && git clone https://github.com/FengHua741/FLY_Katapult.git

• If the firmware package has already been downloaded, it is recommended to update the firmware package before proceeding with the remaining operations

cd ~/FLY_Katapult && git pull

4. Burn firmware

tip

Only burn one of the firmwares

• Below are the firmware burning instructions for 500K CAN speed

sudo dfu-util -a 0 -d 0483:df11 --dfuse-address 0x08000000 -D ~/FLY_Katapult/developer/SHT36/FLY_SHT36V2_072_500K.BIN

• Below are the firmware burning instructions for 1M CAN speed

sudo dfu-util -a 0 -d 0483:df11 --dfuse-address 0x08000000 -D ~/FLY_Katapult/developer/SHT36/FLY_SHT36V2_072_1M.BIN

5. If the content shown in the arrow in the following figure appears File downloaded successfully then the burning is successful

   

tip

After burning, the mainboard needs to be completely powered off once.

APM32F072 using windows burning tutorial

• Katapult firmware for SHT36_V2
  • Click the download link below
  • Loading...

1. Flashing Tool Download Link
2. Download DFUProgrammer
3. Copy the firmware (klipper.bin) compiled in advance or the pre-compiled Katapult firmware to any directory on your computer
4. Connect the main board to the computer using a Type-C cable, and make sure it has entered DFU flashing mode
5. Open DFUProgrammer and follow the instructions below
   
   
6. Click to start updating the firmware and wait for it to complete, then you can remove the Type-C cable and jumpers.

STM32F103 using klipper to update firmware tutorial

Search for Devices

• Please ensure that the host computer can access the Internet normally and ensure that the data cable connecting the lower computer to the host computer has data transmission function.
• After SSH connecting to the host computer, input lsusb and press Enter. If the information circled in the picture below is displayed, you can proceed to the next step.
  • If there is no feedback information, this is a system problem of the host computer, and we are powerless. You need to replace a confirmed normal system or replace the host computer.
  • If there is no lsusb command prompt, you can execute the following command to install it:

    sudo apt-get install usbutils

    
• 1d50:606f belongs to the device you will use this time.
• Some host computers may not fully display or fail to display due to system problems.
• If the lsusb command can display the device but there is no 1d50:606f, please try to replace the data cable and connect the motherboard to another USB port on the host computer.

Notice

You can proceed to the next step only when there is 1d50:606f.

• Pull pre-compiled firmware
• All of these are pre-compiled firmware
• Please note that the host software needs to be able to access the internet to install
• The host software needs to execute the following command to download the firmware package

cd && git clone https://github.com/FengHua741/FLY_Katapult.git

• It is recommended to update the firmware package if you have already downloaded it before proceeding with the remaining operations

cd ~/FLY_Katapult && git pull

• This method directly updates the original Katapult firmware on the toolboard via the CAN update tool
• Replace <Toolboard ID> with the CAN ID of the STM32F103 controller's toolboard
• Below is the firmware update instruction for the 103 version at 1M CAN speed

~/klippy-env/bin/python ~/klipper/lib/canboot/flash_can.py -f ~/FLY_Katapult/developer/SHT36/FLY_SHT36V2_103_1M.BIN  -u <Toolboard ID>

• Below is the firmware update instruction for the 072 version at 500K CAN speed

~/klippy-env/bin/python ~/klipper/lib/canboot/flash_can.py -f ~/FLY_Katapult/developer/SHT36/FLY_SHT36V2_103_500K.BIN  -u <Toolboard ID>

Confirm if the firmware starts

• If the firmware starts normally, the LED will blink