This looks like the classical issue described at Issues flashing the printer board.
- Verify your settings.
- Try different SD cards.
While you’re at it, I’d recommend switching to Katapult.
- Use the same settings as you would for building Klipper.
- Build the deployer app.
- Copy it to the SD card and let it flash.
If it was successful, the board should appear in dmesg
with:
[171231.030762] cdc_acm 6-1:1.0: ttyACM1: USB ACM device
[171251.791634] usb 6-1: USB disconnect, device number 3
[171253.119422] usb 6-1: new full-speed USB device number 4 using ohci-platform
[171253.354492] usb 6-1: New USB device found, idVendor=1d50, idProduct=6177, bcdDevice= 1.00
[171253.354542] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[171253.354562] usb 6-1: Product: stm32h723xx
[171253.354578] usb 6-1: Manufacturer: katapult
[171253.354593] usb 6-1: SerialNumber: 1B0029000151313433343333
[171253.358901] cdc_acm 6-1:1.0: ttyACM1: USB ACM device
Then build and flash Klipper with:
make flash FLASH_DEVICE=/dev/ttyACM1
Modify /dev/ttyACM1
according to the dmesg
output.