so after trying to upload the Klipper to the printer, which was partially successful, there was a message about uploading the software and the screen stopped working. but no, mainsail didn’t see the motherboard, so I downloaded the file you sent earlier and simply put it on the SD card and inserted the card into the printer and after a short while it was like it was originally
Lol. Can you send a screenshot of mainsail main page?
Yes but i have the same mcu error.
try ls /dev/serial/by-id/*
No such file or directory
Running Debian Bullseye?
try running sudo apt -y update && sudo apt -y upgrade apt-cache policy udev
and send the terminal output to us
sudo apt -y update && sudo apt -y upgrade && apt-cache policy udev
Compare your command with what I have posted
klippy (5).log (111.5 KB)
I’m not sure what the current status here is. Generally:
- @filos5 - a serial is shown, which is good
- “Unable to connect” usually means that the firmware is not correctly flashed but hard to tell if the settings for this board are wrong to begin with or if it is another issue
What exact MCU type is used on these boards? There are also conflicting information in this thread.
bbrruuuuhh, i need to investigate
I have it on the motherboard, and I took the setting from the Internet, hoping that it would at least connect to the printer and then change the pins and values.
A GD32F303 should be straight forward to flash:
- 28KiB bootloader
- Serial on USART1 PA10/PA9
- Flash firmware by copying “out/klipper.bin” to a SD card
- The firmware filename must end in “.bin” and must not match the last filename that was flashed.