hei how is it going… ive being trying to install klipper on S1 pro, but every time i run in to the same issue: “mcu ‘mcu’: Unable to connect”
i use this config on my board:
*STM32: Chip on the Mainboard
*STM32F401: with “64KiB bootloader” (i check my board is 401)
*Communication interface: USART1 PA10/PA9
i read somewhere that when you put the klipper.bin in to the printer (yes i put it in to a STM32F4 folder) you should see some change in the file, but nope i dont see any.
from my klipper.log im getting:
===== Config file =====
[mcu]
serial = /dev/serial/by-id/
Where did you read the information about the firmware file?
Often it has to have a particular name so that the printer recognizes it upon restart and flashes it.
This can then result in a changed filename.
With the properly flashed firmware you will get the correct ID you have to put into your config.
This is all described in detail on the Klipper documentation website.
This is also your first location when looking for help during configuration of your printer.
Maybe there is already a config available on github for your printer that only needs slight modifications.
Most obvious one is the not set printer kinematic.
@LifeOfBrian the one from GitHub, also i google a bit here and there flashing my specific machine… so a bit from here, a bit from there…
but two things ****today at work i was googling a bit on mcu problems and i came across this post from someone who had a really similar problem to my and he was talking about changing the Baud rate from 25000 (which it was the default from creality to like 11000, but im trying to find the post),
***the other is that now when i came home read the GitHub file line by line and i notices that its says: "“The filename # must be changed to “firmware.bin””, which its doesn’t happen in my case the klipper.bin never change, so i thing my printer isnt flashing and thats why im getting the mcu error, if that the case i have not idea what im doing wrong as im doing everything as its describe in the printer.cfg file…
With the properly flashed firmware you have to enumerate the serial of the MCU when connected to your SBC and this serial is then entered in the printer.cfg.
All described on the Klipper documentation page.
ok we move one step forwarded the printer is properly flash now
but is still missing the MCU, when i try to ls from the PI im getting:
"pi@pi:~ $ ls/dev/serial/by-id/*
-bash: ls/dev/serial/by-id/*: No such file or directory
"
Windows 11 on the RasPi?
The sudo dmesg should be from a Linux derivative I think.
Is the MCU properly connected to the RasPi and has power?
Did you at least power cycle everything once after the firmware flash?
im not running Windows 11 on the RasPi, the pi is running what ever distribution its gets install (Dev i thinks), following KIAUH…
windows 11 my current computer from where i access throw SSH/Terminal
@LifeOfBrian@Sineos ty for the help…
yeah i did try it, and in fact i think i was affected…
i had denomination ( denoting the version 247.3-7+deb11u2 ) and i follow all step for solution… i notice that after restarting then it was:
pi@pi:~ $ apt-cache policy udev
udev:
Installed: 252.5-2~bpo11+1
Candidate: 252.5-2~bpo11+1
Version table:
*** 252.5-2~bpo11+1 100
100 Index of /debian bullseye-backports/main armhf Packages
100 /var/lib/dpkg/status
but still getting MCU from klipper
something i find a bit strange is that when i run lsusb i get:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and theres 4 usb_port on rasp-4, shouldnt i get back 4 ports from the ls as well??
and back to my main issue, any tips, idk how many times ive re-flash checking every single parameter
umm after some more troubleshooting :A i think i figure why i wasn’t getting any answer from by-id(ive this small usb-c adapter l-shape connected to the printer), after i remove it i start getting id),
but still not MCU
in the klipper log say:
mcu ‘mcu’: Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0
with a bit more google i try:
pi@pi:~ $ service klipper-mcu status
Unit klipper-mcu.service could not be found.
pi@pi:~ $ systemctl status klipper-mcu
Unit klipper-mcu.service could not be found.
i see the confg file for my printer over and over and ives everything as recommended: