I already have a printer running klipper now excellently, so i wanted to upgrade my other printer to it as well.
I have a PI 4B flashed with mainsail and connected how ever the MCU to the board doesn’t work. I thought i fried the motherboard some how so i bought another one and its doing exactly the same.
I’ve got the same firmware i flashed my other printer with on a sd card inserted into the motherboard (both btt skr3 v2) so my logic is that if it worked on the other motherboard it should work on this?? its on the SD card as firmware.bin.
when I run ls /dev/serial/by-id/* to get my MCU i get back /dev/serial/by-id/usb-LeafLabs_Maple-if00 which i have in my printer.cfg.
I have no idea what else to do? any suggestions or help would be great!
Thank you
Klipper reports: ERROR
mcu ‘mcu’: Unable to connect
Once the underlying issue is corrected, use the
“FIRMWARE_RESTART” command to reset the firmware, reload the
config, and restart the host software.
Error configuring printer
Also worth mentioning, the mother board isnt yet installed in the 3d printer, that and the Pi are sitting on my desk connect to each other, does that matter?
This indicates that Klipper is not correctly flashed on the board. See Issues flashing the printer board and in particular make sure you configure for the MCU that is REALLY installed on your board.
Unfortunately the screenshots are of no use and you cannot show the issue with screenshots.
Again: Your connection string /dev/serial/by-id/usb-LeafLabs_Maple-if00 clearly indicates that the board is not flashed with Klipper.
Follow the instructions given in the link above and in particular verify that the MCU on your board is actually what you use for compiling the firmware.
i was trying to show you that when i run the command to find my mcu out that it returns ‘/dev/serial/by-id/usb-LeafLabs_Maple-if00’
you can also see that klipper is install on the pi and i have used winscp to extract the klipper.bin file install on the pi.
i have used 3 different sd cards all reformatted to fat32 along with 3 different cables, i have two of the same motherboards (btt skr e3 v2) both returning the same mcu ID.
i have double checed the chip is correct and the bootloader is also
This is why we ask people to be precise with the information that they provide - You did not specify “SKR Mini E3 V2” in the original post. Grumble.
Regardless, two comments:
Could you do a ls ~/klipper/out -l and see if it matches:
orangepi@orangepicm4:~/klipper$ ls out -l
total 1420
-rw-r--r-- 1 orangepi orangepi 11484 Dec 3 17:15 autoconf.h
lrwxrwxrwx 1 orangepi orangepi 32 Dec 3 17:15 board -> /home/orangepi/klipper/src/stm32
drwxr-xr-x 2 orangepi orangepi 4096 Dec 3 17:15 board-generic
-rw-r--r-- 1 orangepi orangepi 27 Dec 3 17:15 board-link
-rw-r--r-- 1 orangepi orangepi 66579 Dec 3 17:16 compile_time_request.c
-rw-r--r-- 1 orangepi orangepi 353 Dec 3 17:16 compile_time_request.d
-rw-r--r-- 1 orangepi orangepi 217612 Dec 3 17:16 compile_time_request.o
-rw-r--r-- 1 orangepi orangepi 16013 Dec 3 17:16 compile_time_request.txt
-rwxr-xr-x 1 orangepi orangepi 29644 Dec 3 17:16 klipper.bin
-rw-r--r-- 1 orangepi orangepi 8426 Dec 3 17:16 klipper.dict
-rwxr-xr-x 1 orangepi orangepi 1096416 Dec 3 17:16 klipper.elf
drwxr-xr-x 4 orangepi orangepi 4096 Dec 3 17:15 lib
drwxr-xr-x 4 orangepi orangepi 4096 Dec 3 17:16 src
This is what I got when I built with your parameters and maybe the Folder view that you are using is rounding the size but even with that there seems to be a discrepancy there.
If you’re comfortable that the build is correct, could you try building with pin PA13 (SWDIO) set? This will turn on the STATUS LED on the board:
If PA13 is set and the BTT SKR Mini E3 V2 is programmed correctly, then you’ll have both LEDs lit.
If they’re both set then you can follow the instructions @Sineos and @EddyMI3D are giving you, knowing that you are updating the firmware on your main controller board.
