Skip to main content

rs232

Schematic Diagram of KF Wiring​

Schematic Diagram of XT30 Wiring​

RS232 Firmware Compilation

Start Compilation​

  • A host machine with the installed klipper service is required Connect via SSH over the network
  • Make sure the device is connected to the host machine
  • Note: Please use a regular host machine, such as a Raspberry Pi FLY board, etc. If it's a modified host machine (e.g., WiFi stick, Redmi, etc.), due to too many issues, we cannot provide technical support for these machines
warning
  • To switch from the ROOT user to a regular user, you can enter the command below
  • Do not use the ROOT user
  • For the fly user, you can directly enter: su fly. For non-fly users, please replace <your host machine username> with your host machine's username!
su <your host machine username>
tip
  • 请确保上位机可以正常联网
  • 固件编译前需要使用SSH通过网络登录上位机
  • 请不要使用串口工具登录上位机

Klipper固件编译和配置页面操作说明​

tip

请确保键盘输入法为半角模式，即英文模式

  1. 键盘上键↑，下键↓，用于上下移动光标来选中菜单项
  2. 确认键Enter 或 空格键Space，用于勾选菜单或进入子菜单
  3. 退出键ESC，用于返回上一级菜单
  4. Q键，用于退出Klipper固件配置页面
  5. Y键，在退出Klipper固件配置页面时，如果有提示，则点击Y键保存配置文件
warning

如果配置页面选项比较少，请先勾选[ ] Enable extra low-level configuration options，用于显示部分隐藏选项

Below is an introduction on how to compile the firmware:

  • After connecting to SSH, enter the following command and press Enter:

    cd ~/klipper && rm -rf ~/klipper/.config && rm -rf ~/klipper/out && make menuconfig

  • Where rm -rf ~/klipper/.config && rm -rf ~/klipper/out is to delete previous compilation data and firmware, make menuconfig is to compile the firmware, after execution, the following interface should appear

  • Select Enable extra low-level configuration options and press Enter

  • Enter the menu Micro-controller Architecture then select Raspberry Pi RP2040 and press Enter

  • Select Bootloader offset, select: NO bootloader

  • Select Communication interface, select: UART0 on GPIO0/GPIO1

  • Select GPIO pins to set at micro-controller startup, enter: !gpio18
warning

Please enter !gpio18 in English input mode

  • Press Q key, Save configuration will appear, then press Y key
  • The configuration should now be saved and you should exit to the command line interface
  • Enter make -j4 to start compilation, it takes some time
  • If the following content is output, the compilation is successful

Enter Burning Mode​

tip

The arrow points to the BOOT button

  • With the tool board completely powered off, press and hold the BOOT button, connect the tool board to your computer's USB port using a Type-C data cable with data transfer function, and release the BOOT button after correctly connecting to the computer

Confirm Whether Entering Burning Mode​

  • Please ensure that the host machine can connect to the network normally, and ensure that the data cable connecting the peripheral machine to the host machine has data transmission function.
  • After SSH connecting to the host machine, enter lsusb and press Enter. If the information circled in the following image is displayed, you can proceed to the next step.
    • If there is no feedback information, this indicates a system issue with the host machine, and we are unable to help. You need to replace it with a confirmed normal system or replace the host machine.
    • If the prompt says there is no lsusb command, you can execute the following command to install it: 
      sudo apt-get install usbutils
  • 2e8a:0003 belongs to the device you will be using this time. The suffix Raspberry Pi RP2 Boot has some reference value but is not used as a basis for judgment.
    • Some host machines may display incompletely or not at all due to system issues.
    • If entering the lsusb command displays the device but does not show 2e8a:0003, please try replacing the data cable and attempt to connect the motherboard to another USB port on the host machine.
Note

You can only proceed to the next step when there is 2e8a:0003.

Burn RS232 Firmware​

  • Please note that the current toolboard is in firmware burning mode and can only burn firmware with a .uf2 suffix.
  • Use the following command to burn the firmware to the toolboard.
cd && cd ~/klipper/
make flash FLASH_DEVICE=2e8a:0003
tip

If this is the first burn after writing the system with the host machine, you may see a prompt similar to the one circled in red below — partial red prompts are normal and not an error.

Confirm Whether Firmware Starts​

  • If the firmware starts normally, the LED shown in the figure below will light up