Ender 3 s1 pro 'mcu errror'

[ItsMocha]

Basic Information:

Printer Model: Ender 3 s1 pro
MCU / Printerboard: STM32F401
Host / SBC Pi 3 B+ using mainsail /klipper
klippy.log

Hi all I’ve been trying to get klipper to work with my ender 3, i’m pretty sure its possible . So far I’ve got the pi board connected to the ender 3 via usb a → usb c.
I made the klipper.bin file using the following settings in the menuconfig

I’ve made a partition on my sd card with fat32, made a folder as ‘STM32F4_UPDATE’ and placed the bin file. Take the sd card and place it into the ender 3 power on, the screen does not load correct which from what i’ve read is normal. After a bit the screen goes black, i assume at this point the flash is done, and power off the ender 3.

reboot/ restart everything log into my pi board via the web to get to the mainsail dashboard, I get the following.

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

I’ve tried what i feel like is everything to get the two to talk to each other , any help will be greatly appreciated.

printer.cfg.txt (2.8 KB)
klippy (1).log (893.4 KB)

[DaVinci10]

serial: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0

Is this what you see with running:
ls -lta /dev/serial/by-id/*
in an ssh session? or if your using KIAUH you can choose 4) Advanced menu, 5) get mcu id

[ItsMocha]

Yes that is what i am getting when running cd /dev/serial/by-id/* via ssh

my printer is currently running a print but i can post a screen shot in a few.

[ItsMocha]

[DaVinci10]

Have you read this one?

Klipper cant connect to mcu

Basic Information: Printer Model: ender 3 s1 pro MCU / Printerboard: STM32F401 klippy.log (49.5 KB) Fill out above information and in all cases attach your klippy.log file. Describe your issue: …Hi Everyone. im relatively new to 3d printing and I am in the process of flashing klipper onto my ender 3 s1 pro I believe the flash went okay but i honestly don’t know how to tell, But when I connect my rpi to my printer mainsail it spits out an mcu error. I am extremely lost all help is much app…

in there I read

Aug 2023

fixed

@cbrew
Your error is:

mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0: [Errno 2] No such file or directory: '/dev/serial/by-id/usb-1a86_USB_Serial-if00-port0'
Check Debian Bullseye Bug causing Klipper to no longer find the printer board 54

It leads to this one…

Debian 11 (Bullseye) udev bug - No board or serial found

Background In recent updates, Debian Bullseye (Debian 11) introduced a bug in udev that causes the command ls /dev/serial/by-id/* to fail, because the bug prevents the creation of this device path. As of writing this, the bug remains unfixed in the regular Debian repositories, but it is already fixed in optional Debian repositories. How to Diagnose To check if the OS is affected by the bug, run: sudo apt -y update && sudo apt -y upgrade apt-cache policy udev If the command’s output display…

hope its that easy, alot of us users fell into the rights bug

on the Klipper discord they had pinned a script that did all the fixes. its pinned in the mainsail forum on klipper discord.

Fix for current by-id issue in debian updates

curl -sSL https://raw.githubusercontent.com/mainsail-crew/MainsailOS/develop/patches/udev-fix.sh | bash

I dont know if any of this is your issue, but like I said earlier. a bunch of us got hit with it.

[ItsMocha]

I have looked into Sineos fixes, I ran the diagnose and my udev was:

This is not the ‘deb11u2’ as outlined in his post.

let me know what else can help diagnose this.
(sorry for the janky screen, i can only post on at a time
Thank you

[DaVinci10]

Was hoping, but I guess I’ll have to defer to others here. was reminded earlier tonight, with a warm welcome; that I should let the pro’s support folks on here. Hope you well.

I saw this one as well… with double checking the processor/comm port btw

Mcu 'mcu': Unable to connect - Ender 3 S1 Pro

Assuming you are using the stock board, the example config says: To use this config check the STM32 Chip on the Mainboard, during “make menuconfig” select accordingly either the STM32F103 with “28KiB bootloader” or the STM32F401 with “64KiB bootloader” and serial (on USART1 PA10/PA9) for both. Have you checked the board to see whether is uses the STM32F103 or STM32F401 mcu? Also in your menuconfig, you have: Communication interface (USB (on PA11/PA12)) The config documentation says tha…

[Sineos]

@DaVinci10 answers point into the right direction.
It is mandatory that you properly identify the MCU on this board and then use the correct settings.
Also the SD card used for flashing can make a big difference.

Generally, see Issues flashing the printer board for the influencing factors and what to check.

[ItsMocha]

pics.zip (4.3 MB)

I’ve added a zip folder of a few pictures, 1: the mcu, 2: the micro sd card I am using) 3: the formatted partition of the micro sd card.

Not sure if this qualifies as a “good quality” sd card. From that link you’re guessing the sd card or cable? Is the a good way to know if the mcu is flashing correctly without a proper screen?

Thank you.

[ItsMocha]

I will say I did use the same card to flash the mcu back to crealitys firmware.

[Sineos]

@ItsMocha

From that link you’re guessing the sd card or cable? Is the a good way to know if the mcu is flashing correctly without a proper screen?

There are a lot more items mentioned in this link. It is quite impossible to say which is the root cause from remote.

I propose to systematically go through them in the order they are listed.

[ItsMocha]

I wouldn’t be opposed to you remoting into my system, I think the biggest hurdle would be time zones.

make menuconfig Settings

I’ve posted the settings and mcu within my printer.

Flashing the board

I’m flashing via a sd card and have posted my procedure.

The SD Card used for flashing

This question was never answered and posted all of what I have performed.

USB Cable / Connection

I would assume that if the pi board is seeing the serial, it is a ‘good quality’ cable.

Linux Issues

I’ve posted the ‘common’ linux issues and do not think my pi has these issues, and even preformed the ‘fixes’

Obtaining the board’s serial

The only thing that I see here is its possible that the serial might change, how common is this?

[Sineos]

• For the F401 MCU your settings seem correct
• I cannot speak for the quality of your USB cable
• The guide above clearly mentions a SD of below 8 GB for flashing and I cannot comment on the quality of yours (not saying that it has to be the root cause)
• The board has CH3xx USB chip, so it will always register as /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 (regardless if Klipper is correctly flashed or not)

From the instructions

# Flash this firmware by copying "out/klipper.bin" to a SD card and
# turning on the printer with the card inserted. The filename
# must be changed to "firmware.bin"

# With STM32F401, you might need to put "firmware.bin" in a
# folder on the SD card called "STM32F4_UPDATE" in order to flash.

• It seems not clear with this board if STM32F4_UPDATE is needed or not
• There are reports that renaming the klipper.bin to firmware.bin might not be working
• A lot of the Creality boards require changing the firmware filename on every flash attempt

I do not own this board, so I cannot comment first hand. There are enough reports that it works, so it is likely something on your end.

Follow the dmesg instructions that are equally outlined in the link and check if there is anything telling.

[ItsMocha]

I appreciate all the help. When I downloaded the firmware from creality it did have the STMF4_UPDATE folder, I forget the name of the file.bin,.but maybe I can just try copying over the klipper.bin and renaming it, I think thats the only thing I haven’t tried. Would you think re-formatting to 8gb would suffice or just getting a 8gb card?

[ItsMocha]

dmesg.txt (35.2 KB)

[ItsMocha]

This issue was fixed via discord with James. you can format a large sd card, i did mine for 8gb, and was able to flash successfully.