Outdated Beacon firmware

I am getting the following error on a fresh config of my VC4.

MCU Protocol error

This is frequently caused by running an older version of the
firmware on the MCU(s). Fix by recompiling and flashing the
firmware.

Your Klipper version is: v0.12.0-268-g0844388d7-dirty
MCU(s) which should be updated:
mcu: Current version v0.12.0-268-g0844388d7
rpi: Current version ?-20240727_132503-fv-az659-741
toolboard_t0: Current version v0.12.0-268-g0844388d7
beacon: Current version Beacon 1.1.0
Up-to-date MCU(s):
<none>

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

Outdated Beacon firmware version 0.1.0, current version is 2.1.0.
Please run `install.sh` or `update_firmware.py update all` to update to the latest version.
Using an outdated firmware version can result in instability or failures.

mcu 'beacon': Unknown command: beacon_contact_home

MCU Protocol error

This is frequently caused by running an older version of the
firmware on the MCU(s). Fix by recompiling and flashing the
firmware.

Your Klipper version is: v0.12.0-268-g0844388d7-dirty
MCU(s) which should be updated:
mcu: Current version v0.12.0-268-g0844388d7
rpi: Current version ?-20240727_132503-fv-az659-741
toolboard_t0: Current version v0.12.0-268-g0844388d7
beacon: Current version Beacon 1.1.0
Up-to-date MCU(s):
<none>

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

Outdated Beacon firmware version 0.1.0, current version is 2.1.0.
Please run `install.sh` or `update_firmware.py update all` to update to the latest version.
Using an outdated firmware version can result in instability or failures.

mcu 'beacon': Unknown command: beacon_contact_home

I trying running install.sh and update_firmware.py but only got MCU protocol errors. Any advice?

3 Replies

RubbyOP•3mo ago

I saw a similar post saying beacon may not be getting power. There is no light on my beacon so that could be the issue? Found a script from Mikkel that solved it: sudo ~/beacon/update_firmware.py update all

miklschmidt•3mo ago

So the issue is that RatOS can't flash you beacon when it's not connected. So if you updated RatOS / Beacon before connecting the beacon, it won't be flashed. You can flash it through the configurator through the help menu (i know, not ideal place to put it, it's not permanent though).

RubbyOP•3mo ago

Ah that explains it. I think it was unplugged during the initial flash! Thank you!

Gaming

Programming

Outdated Beacon firmware