![Rat Rig Community [Unofficial]](https://cdn.discordapp.com/icons/582187371529764864/08375bea6b5b9088b6d4cfc2b6e25fba.webp?size=48){kind=icon}
Unable to flash Octopus 1.1 on RatOS 2 alpha5
Hi,
Having been a very happy camper running buster-based RatOS 2 alpha I proceeded and reinstalled with the alpha 5 bullseye image and merged my old conf into the new one. Everything was fine until sometime after I applied updates which included klipper to v0.11.0-86-g6026a99a and sometime after that the board would no longer show up on the USB bus following a firmware restart.
I have found myself in the position of having an inaccessible MCU and so far I have been able to dig myself out of that particular hole by setting the board to DFU mode and flashing klipper with 'make flash...' but now there seems to be something wrong with the build environment. The steps I have been following to build and flash is to:
# set octopus to DFU mode, and reset. lsusb shows:
# Bus 001 Device 003: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
cd klipper
../printer_data/config/RatOS/boards/btt-octopus-11/firmware.config .config
make clean
make flash FLASH_DEVICE="0483:df11"
The flashing part bails however with:
Flashing out/klipper.bin to 0483:df11
Usage: flash_usb.py [options] -t <type> -d <device> <klipper.bin>
flash_usb.py: error: option -s: invalid integer value: ''
make: *** [src/stm32/Makefile:98: flash] Error 2
As far as I can tell it fails because no valid argument is set for -s. Making the Makefile echo the flash command shows:
@python3 ./scripts/flash_usb.py -t stm32f446xx -d 0483:df11 -s out/klipper.bin
In the same Makefile it appears that -s is set to "$(CONFIG_FLASH_APPLICATION_ADDRESS)" but I cannot see where that variable is supposed to come from.
Any ideas?
Having been a very happy camper running buster-based RatOS 2 alpha I proceeded and reinstalled with the alpha 5 bullseye image and merged my old conf into the new one. Everything was fine until sometime after I applied updates which included klipper to v0.11.0-86-g6026a99a and sometime after that the board would no longer show up on the USB bus following a firmware restart.
I have found myself in the position of having an inaccessible MCU and so far I have been able to dig myself out of that particular hole by setting the board to DFU mode and flashing klipper with 'make flash...' but now there seems to be something wrong with the build environment. The steps I have been following to build and flash is to:
# set octopus to DFU mode, and reset. lsusb shows:
# Bus 001 Device 003: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
cd klipper
../printer_data/config/RatOS/boards/btt-octopus-11/firmware.config .config
make clean
make flash FLASH_DEVICE="0483:df11"
The flashing part bails however with:
Flashing out/klipper.bin to 0483:df11
Usage: flash_usb.py [options] -t <type> -d <device> <klipper.bin>
flash_usb.py: error: option -s: invalid integer value: ''
make: *** [src/stm32/Makefile:98: flash] Error 2
As far as I can tell it fails because no valid argument is set for -s. Making the Makefile echo the flash command shows:
@python3 ./scripts/flash_usb.py -t stm32f446xx -d 0483:df11 -s out/klipper.bin
In the same Makefile it appears that -s is set to "$(CONFIG_FLASH_APPLICATION_ADDRESS)" but I cannot see where that variable is supposed to come from.
Any ideas?
![Rat Rig Community [Unofficial] banner](https://cdn.discordapp.com/banners/582187371529764864/4ee3e42e227d6aac26f048a3e69d5924.webp?size=480)
The #1 unofficial Rat Rig Community on Discord!
14,070Members
Resources
Similar Threads
Was this page helpful?
![Rat Rig Community [Unofficial]](https://cdn.discordapp.com/icons/582187371529764864/08375bea6b5b9088b6d4cfc2b6e25fba.webp?size=16){kind=icon}