Fresh RatOS install x2 and still can't get the MCU to respond
Have installed RatOS x2 today, Have a brand new Octopus V1.1 flashed via sd card, and tried flashing it through RatOS a few times and the Configurator keeps telling me Octopus V1.1 Detected but is unresponsive. Not sure what else to do other than do the whole thing through SSH like usual.
Solution:Jump to solution
Ok.... I finally got it to work.... Reinstalled RatOS on the Pi another 2 times in the last 24 minutes and now its detecting the board.... @miklschmidt Maybe an Idea, Nothing more.
Post a note on the OS install page for users not using an SD card that the install might not work properly and to try reinstalling RatOS a couple times before pulling hair out. Like me 😁...
27 Replies
Have you removed everything attached to the octopus except for power and USB?
Yes. Only things connected are power and usb. The Firmware file changes from .bin to .CUR file format
Can you take a photo of your board and upload it? Maybe you forgot to remove a jumper or something
1 sec
Sorry didn't move stepper wiring out of the way first
Ok, no boot jumper and no power jumper which is good. When you did the flashing, was your pi connected to the Internet? If not it may not have made the klipper firmware correctly
Pi was connected to my home network the entire time
Ok. Have you tried using a different USB cord?
A few different coards and this started with an SKR Pro that bricked and is not recoverable 3 days ago.
I just tried configuring the Firmware manually through ssh and no change there either.
Tried using a usb cord I haven't used yet. Reflashed firmware again and it took the firmware. But no changes on RatOS configurator
Not sure why it is saying it is unresponsive, maybe @miklschmidt has more info. But if it changes to .CUR I think it is safe to continue
But be sure to use the firmware from the configurator and not one you compiled yourself
Most likely yes.
I'm not sure either. This usually only happens if the board doesn't boot into klipper (for example if boot0 is left in place) or klipper wasn't able to pull the dependencies from the web needed to compile the chelper code.
It's worth trying to reset the board (click the reset button next to the USB-C connector) and try the configurator again (it should detect and verify the version).
Solution
Ok.... I finally got it to work.... Reinstalled RatOS on the Pi another 2 times in the last 24 minutes and now its detecting the board.... @miklschmidt Maybe an Idea, Nothing more.
Post a note on the OS install page for users not using an SD card that the install might not work properly and to try reinstalling RatOS a couple times before pulling hair out. Like me 😁
I don't think the installation is the issue here. Balena etcher would fail during verification if the image wasn't 1:1.
Hmmm I see I am being pranked now
I promise all I did was Reinstall RatOS with Balena etcher this entire time.
I believe you
2.1 precompiles all required klipper files so at least that takes care of the chelper issue (which i believe is the source of most of this)
I see this issue often enough with Linux and Windows based installs. Often times I get an issue with not being able to install Video or Lan Drivers and after reinstalling I have those functionalities.
So uh what do I do about not being able to click next?
Oh sorry i missed that, i believe that's an old bug that was fixed some time ago, but 2.0 doesn't compile anymore so the current image is rather old and doesn't have those fixes. As a workaround you can increment the
step in the url manually.
Alternatively go to /config and update ratos-configuratorAlso backing out a few times got it to unlock apparently
yeah there were some state update issues so given the right timing it prolly works 😂
I couldn't imagine being you when this was first rolled out and everyone started using it
weirdly enough these issues have been popping up more recently than they did when that image was released almost a year ago
I'm guessing you have made updates over that year?
Also if you need some Guinee pigs to try out 2.1 let me know. I ain't afraid to try things out for the heck of it.
Now to wire it all up and start this puppy up after the week of disliking RatOS Install/ SKR Pro Bricking/ Lacking braincells and reinstalling RatOS like I should have 5 days ago.