RatOS will not connect to my mcu
Have tried different cords, when I flashed the controller it returned a .cur file like it should have, now though I cannot connect to it.
73 Replies
Have you looked at and worked through all the suggestions in https://discord.com/channels/582187371529764864/1046952693480038500 ?
absent-sapphire•2y ago
Are you using RatOS? I had the same problem after updaten my SKR2. Search for the Serial ID and check if that’s correct in the config
national-gold•2y ago
Ive worked through all the suggestions and it seems like the octopus is being recognized by the pi but I think the serial id for the board may be incorrect in config
did you flash it with the correct firmware?
national-gold•2y ago
Yes, I’ve tried the one from the firmware_binaries folder and the generic klipper one for the octopus, the klipper one shows up on ssh but with the one from ratos it doesn’t show up
sensitive-blue•2y ago
@jeffbezosvevo I'm at exactly the same point- worked through everything in the FAQ linked, checked that the .bin changed to .cur, firmware is correct for the SKR2 board, checked all wiring
national-gold•2y ago
It just doesn’t show up or connect and I’m not really sure what else to try
sensitive-blue•2y ago
Me either, mine is a V-Minion but I'm in the same spot.
Did you first run
COMPILE FIRMWARE?national-gold•2y ago
Yes
Is there any way to recompile without starting over with ratos?
Yes, run the macro in the web UI
national-gold•2y ago
I recompiled and reflashed my board, no change.
and what is the output when you run
dmesg -w and then plug in your octopus?sensitive-blue•2y ago
Mine just returns the same 'mcu unable to connect' message, that's before and after plugging in the USB to the SKR2.
that is not running
dmesg -w