Skip to main content

FLYOS-FAST Firmware Compilation Instructions

FLYOS-FAST comes with the Klipper source code and compilation environment pre-installed. Firmware should be configured and compiled on the current device according to the product documentation of the mainboard being used.

Dedicated toolchain architectures are not supported
  • The FLYOS-FAST system does not provide dedicated toolchains such as AVR and PRU, so products requiring these toolchains cannot compile firmware on this machine.
  • For example: BeagleBone PRU and Atmega AVR. Please do not select these architectures in make menuconfig, and do not directly use the corresponding configuration files for system compilation.
Allwinner A64 AR100 is not supported

The FLYOS-FAST system does not support compiling or generating Allwinner A64 AR100 firmware. Even if this platform does not belong to the AVR or PRU architectures, it cannot be compiled locally on FLYOS-FAST.

Compiling on FLYOS-FAST​

  1. Log in to FLYOS-FAST via SSH. The system uses the root user.

  2. Enter the system's preset Klipper directory:

    cd /data/klipper

  3. Open the firmware configuration interface:

    make menuconfig

  4. Select the correct MCU architecture, chip model, clock, communication method, and bootloader offset according to the mainboard product documentation. Do not select architectures that require AVR, PRU, or other dedicated toolchains.

  5. After saving the configuration, start compiling:

    make -j4

The build output is located at:

/data/klipper/out/

The actual filename is determined by the MCU architecture and bootloader configuration, commonly klipper.bin or klipper.uf2. Before flashing, please confirm that the firmware configuration fully matches the mainboard model, communication method, and bootloader offset.

General compilation steps and configuration items: View firmware compilation instructions

When compilation fails

Do not arbitrarily change the MCU architecture, disable security options, or use configuration files from other mainboards just to bypass errors. Please keep the complete terminal output, verify the compilation parameters in the product documentation, and contact technical support.

Loading...