Error after Klipper firmware 0.13 update

General Discussion
1

Basic Information:

Printer Model: monoprice mine select V3
MCU / Printerboard: stm32f070xb / M200_V3-MAINBOARD
Host / SBC: RasberryPi
klippy.log

Here the relevant part from klippy log

loaded MCU ‘mcu’ 132 commands (v0.13.0-189-ge1ba7c17c / gcc: (15:12.2.rel1-1) 12.2.1 20221205 binutils: (2.40-2+18+b1) 2.40)
MCU ‘mcu’ config: ADC_MAX=4095 BUS_PINS_i2c1=PB6,PB7 BUS_PINS_i2c1_PB6_PB7=PB6,PB7 BUS_PINS_i2c1_PB8_PB7=PB8,PB7 BUS_PINS_i2c1_PB8_PB9=PB8,PB9 BUS_PINS_i2c1_PF1_PF0=PF1,PF0 BUS_PINS_i2c1a=PF1,PF0 BUS_PINS_spi1=PA6,PA7,PA5 BUS_PINS_spi1a=PB4,PB5,PB3 BUS_PINS_spi2=PB14,PB15,PB13 BUS_PINS_spi2a=PC2,PC3,PB10 CLOCK_FREQ=48000000 INITIAL_PINS=PA8,PB11,PB1,!PB3,!PB8 MCU=stm32f070xb PWM_MAX=257 RESERVE_PINS_USB=PA11,PA12 RESERVE_PINS_crystal=PF0,PF1 STATS_SUMSQ_BASE=256 STEPPER_OPTIMIZED_EDGE=6 STEPPER_STEP_BOTH_EDGE=1
mcu_temperature ‘mcu’ nominal base=358.903654 slope=-767.441860
Sending MCU ‘mcu’ printer configuration…
webhooks client 130074575577872: New connection
b’Got EOF when reading from device’

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

My printer a monoprice mine select V3 has klipper firmware 0.11
It is working fine also with klipper host 0.13.

Today i compiled 0.13 and flash it. Now it stops working.
I used the same config as for compiling as 0.11
And the printer.cfg ist also the same.…

It look like the serial comunicatin is working in general. so no USB Issue.

After i flashed back klipper firmware 0.11 it works again.

The main difference if have seen is the size of the firmware
firmware v0.11 28kB
firmware v0.13 42kB (but i think this is because off more feature)

Has enybody an idea what’s wrong ?

2

The only relevant part is the log itself.

3

deleted - Sineos

4

{26EDA76B-2BD8-45A8-A632-C9AF8099162B}
{26EDA76B-2BD8-45A8-A632-C9AF8099162B}1074×170 14.4 KB

Seems not too difficult, right?

5

klippy.log (167.0 KB)

6

I have already checked the Knowlege Base.
I have no cable or usb port problems.
I also checked on a different Host.
With firmware v0.13 my Raspberry became unresponsive.
With firmware v0.11 all working fine.

7

Hard to tell, since the log contains various issues:

In any case, do not “recycle” old .config files when updating across major versions.

8

Hi,

thanks for looking into the logfile.

The “No such device or address“ error came from a bad configured VM from my side. I messed up the usb passthrue.
After i fixed this, these message is gone. I made the same mistake with my webcam.
The second point i can rule out because with the v0.11 firmware it’s workin fine.
I have also made i total new .config by deleting the old and create a new one with menuconfig.
I tried different hosts (a Raspberry and a debian VM on a nuc under Proxmox)
Also i change the usb cable. No difference.
i think the v0.13 firmware is bad. There must something different against v0.11
In the past i had also the same problems with v0.12 firmware.
Thats why i am staying at v0.11. This pice is working with my printer.
thanks

9

Considered it could be this?

10

It is possible that on some obscure/old/cheap/not popular MCUs, there could be issues.
If you say that it has been broken for more than 2 years.
It’s unfortunate.

commit 0d67d9c45d2dc39f8b4be7d1bb54b94b2698a2b6 (tag: v0.12.0)
Author: Kevin O'Connor <kevin@koconnor.net>
Date:   Thu Oct 12 20:54:45 2023 -0400

    docs: Note the release of v0.12.0

But it also means that this whole time, no one reported it.
It is hard to guess or debug without this particular MCU in hand.

If you will, you can go down the rabbit hole: Klipper Versioning, Downgrading, and Bisecting
To, well, isolate the change that broke your particular MCU.

2 Likes
11

Thanks for advise.

i will give it a try. But at the moment i have no time. My free time is limited.
I don’t use my Print very often. So will freeze my Enviroment at the current state.
As far as i cant tell v0.11 is working v0.13 and v0.12 not.

12

Thank,

i only used the VM for troubleshouting and to rule out the Raspberry. In general i use a Raspberry.
I had no chance troubleshoot on my Raspberry because at the time i use the v0.13 Firmware this piece freezed and become unresposive. No idea why.
I thought it was a wrong device-ID but thats not the case.
It is really the firmware itself at the point …Sending MCU ‘mcu’ printer configuration
the firmware crashed on my printer. My raspberry freezed and no good logs. i don’t know why this happend. With the VM i had the chance to get logfiles an rule out the device-ID guess and also cable an usb-port problems.
Maybe i find a way to stay at klipper v0.11 in mainsail. At the moment my host is 0.13 an my printer is 0.11. I fear in future releases this combination will not work anymore.