Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
SergeDubovsky opened this issue Jun 13, 2024 · 0 comments
Open

Comments

@SergeDubovsky
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant