SKR3 EZ - No MCU serial

Hello @Sineos, thank you for posting this solution. I was wondering if you’d be able to help me solve this as I’m running into a similar issue. I’m trying to install a fresh copy of Klipper using the KIAUH script on a RPi4 + BTT SKR3 EZ board. Everything seems to run fine up until I flash the firmware and connect via usb to try and get the MCU id. Then I’m faced with the usual “No MCU found!” error.

I’ve attempted to run the command sudo dmesg that you suggested and I get back an error stating “MMU error from client L2T (0) at 0x21000, pte invalid”

The command after that for sudo systemctl list-units | grep brltty doesn’t return anything.

Any idea of what this might mean/how to fix it?

Any feedback is much appreciated, thank you in advance!

Please do not necropost. Moved it into a new thread.

Your dmesg output shows nothing interesting so far. The MMU “error” can be disregarded IMO.

Do the following:

  1. Turn on the printer.
  2. Disconnect the USB from the RPi to the board
  3. Re-connect the printer board to your RPi.
  4. Run sudo dmesg > dmesg.txt in the command prompt, and then attach the ‘dmesg.txt’ file here

Hello @Sineos, apologies about that, thanks for replying though!

Here are the results from the procedure you suggested:
dmesg.txt (30.8 KB)

Thanks again for the help, looking forward to your reply!

Best

[   76.468199] usb 1-1.2: USB disconnect, device number 3
[   87.485909] usb 1-1.2: new full-speed USB device number 4 using xhci_hcd
[   87.597921] usb 1-1.2: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
[   87.597939] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   87.597945] usb 1-1.2: Product: stm32h743xx
[   87.597950] usb 1-1.2: Manufacturer: Klipper
[   87.597955] usb 1-1.2: SerialNumber: 490044000B51303138393138
[   87.603842] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device

This is fine.

Post the output of ls /dev/serial/by-id/* and attach a recent klippy.log

Hmmm, it appears that the dev folder is missing from the klipper directory. I posted the output of running ls /dev/serial/by-id/* and listing the items in the klipper & home directories for your reference and the klippy.log file you requested. Hope this helps, thanks again for the help!

klippy.log (32.6 KB)

If you are running Debian Bullseye then check: Debian Bullseye Bug causing Klipper to no longer find the printer board

1 Like

Hello @Sineos, thank you for getting back to me and apologies for the delay in the response.

I’ve checked the procedure in the other thread that you shared and I didn’t want to proceed without checking in with you first. Running apt-cache policy udev returns the following:

I’m assuming this is the same as Debian Bullseye, but I installed PiOS directly from the RP-imager so it’s showing up as raspbian. After running sudo apt edit-sources and selecting nano as the editor, I get back the following menu:

Should I still proceed to add deb http://ftp.debian.org/debian bullseye-backports main non-free contrib at the end, save and close and run the rest of the procedure (sudo apt updatesudo apt install udev -t bullseye-backports)?

Thanks again for all the help!

You can safely proceed.

1 Like

Amazing! After running the procedure highlighted on the other thread, it looks like it is now able to get the MCU serial id.

Thanks so much for all the help! :slight_smile:

1 Like