#How to prevent RatOS from flashing boards

46 messages · Page 1 of 1 (latest)

eternal snow
#

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.

warped plinth
#

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?

eternal snow
#

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?

warped plinth
#

calling in the big guns: summon @still topaz

eternal snow
#

hehe

warped plinth
#

cause yeah, that doesn't make sense

eternal snow
#

can't believe I'm the first encountering this problem 🤔

still topaz
#

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?

eternal snow
#

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

still topaz
still topaz
#

You should just do this via the configurator though

eternal snow
#

but 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

still topaz
#

Please ssh in and check the result of lsusb

still topaz
#

(by flashing again)

still topaz
eternal snow
#

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

still topaz
#

The firmware flashing process isn't perfect, sometimes (rarely) it fails.

still topaz
#

That's what it's made for

eternal snow
#

ohh.. ok, so you mean that maybe there was a hickup during flashing and that's what made it lose the connection

still topaz
eternal snow
#

which configurator? 🫣

still topaz
eternal snow
#

yes

still topaz
#

the configurator at /configure

#

so ratos.local/configure

#

You know, the one you used when you installed RatOS in the first place.

eternal snow
#

erm... eehhh.... I flashed the firmware to the sd card on my notebook, inserted it in the pi and hit the power button

still topaz
eternal snow
#

i do.... but i just changed the txt file on the card, like back in ratOS 1, lol

#

sry

still topaz
#

(it's also in the docs btw)

#

would've explained the situation 🙂

#

and fixed it too

eternal snow
#

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 🙂