USB Firmware Compilation
Start Compilation
Firmware Compilation Quick Guide
Precautions
- Network: Ensure the host machine (Raspberry Pi, etc.) is connected to the network.
- Login Method: Must log in via SSH over the network; serial port login is disabled.
- Input Method: Keep the keyboard in English half-width mode.
SSH Login and User Switching
Use tools like MobaXterm, PuTTY, etc., to SSH into the host machine.
Switching Users:
- Standard Systems (Official Raspberry Pi OS, etc.)
Do not useroot. Switch to a regular user:su <username> - FLY Host Machine (FlyOS-FAST System)
Only supports logging in as therootuser (password:mellow).
Firmware Compilation Operation Guide
In the Klipper firmware configuration interface, only keyboard operations are supported; mouse usage is not possible.
| Key | Function |
|---|---|
| ↑ / ↓ | Move cursor up/down to select menu items |
| Enter / Space | Confirm selection, toggle options, or enter submenus |
| ESC | Return to the previous menu level |
| Q | Exit the configuration interface |
| Y | When exiting, press Y to save the configuration if prompted |
The following describes how to compile the firmware:
-
After connecting to SSH, enter the following command and press the
Enterkey:cd ~/klipper && rm -rf ~/klipper/.config && rm -rf ~/klipper/out && make menuconfig -
Among them,
rm -rf ~/klipper/.config && rm -rf ~/klipper/outdeletes the previous compilation data and firmware, andmake menuconfigcompiles the firmware. After execution, the following interface should appear:Loading... -
Select
Enable extra low-level configuration optionsand press theEnterkey.Loading... -
Enter the menu
Micro-controller Architecture, then selectSTMicroelectronics STM32, and press theEnterkey.Loading... -
Enter the menu
Processor model, selectSTM32H723, and press Enter.Loading... -
Select
Bootloader offset, and choose:128KiB bootloader.Loading... -
Select
Clock Reference (8 MHz crystal), and choose:25 MHz crystal.Loading... -
Communication interface, select:USB (on PA11/PA12).Loading...
- Press the
Qkey, and Save configuration will appear. Then press theYkey.Loading... - The configuration should now be saved, and you will have exited to the command line interface.
- Enter the command below to start compilation. It will take some time.
make -j4
- If the following content is output at the end, the compilation is successful.
- Due to Klipper version differences, as long as
out/klipper.binappears, it indicates success.Linking out/klipper.elf
Creating bin file out/klipper.bin
Confirm Entry into Flashing Mode
- After connecting the mainboard to the host computer using a Type-C cable, double-click the reset button. At this point, the LED on the mainboard will flash.
- If the LED does not flash, please re-flash the katapult firmware: Flash Katapult Firmware
- If the LED does not flash, after flashing the katapult firmware, proceed to the next step.
Flash the Firmware
Start Flashing
- Non-FLY official host software requires installation of Katapult
- Install Katapult
Get the Board ID
Execute the following command to search for the device ID. Normally, an ID similar to the one in the image below should be displayed (Note: Each board has a different ID):
ls /dev/serial/by-id/*
If the searched ID contains
usb-katapult_stm32xxxxxxxx, it means you can proceed to the next step.
Flash the Firmware
- Ensure the firmware file has been compiled.
- Replace
<Your Board ID>in the commands below with the actual ID obtained in the previous step.
- For regular host software, use the following code:
~/klippy-env/bin/python ~/katapult/scripts/flashtool.py -d <Your Board ID> - For FLY host software, use the following code:
python3 ~/katapult/scripts/flashtool.py -d <Your Board ID>
Flashing Process Reference:
Successful Flashing Reference:
Firmware Update
- USB Firmware Update
- Bridged CAN Firmware Update
USB Firmware Update Steps
- Query the Board ID
ls /dev/serial/by-id/*
In the image below, /dev/serial/by-id/usb-katapult_rp2040_E662549553642032-if00 is the board ID.
- Update the Firmware
cd ~/klipper/ && make flash FLASH_DEVICE=<Your Board ID>
- Replace
<Your Board ID>with the actual ID obtained from the query.
Bridged CAN Firmware Update Steps
- Reset to Enter Flashing Mode
<Your Board ID> is the CANBUS UUID of the board in the printer.cfg configuration file.
- For regular host software, use the following code:
~/klippy-env/bin/python3 ~/katapult/scripts/flashtool.py -i can0 -r -u <Your Board ID> - For FLY host software, use the following code:
python3 ~/katapult/scripts/flashtool.py -i can0 -r -u <Your Board ID>
In the image below, f95cee90e1f9 is the board's CANBUS UUID (for example only).
- Query the New Device ID
ls /dev/serial/by-id/*
- This is just a reference!
- In the image below,
/dev/serial/by-id/usb-Klipper_stm32f072xb_38001B000551324752333720-if00is the newly identified board ID.
- Flash the New Firmware
cd ~/klipper/ && make flash FLASH_DEVICE=<Your Board ID>
Solution for Flashing Wrong Firmware
Method One: Quickly Enter Flashing Mode
- Power off the board.
- After powering on again, quickly double-click the RESET button.
- Re-enter flashing mode.