Jasper
February 9, 2025, 5:08pm
1
klippy (1).log (278.4 KB)printer (1).cfg (16.2 KB)
I am trying to connect my MCU to klipper but something isn’t working.
this is how i found the id:
I don’t know what is wrong so i don’t know what more info to give.
I still needed to build some stuff, it said installed on some stuff so i thought i already had it installed, but i am working on it atm!!
The communication between the Manta M8P V2.0 and the CM4 should be via USB - NOT Serial.
You should have a connection that looks something like:
/dev/serial/by-id/usb-Klipper_stm32g0b1xx_1A003C001050505933383420-if00
What were the parameters that you used to build the Klipper Firmware?
If you had followed the process set out in the User Manual, you’d see that it should be:
Jasper
February 9, 2025, 5:22pm
3
is this the correct thing/way to flash?
^This didn’t work.
the only connection type that shows something is UART:
but when i continue, there is no supported board or it shows this when flashing:
I have no idea of the process that you’re going through.
Let’s go through the process that should work for you:
SSH into your CM4
Press and hold the “B00T0” button, press and release “RESET” and then release “BOOT0”. This will put your board into “DFU Mode”.
Check to see if you are in DFU Mode by running lsusb - Stop if you don’t see something like:
Restart KIAUH.
Select 4) [Advanced] and then 1) [Build]
Put in the specified values from the User Manual:
Quit and let the code build.When done, select 2) [Flash] and 1) Regular flashing method followed by 1) make flash (default)
Now, you want to 3) USB (DFU mode) at which point you’ll see:
11. Select
0) 0483:df11 and start the flash process
12. When the flash process is compete, select
4) pGEt MCU ID] for
1) USB and you’ll get something like:
13. Copy the
/dev/serial/by-id/…
string into yourprinter.cfg`
Now, when you restart Klipper, you should be connected.
Jasper
February 9, 2025, 8:10pm
5
it worked, i got the /dev/serial/by-id/......
my old board (the one i short circuited, but seemed to be fine after switching to CM4) did not go into DFU mode, switched it to the new board and it worked inmedialty.
the old board onlty showed this when i checked with lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Jasper
February 9, 2025, 8:17pm
6
Not quite there yet…
printer (1).cfg (15.9 KB)
klippy (1).log (393.3 KB)
And then eventually it says that it can’t connect to MCU
You’re going to have to go carefully through your printer.cfg. It looks like you’re patching together new information with old.
I just took a quick look at it and, on line 2, you have:
[mcu]
serial: /dev/serial/by-id/usb-Klipper_stm32h723xx_0B001C000A51323235363233-if00
and, on line 264:
[mcu]
serial: /dev/serial/by-id/usb-Klipper_stm32h723xx_12002F001751313434373135-if00
Klipper takes the last value in a file.
Jasper
February 10, 2025, 4:50pm
8
and, on line 264:
strange, i just inported my old printer.cfg
1 Like
