Mcu unable to connect, sv07

[David3d]

Basic Information:

Printer Model: sovo sv07 plus
MCU / Printerboard: stm32
Host / SBC OS: Armbian 22.05.0-trunk Buster

klippy (16).log (1.6 MB)

I dont know whats happening, cant put mainsail working, already flashed mcu board several times, already upgraded klipper and happyHare,

…

[3dcoded]

Hi @David3d ,

From the log:

serialhdl.error: mcu 'mcu': Serial connection closed

This typically indicates that Klipper isn’t properly flashed to the mainboard.

Mcu: Serial connection closed / Timeout on connect / Wait for identify_response

mcu: Serial connection closed / Timeout on connect / Wait for identify_response Background The printer-board / MCU did not respond to the connection attempt of the Klipper Host until finally the serial connection timed out and was closed. Often, these 3 errors will go hand in hand in the klippy.log Reasons Hardware issues between the board and the SBC, e.g. USB port, USB cable etc Wrong parameters during make menuconfig when building the firmware for the board Firmware not correctly flashed to…

[David3d]

when i do ls/dev/serial/by-id/* it shows the actual board

[Sineos]

1. I cannot comment on the settings or the needs for this printer, as it typically has an OEM-modified Klipper setup. Regarding “Disable SWD,” make sure that it is indeed a GD MCU; otherwise, it will not boot properly.
2. I’m not fully convinced that using a self-compiled bleeding-edge Linux/kernel version is a good idea unless you can debug and solve issues arising from it. An eth0 error on the MOTD does not increase this confidence.
3. Follow this link.

[David3d]

i didnt replace the name of the .bin file, that was the issue