Teachable Moments: Flashing Klipper Updates to your MCUs
Vložit
- čas přidán 28. 09. 2023
- Links:
docs.vorondesign.com/communit...
Commands to copy/paste into your terminal window:
sudo nano ~/update_klipper.sh
Once inside the nano text editor, paste the following:
sudo service klipper stop
cd ~/klipper
git pull
make clean KCONFIG_CONFIG=config.octopus
make menuconfig KCONFIG_CONFIG=config.octopus
make KCONFIG_CONFIG=config.octopus flash FLASH_DEVICE=/dev/serial/by-id/YourMCUIDHere
read -p "Octopus firmware flashed, please check above for any errors. Press [Enter] to continue, or [Ctrl+C] to abort"
#make clean KCONFIG_CONFIG=config.ebb36
#make menuconfig KCONFIG_CONFIG=config.ebb36
#make KCONFIG_CONFIG=config.ebb36
#python3 ~/katapult/scripts/flash_can.py -i can0 -u YourCANBUSUUIDHere -r
#python3 ~/katapult/scripts/flash_can.py -i can0 -u YourCANBUSUUIDHere -f ~/klipper/out/klipper.bin
sudo service klipper start
Quit and Save, then from the command prompt, issue this command to make the update_klipper.sh file executable:
sudo chmod 777 ~/update_klipper.sh
Once ready, run the shell script with the following command as needed:
~/update_klipper.sh
Had no idea what the voron docs were saying till i saw it in video, so thanks to you all 4 of my boards update in 30 seconds instead of 30 minutes. Good stuff
Great to hear!
Thanks you so much this worked perfectly. Will save me a ton of time the next time I have to update MCUs some time in the distant future.
Thank you very much for providing this tutorial. Massive help for something I didn't realize was possible till coming across this video.
You're welcome!
Works like a charm! Thank you very much!
You're welcome!
Thank you! This really helped me out.
De nada!
Thanks so much, very helpful!!!
You're welcome!
Steph, you are awesome man! Ive been using Linux for over two decades and i still learn something new everytime i see another user do their thing. Definitely gonna use this when im flashing my scara robot build. Not sure if ill be able to get klipper to to play with the kinematics well but at least the flashing should go easier. 😂
I am not a Linux developer, but 3 decades in software tech support probably ranks me as an above average power user. Many of the tools in my bag of tricks are probably "old school", and if it still works well enough, I usually don't bother learning the "newer, better" way of doing things.
"New ways" are only ever worth it to me if you end up learning something new in the process. If they are just a slightly different/even slightly improved way of doing the same thing and you don't learn anything new... if it ain't broke...
Thank you for this!
Welcome!
Good guide, I am just running into the issue of making my Canbus devices(mcu&Toolhead) discoverable
You shouldn't need them to be discoverable to flash Klipper to them.
Thanks for sharing! chmod 777 should be avoided as much as possible, `chmod +x` should be sufficient.
In a true multi-user *nix environment, I would 1000% agree, but for the purposes of a single user environment, I personally don't feel like it really matters.
No one else but me is ever logging into the Pi, and I am only ever logging into it with the pi user account. I might as well just make pi a root-level user, and not even bother with sudo, but some apps might not like that.
HI. Great video, thanks Although it seems like the "preconfigured" config.octopus file does a lot of the heavy-lifting....but unless I missed it, there wasn't any detail about that?
That file is generated when you make changes and save the configuration in make menuconfig. Basically you have to configure it manually the first time, then you're just reusing that saved configuration file whenever you update and reflash Klipper.
So I was able to create a file that updates my main mcu I'm having trouble with my klipper expander. Serial by id wouldn't work on it for some reason. Do I have to reset it, install a boot jumper, etc every time I want to update klipper on it?
I have no personal experience with it, but according to this, the Klipper Expander board requires adding a jumper to put it into DFU mode:
github.com/VoronDesign/Voron-Hardware/blob/master/Klipper_Expander/Documentation/README.md#boot-jumper
I refuse to purchase any board that can't be updated remotely.
@@oldguymeltsplastic Not ideal but at least I know what the issue is now. Also, thanks for uploading this video, it helped a lot.
I got the following error at the end of updating my SKR MINI E3 VE "make: *** [src/stm32/Makefile:111: flash] Error 255". So i aborted the proceed but when i went inside mainsail the MCU was updated !! Thank you
Sounds suspicious to me, but if you're happy, I'm happy!
Mine is doing the same thing but is not updating. The CAN board is updating so that at least removes one item which is nice. Did you ever have to dig into this more? Would be nice to do the main board too.
Do i lose any of my files on my board? im using an arduino for my printer. and if lost i cant reflash the old firmware.
I have no experience with Arduinos.
@@oldguymeltsplastic ah, okay thanks atleast for the reply
Hi, my configuration is as follows: Voron 2.4 300, BTT Octopus + BTT PI + EBB SB2240 (with U2C boar)... I followed ur instructions and now my mcu and ebb are not recognised by the host?? Any idea what to do? Shall I access manually the Octopus and flash the board via USB/DFU mode as I did during initiall setup?? Thanks.
Was the Octopus working with Klipper before you installed CAN Bus? If so, did you flash anything to the Octopus? Because if you are using a U2C, then you shouldn't have flashed anything at all to the Octopus.
With a U2C, all of the CAN Bus functionality is between the Pi, the U2C, and the EBB, the Octopus continues communicating with the Pi over USB.
If you did change anything on the Octopus, then you need to reflash it with Klipper configured for USB communication.
It's a fairly common mistake, so you're in good company.
@@oldguymeltsplasticHi, thanks for taking the time to reply. Yes, before, everything was working fine (set-up) months ago following Your videos. I decided to update all the pending updates within the Mainsaill update manager... and go the error that the MCU and EBB are running an older version and that I shall update those as well. So I found this video of Yours and all made perfect sense, but honestly I dunno much about software...
@@oldguymeltsplasticSorry, dunno if it matters but I installed octopus and u2c and ebb all at once months ago... my voron had can from the very beginning.
what password do i put pls someone help
It depends on your board. I have mks-pi
User: mks Pass: makerbase