How to prevent RatOS from flashing boards
I installed RatOS 2.0 a few days ago and took my time to setup everything again. And then, yesterday, some updates again and so i click on "update all".
It took longer than normal and after a reboot, klipper couldn't connect to my octopus 1.1 any more.
Turns out that during the update, the board got flashed too, but obviously with wrong settings (connection to Pi over serial port instead over USB).
How can I prevent this from happening at all?
Or is there a possibility to configure that in the first place?
Couldn't find any info on that in the docs.
Since I plan on adding maybe one or two picos or other arduinos, I don't want to constantly need to flash everything to get it working again. Kind of annoying.
27 Replies
it is supposed to flash the board automatically because the version of klipper changed enough that your board needed new firmware. Did you override the MCU connection or something in your printer.cfg?
then... why is it now working with my 4 days old firmware? what might have changed?
The 3 lines I have in my config are:
[mcu]
baud: 250000
serial: /dev/btt-octopus-11
and I'm using a USB cable for connection.
How does klipper think I want to use the other port instead?
calling in the big guns: summon @miklschmidt
hehe
cause yeah, that doesn't make sense
can't believe I'm the first encountering this problem 🤔
Turns out that during the update, the board got flashed too, but obviously with wrong settings (connection to Pi over serial port instead over USB).How do you know?
got this error in klippy.log
mcu 'mcu': Starting serial connect
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-11: [Errno 2] No such file or directory: '/dev/btt-octopus-11'
so I was assuming that with flashing the board, it got told to use the serial header instead of the USB connection.
where does klipper get the information what settings it should use for flashing a new firmware. If I do it manually with makeconfig, I get a lot of settings to choose
Yeah this is because your board isn't connecting for some reason. It hasn't been automatically flashed for UART (that would be pure magic) 😄
Those come from RatOS, in the board config folder there's a
firmware.config, that gets copied into ~/klipper/.configure
You should just do this via the configurator thoughbut what other setting can there be, that no serial connection was possible? I just took my 4 days old firmware, flashed it to the board and it connected again
Please ssh in and check the result of
lsusb
This is not what happened. There are no magic settings that automatically get set, it's literally the same everytime, it's not the firmware, it's the flashing process. It happens, use the configurator to restore your board.
(by flashing again)
ah fine, same fix different steps 🙂correct, there is a firmware-folder now with the octopus1.1 bin
this showed up after the klipper update. hadn't had that after the fresh install
The firmware flashing process isn't perfect, sometimes (rarely) it fails.
Yeah this is a leftover from olden times 😄 Always use the configurator when you have board trouble
That's what it's made for
ohh.. ok, so you mean that maybe there was a hickup during flashing and that's what made it lose the connection
Yes, or rather, the firmware that was flashed got corrupted or the process didn't finish correctly or something like that, leaving the board with broken firmware.
which configurator? 🫣
You're on RatOS 2.0 no?
yes
the configurator at /configure
so ratos.local/configure
You know, the one you used when you installed RatOS in the first place.
erm... eehhh.... I flashed the firmware to the sd card on my notebook, inserted it in the pi and hit the power button
So you didn't even look at the installation guide? You're not using wifi?
i do.... but i just changed the txt file on the card, like back in ratOS 1, lol
sry
ah ok, that's fine. Go to ratos.local/configure?step=1 and check it out, it'll help you next time something is wrong with the board 🙂
(it's also in the docs btw)
would've explained the situation 🙂
and fixed it too
I was there, but I didn't recognize it as "my" error
thanks for the clarification!
RTFM again
Thanks for your help mikl 🙂
just had another update of klipper from 188 to 189 where the board got flashed again... it worked now 🙂
excellent 👍