Skip to content

Extend the Katapult support for the full automation of MCU updates #480

@SergeDubovsky

Description

@SergeDubovsky

Is your feature request related to a problem? Please describe

CAN deployment complexity

Describe the solution you'd like

Hi,

This is an extension of #439. The Feature request is for the support of flashing MCUs via Katapult, I suggest taking it further. We can automate the MCU flashing. I am helping in Voron Discord can-and-usb channel and we have an extensive experience with flashing MCUs to all imaginable boards.
The Esoterical Guide already has configurations for the vast majority of MCUs. We can create .config files for all of them, so in the KIAUH, the user will have the option to specify MCUs make and models, and the script will build the Katapult/Klipper with KCONFIG_CONFIG=config.MCU
Since KIAUH has access to printer.cfg it can invoke the Katapult and flash the MCU via CAN with minimal user input, or even no input, if we can save a .config for each UUID.

If that sounds interesting, please stop by the Discord channel; we can talk about details.

Describe alternatives you've considered

No response

Additional information

No response

Metadata

Metadata

Assignees

Projects

Status

Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions