2.1 RC3 configurator can't flash board(s)
Fresh install of the new RatOS, brand new Sandisk card from Amazon.
Pi4
BTT Octopus Pro H723 v1.1
Ethernet
Can see MCU is connected in
/dev/serial, along with the EBB42.
Configurator can't seem to detect the board for some reason, so won't flash them.
Hoping to resolve it as the primary reason from switching from my old 429 board was to allow automated flashing, and not having to use my dfu-util flashing script anymore.
Debug.zip attached.
Followed the process outlined in the RatOS docs ref. updating via mainsail prior to proceeding with the configurator beyond wifi setup.
RatOS --> RatOS configurator --> updated all others.Solution:
Jump to solution
```
pi@RatOS:~/klipper $ ls -lah
total 116K
drwxr-xr-x 12 pi pi 4.0K Feb 12 20:34 .
drwxr-xr-x 21 pi pi 4.0K Feb 12 19:49 .....
12 Replies
that command line output only shows a beacon and a ebb42 - so looks like your octopus is indeed not connected. Is this the first time you are trying to flash it?
STMicroelectronics_MARLIN_STM32H723ZX_CDC_in_FS_Mode_303F345D3231-if00
Is this not the H723's STM32 MCU?
Yea, it's a completely fresh board, straight out of the box from BTT.then yeah, I would expect it to not detect it and you would have to use dfu to flash it the first time
after that, it should automatically detect it and update it
ahh I missed that, the formatting on my screen jammed it together with the beacon
Getting a perms error, it seems:
{"level":50,"time":1739393944902,"pid":4522,"hostname":"RatOS","err":{"type":"TRPCError","message":"Could not compile firmware for Octopus Pro H723 V1.1: \n\n Could not compile firmware for Octopus Pro H723 V1.1: EACCES: permission denied, copyfile '/home/pi/ratos-configurator/configuration/boards/btt-octopus-pro-h723-11/firmware.config' -> '/home/pi/klipper/.config'
Probably because I tried a manual clipper flash, shall delete the .config?Are you using the default
pi user or did you change it?Standard user, just with
passwd changed (via cli)that might have messed it up, i've read in here that ratos assumes the defaults. Could try setting it back to
raspberry and try againSolution
Looks like it was just the manual attempt at flashing via klipper. Old habbits die hard.
It generated a
.config in the ~/klipper directory which the pi user then can't overwrite, as the klipper flash was run as root.
So yeah my bad, I created the problem.Thanks for the support guys! Really appreciate it. ❤️
Do what we can! blacksmith knows a lot more than I do but I'm working on it
yeah, I would delete it
and apparently I am looking at old messages and you already did 😅