mcu 'mcu': Unable to connect | Mainsail | Page 1

thick crescent Jan 24, 2023, 8:08 PM

#

HI.
I need help. I get klipper error:mcu 'mcu': Unable to connect

Here is my klipper log.

📎 klippy_3.log

formal cape Jan 25, 2023, 5:23 AM

#

Have you flashed and verified your mcu board

thick crescent Jan 25, 2023, 8:12 AM

#

I have flash the MCU. How can i verify the mcu?
The board is creality V4.2.7. I have tried following the doc. provided by klipper for flashing the MCU. Under make menuconfig. I use the setting provided in printer.cfg. and also tried to use:
[*] Enable Extra low-level configuration option
Micro-controller Architecture (STMmicroelectronics STM32)
Processor Model (STM32F103)
Bootloader offset (28 KiB Bootloader)
Clock Refrense (8MHz Crystal)
Serial (on USART1 PA10/PA9)
(115200) Baud rate for serial port

formal cape Jan 25, 2023, 8:13 AM

#

puh not sure for the creative boards but normally the name changed e.g to .cur instead of .bin

#

# turning on the printer with the card inserted. The firmware
# filename must end in ".bin" and must not match the last filename
# that was flashed.```

#

I would insure that with a "wild name"

#

the settings look ok.

#

But to insure it is build correct ssh in the PI:

make clean
make menuconfig
make build```

#

at make menuconfig only check that the setup is still correct

#

than copy the klipper.bin file to the sd and maybe change the name in "sun.bin" (only to insure it is a new name)

#

report back if that helps

thick crescent Jan 25, 2023, 10:52 AM

#

My board dont change the file from bin to cur when I flash it. But when I flash it back to marling. It add another file called eeprom.

I will report back when I have tried it out.

thick crescent Jan 25, 2023, 9:34 PM

#

@formal cape nope it didnt work.

thick crescent Jan 25, 2023, 10:56 PM

#

I also tried to flash it via Serial.

#

make: *** [src/stm32/Makefile:98: flash] Error 255. this is what I got back.

formal cape Jan 26, 2023, 6:27 AM

#

hmmm not a real expert for that creative stuff. Lets see if the board is seen at all. ssh in the PI
unplug the usb cable of the board
lsusb
plug the cable
lsusb
in the second case you should see one more device in that list

thick crescent Jan 26, 2023, 8:56 AM

#

I have unplugg the printer en enter command: ls /dev/serial/by-id/. And i see that i didnt register ports. Then i plugg the cable back to printer and enter ls /dev/serial/by-id/ then the port is there. So I think that the V4.2.7 mcu board wont connect to PI. I think i may try it out with my old V1.1.4 board to see if thats the issue.

#

Sry for the texts off wall. Typing on mobile phone at work. XD

thick crescent Jan 29, 2023, 8:31 PM

#

okay. I tried with my old V4.2.2 board. its stil didnt show up in mainsail

#

when i did the command that us ask. this was shown:

#

pi@mainsail:~/klipper $ lsusb
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
pi@mainsail:~/klipper $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 1a86:7523 QinHeng Electronics CH340 serial converter
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

#

so it did show one more device

thick crescent Jan 29, 2023, 10:17 PM

#

SOLVED!!!

#mcu 'mcu': Unable to connect