USB Firmware Compilation
Connect to Host Computer
The Fly-D8 mainboard can only communicate with the host computer for Klipper via the Type-C USB interface.
Below is an introduction on how to compile the firmware:
-
After connecting via SSH, enter the following command and press the
Enterkey:cd ~/klipper && rm -rf ~/klipper/.config && rm -rf ~/klipper/out && make menuconfig -
Here,
rm -rf ~/klipper/.config && rm -rf ~/klipper/outdeletes 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... -
Navigate to the
Micro-controller Architecturemenu, then selectSTMicroelectronics STM32and press theEnterkey:Loading... -
Enter the
Processor modelmenu, selectSTM32H723, and press Enter:Loading... -
Select
Bootloader offsetand choose:128KiB bootloader:Loading... -
Select
Clock Reference (8 MHz crystal)and choose:25 MHz crystal:Loading... -
For
Communication interface, select:USB (on PA11/PA12):Loading...
- Press the
Qkey, and when Save configuration appears, press theYkey:Loading... - The configuration should now be saved, and you will exit back to the command line interface.
- Enter the following command to start compilation. This may take some time:
make -j4Loading... - 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
Enter Flashing Mode
- After connecting the mainboard to the host computer using a Type-C data cable, double-click the RST button. At this point, the LED light on the mainboard will flash.
- If the LED light does not flash, please re-flash the katapult firmware: Flash katapult firmware
- If the LED light does not flash, after flashing the katapult firmware, proceed to the next step.
- Please ensure that the host machine can connect to the network normally and ensure that the data cable connecting the lower-level machine to the host machine has data transmission function.
- After SSH connecting to the host machine, input
lsusband press Enter. If the information circled in the following picture appears, you can proceed to the next step.- If there is no feedback at all, this is a system problem of the host machine, and we are unable to help. You need to replace with a confirmed normal system or replace the host machine.
- If the prompt says there is no
lsusbcommand, you can execute the following command to install it:sudo apt-get install usbutilsLoading...
1d50:6177belongs to the device you will use this time.- Some host machines may not fully display or fail to display due to system problems.
- If the
lsusbcommand can display the device but does not show1d50:6177, please try replacing the data cable and connecting the mainboard to another USB port on the host machine.
- If you have executed the above steps before and successfully burned the Klipper firmware, and the mainboard is running normally, but you just want to update the Klipper firmware, please directly check the
Firmware Updatesection in the right menu bar of this page.
You must query the 1d50:6177 device before proceeding to the next step.
Flash Firmware
Start Flashing
- Internet connection is required when installing the flashing plugin. Please ensure your host computer is connected to the internet.
- If the flashing plugin is already installed, there is no need to reinstall it.
Install Flashing Dependencies
If you are using a non-Fly official host computer, you must execute the following command to install the firmware flashing dependency package!
- GitHub Repository
- Domestic Mirror
cd && git clone https://github.com/Arksine/katapult.git
cd && git clone https://gitee.com/MrCakeFuck/katapult.git
Get Board ID
Execute the following command to search for the device ID. Normally, an ID similar to the one shown in the image below should be displayed (Note: The ID is different for each board):
ls /dev/serial/by-id/*
Flash Firmware
- Ensure the firmware file has been compiled.
- Replace
<Your Board ID>in the command below with the actual ID queried in the previous step.
- Standard Host
- Fly Host Flashing Tutorial
~/klippy-env/bin/python ~/katapult/scripts/flashtool.py -d /dev/serial/by-id/<Your Board ID>
python ~/katapult/scripts/flashtool.py -d /dev/serial/by-id/<Your Board ID>
Flashing Process Reference:
Successful Flashing Reference:
Firmware Update
- USB Firmware Update
- Bridged CAN Firmware Update
USB Firmware Update Steps
- Query 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 Firmware
cd ~/klipper/ && make flash FLASH_DEVICE=<Your Board ID>
- Replace
<Your Board ID>with the actual queried ID.
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.
- Fly-Armbian/Standard Host
- Fly-FAST System
~/klippy-env/bin/python3 ~/katapult/scripts/flashtool.py -i can0 -r -u <Your Board ID>
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 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 recognized board ID.
- Flash New Firmware
cd ~/klipper/ && make flash FLASH_DEVICE=<Your Board ID>
Solution for Flashing Wrong Firmware
Method 1: Quickly Enter Flashing Mode
- Power off the board.
- After powering on again, quickly double-click the RESET button.
- Re-enter flashing mode.