search

dw-0 / kiauh

Klipper Installation And Update Helper
GNU General Public License v3.0
3.37k stars 488 forks source link

mcu 'mcu': Command format mismatch: config is_config=%c crc=%u is_shutdown=%c move_count=%hu vs config is_config=%c crc=%u move_count=%hu is_shutdown=%c #190

Closed E-Olsen closed 2 years ago

E-Olsen commented 2 years ago

Linux Distribution

PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)" NAME="Raspbian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=raspbian ID_LIKE=debian

What happened

I used KIAUH to update my SKR Mini E2 v2 to the same Klipper release as my Host but now I get the following results when connecting via Fluidd:

This type of error is frequently caused by running an older version of the firmware on the micro-controller (fix by recompiling and flashing the firmware).

Known versions: host=v0.10.0-376-gfb3bae45, mcu=v0.10.0-42-g64e46498

Once the underlying issue is corrected, use the "RESTART" command to reload the config and restart the host software. Protocol error connecting to printer

I set the menuconfig to be correct for the SKR Mini E3 v2 and generated the klipper.bin file in the /out directory. I used WinSCP to copy that file to an sd card and renamed it to firmware.bin as required.

Turned off power to the board and turned it back on. It did not change the version to v.0.10.0-376 as expected.

What did you expect to happen

I expected the version of the MCU to match the Host, which should be v0.10.0-376-gfb3bae45, the most recent as of 4/21/2022 on the Master branch. Instead, the board did not flash at all and did not rename the firmware.bin file.

How to reproduce

I am not sure HOW I got v0.10.0-40 onto the MCU as v0.10.0-376 is the current version.

Additional information

Is there a way I can upgrade my Host to v0.10.0-40?

dw-0 commented 2 years ago

I expected the version of the MCU to match the Host, which should be v0.10.0-376-gfb3bae45, the most recent as of 4/21/2022 on the Master branch. Instead, the board did not flash at all and did not rename the firmware.bin file.

Your expectation here is correct. But you say that the board did not flash at all and did not even rename the firmware.bin file. That is usually an indicator for a firmware that has been build wrong. Some settings during the make of the firmware must have been made wrong. And thats the reason your firmware on the mcu still shows as the last, valid flash that was made.

Though, this is likely not a KIAUH issue or bug, so i suggest you rather join the Klipper community on the official Klipper Discord if you need further assistance: https://discord.klipper3d.org/