Katapult firmware
Katapult firmware description
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.
- CAN connection
tip
- SHT36 LIS3DH supports CAN
- Only CAN firmware with 500K and 1M rates is provided here
Enter programming mode
tip
The circled one is the BOOT button
- With the mainboard completely powered off, short the BOOT button and connect one end of a data cable to the mainboard and the other end to your device
- Then release the short on the BOOT button
Programming the firmware
- Windows programming tutorial
- Host programming tutorial
- Katapult firmware for SHT36_LIS3DH Click to automatically download the firmware
- Prepare a data cable with data transfer capabilities.
- Download the firmware to the computer.
- Connect the BOOT jumper or hold it and connect it to the computer, at this point the
RPI-RP2
disk will appear. - Remove the BOOT jumper or release the button!!!
- Copy the firmware that needs to be burned into it, please note that only
UF2
suffix firmware can be used!!! (Do not modify the suffix name, it is useless.) - Refer to
- After copying the firmware into the
RPI-RP2
disk, it will automatically disappear, indicating that the firmware burning is complete!
-
Install the flashing tool
- Enter the following command in SSH
- Only need to execute it for the first flash, no need to execute again later
cd ~/klipper/lib/rp2040_flash/ && make
-
Execute the following command to check if the connection is successful.
-
Enter
lsusb
-
If there is no
2e8a:0003
device, try re-entering flash mode -
Due to system version issues, it may display other names. If
2e8a:0003
is present, it means the flash mode has been entered
NotesProceed to the next step only when
2e8a:0003
is present -
-
Pull the pre-compiled firmware
- All are pre-compiled firmware here
- Please note that the host computer needs to be online to install
- The host computer 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
- Program the firmware
tip
Only one of the firmwares needs to be programmed
-
The following is the firmware programming command for 500K CAN rate
sudo ~/klipper/lib/rp2040_flash/rp2040_flash ~/FLY_Katapult/BL/SHT36/FLY_SHT36LIS3DH_CANBOOT_CAN_500K.uf2
- The following is the firmware programming command for 1M CAN rate
sudo ~/klipper/lib/rp2040_flash/rp2040_flash ~/FLY_Katapult/BL/SHT36/FLY_SHT36LIS3DH_CANBOOT_CAN_1M.uf2
-
If the following prompt appears, the programming is successful
tip
After programming, the mainboard needs to be completely powered off once.
Confirm if the firmware starts
- If the firmware starts normally, the LED will blink
