Error after Klipper firmware update on SKR1.4 - mcu : Unable to open serial port... | VORONDesign | Page 1

digital zodiac Apr 8, 2024, 8:33 PM

#

Folks, I shared this Q in the ⁠klipper channel but got no traction. Can someone here please help -

I have a 2.4 thats is a few years old, This happened when I was updating it to the latest klipper. I see this error in klippy.log
mcu : Unable to open serial port: [Errno 2] could not open port ...
This happened when I updated the klipper firmware on my SKR1.4 to v0.12.0. The bahavior is that the MCU is unable to connect to klipper. I can confirm from command line by running ls /dev/serial/by-id/* I see no results & get this error
ls: cannot access '/dev/serial/by-id/': No such file or directory*

When I revert back the firmware version to v0.10.0 [using the old CUR file] the error goes away & Klipper is happily able to connect to the SKR1.4 running a the old firmware.

My Q to the good folks here is - How do I update the SKR 1.4 to the latest version without breaking it? Here is what my menuconfig looks like which I used to build the latest firmware.

hasty ginkgo Apr 8, 2024, 10:02 PM

#

digital zodiac Folks, I shared this Q in the ⁠klipper channel but got no traction. Can someone ...

That "no bootloader" setting is almost certainly wrong

#

Unless you have an actual hardware programmer for lpc chipps

digital zodiac Apr 8, 2024, 10:06 PM

#

should that be the other option?

#

i'll try with that...

#

Seems like it is the same setting as this one from the voron guide

#

Target board uses Smoothieware bootloader

#

seems similar to

#

16Kib bookloader (Smoothieware bootloader)

#

i'll try and reply back here.

hasty ginkgo Apr 8, 2024, 10:11 PM

#

Yep

#

The exact text has changed a couple of times for some reason

digital zodiac Apr 8, 2024, 11:03 PM

#

okay I made progress. I flashed with these settings

#

This change fixed it..

#

Voron_Heart 🎉

#

thanks @hasty ginkgo

flat dune Aug 10, 2024, 1:52 AM

#

So I opened the klippy log and saw this in it how can I fix this problem

hasty ginkgo Aug 10, 2024, 1:53 AM

#

flat dune So I opened the klippy log and saw this in it how can I fix this problem

please open your own post, dont just lump onto some old one that looks vaguly similar. But it looks like you haven't actually edited your own device ID into your config yet. Have you flashed the board yet?

flat dune Aug 10, 2024, 1:54 AM

#

Sorry I meant to do that but got confused but Im pretty sure I have flashed the board but could you explain that to me so I can know for sure

hasty ginkgo Aug 10, 2024, 1:56 AM

#

flat dune Sorry I meant to do that but got confused but Im pretty sure I have flashed the ...

Well, I don't know enough about your system to give a very detailed answer, but broadly speaking, you build some firmware with something like

cd ~/klipper
make menuconfig
make clean
make

and then you either copy it to an sdcard, or use dfu flashing, or some means to get that firmware onto the mcu

then you use ls /dev/serial/by-id/* to get the actual ID of the board, and that goes into your config, in the [serial] section

flat dune Aug 10, 2024, 1:57 AM

#

Yeah I have done that

hasty ginkgo Aug 10, 2024, 1:58 AM

#

well you pretty clearly havent done the last bit of it

#

given that you posted a screenshot of klipper trying to connect to "<your-mcu-id>"

#

which is the spot where you're supposed to drop in the actual id

#

unless of course that's old log data

#

did you scroll to the BOTTOM (aka, the newest part) of the log?

flat dune Aug 10, 2024, 2:02 AM

#

Oh sorry I took it out to try something I forgot I did that but I've put it back in and scrolled to the bottom of the log

hasty ginkgo Aug 10, 2024, 2:02 AM

#

okay, and what error are you getting down there?

flat dune Aug 10, 2024, 2:05 AM

#

I don't see an error

#

But I do also have another issue if you could help me with that too please

#

It's in mainsail

hasty ginkgo Aug 10, 2024, 2:07 AM

#

what's that?

flat dune Aug 10, 2024, 2:08 AM

#

hasty ginkgo Aug 10, 2024, 2:09 AM

#

flat dune

then there should be an error in the klipper log to match

#

did you hit the restart button after you edited the mcu id back in?

#

what did you have for an mcu id?

flat dune Aug 10, 2024, 2:10 AM

#

the id was usb-Klipper_stm32g0b1xx_26002E001350415833323520-if00

hasty ginkgo Aug 10, 2024, 2:11 AM

#

okay, and what exactly does the [mcu] section look like now?

flat dune Aug 10, 2024, 2:11 AM

#

in the log?

hasty ginkgo Aug 10, 2024, 2:11 AM

#

or directly from printer.cfg

#

but yes, from the log would be ideal

#

just make sure it's the most recent version (lowest in the file)

flat dune Aug 10, 2024, 2:14 AM

#

that is the very bottom

hasty ginkgo Aug 10, 2024, 2:14 AM

#

no

#

the [mcu]

#

section

#

like, the section you edited and put the id into

flat dune Aug 10, 2024, 2:15 AM

#

oh sorry

#

hasty ginkgo Aug 10, 2024, 2:16 AM

#

where the heck did "by-path" come from?

flat dune Aug 10, 2024, 2:16 AM

#

im not sure

hasty ginkgo Aug 10, 2024, 2:16 AM

#

also, why do you have the same id in there for 2 different boards?

flat dune Aug 10, 2024, 2:17 AM

#

was the id in supposed to be in the top one or the bottom one

hasty ginkgo Aug 10, 2024, 2:18 AM

#

I don't really know. What board did you retrieve that id FROM?

#

if it's from your main controller, then it's the top one, [mcu]

#

if it's some toolhead board known as pth (what board even is that?) then it should go there, in [mcu pth]

flat dune Aug 10, 2024, 2:19 AM

#

the config came from the LDO docs site. the toolboard is the nitehawk from them

hasty ginkgo Aug 10, 2024, 2:20 AM

#

wonder how they got from "nitehawk" to "pth"

#

oh well, point is, the nitehawk id goes in the second one there

flat dune Aug 10, 2024, 2:20 AM

#

ok

hasty ginkgo Aug 10, 2024, 2:21 AM

#

but in both cases, it should be "by-id" not "by-path", just the same as in the ls /dev/serial/by-id/* command

flat dune Aug 10, 2024, 2:22 AM

#

like this?

hasty ginkgo Aug 10, 2024, 2:23 AM

#

flat dune like this?

[mcu] looks good. [mcu pth] still seems sus

#

have you flashed the nitehawk and gotten an ID for it yet?

flat dune Aug 10, 2024, 2:24 AM

#

no

hasty ginkgo Aug 10, 2024, 2:24 AM

#

so it's fine for now. but of course, klipper isn't going to start properly until you have BOTH boards configured, since printer.cfg is calling for both of them

flat dune Aug 10, 2024, 2:24 AM

#

ok

hasty ginkgo Aug 10, 2024, 2:26 AM

#

still, if you try to restart klipper now, I imagine you'll see a shift from it complaining about mcu: mcu to complaining about mcu:pth

#

once you see that, you can kinda read between the lines, and trust that it's successfully communicating with the first mcu

flat dune Aug 10, 2024, 2:27 AM

#

im doing that now

#

yeah it says mcu pth

hasty ginkgo Aug 10, 2024, 2:40 AM

#

flat dune yeah it says mcu pth

Great. That's about all you can hope for, until you get that nitehawk sorted out

#Error after Klipper firmware update on SKR1.4 - mcu : Unable to open serial port...