Basic Information:
Printer Model: Alfawise u20
MCU / Printerboard: SKR3 V3 STM32H723
klippy.log
Description :
Hey everyone,
I’ve got an SKR3 board, and I feel like the millionth person facing issues with it. Here’s the situation:
I followed the standard flashing process with the .bin
file, but ran into problems at a key point.
Issue 1:
When I flash the stock firmware-usb.bin
from the official GitHub repo, everything goes smoothly.
The file changes to FIRMWARE.cur
, and the status LED turns off as expected.
However, when I try flashing Klipper (after renaming it to firmware.bin
), the status LED never turns off.
The file gets renamed to : FIRMWARE.cur
, but something’s still wrong, and the board doesn’t seem to complete the process.
Issue 2:
Assuming the flashing with the original file worked, I tried moving forward.
I used the command ls /dev/serial/by-id/
to check for the device, but it doesn’t seem to exist.
When I ran ls /dev
, there’s no “serial” listed either.
Here’s what I’ve already tried:
- Swapped USB cables and confirmed the one I’m using supports data transfer.
- Checked the Raspberry Pi’s USB ports with other devices—no issues there; they’re detected with
lsusb
. The only thing not showing up is the SKR3. - Confirmed that the CAN/USB switch is in the correct (released) position.
At this point, I gave up on USB and tried connecting the SKR3 to the Pi via UART:
- PA10 > GPIO15
- PA9 > GPIO14
- GND > GND
Even with the .bin
file from GitHub, it didn’t work.
Does anyone have any suggestions on what to try next? I’d appreciate any help!