Erik Persson
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 6/8/2024 in #ratos-support
Invalid option pullup_resistor
Thanks @miklschmidt! I should really have thought of that myself. 🙂 And @blacksmithforlife 🇺🇸 : So far 2.1RC has been working great except for this issue and that was definitely self-inflicted.
5 replies
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 1/24/2023 in #ratos-support
Unable to flash Octopus 1.1 on RatOS 2 alpha5
So I finally had some time to investigate this further. Without BOOT0 the board will not show up at all when power cycled. With BOOT0 and one press of the reset button it will enter DFU mode.
From DFU I can flash it using dfu-util after which it will reset and actually present itself as a klipper device with all the correct characteristics and it can be used from RatOS.
Another power cycle will render the board inop again, BOOT0 setting regardless but it will again enter DFU mode and the process can be repeated.
As this starts to look like a bootloader issue I reflashed the bootloader with STM32Cube programmer using the firmware image from BTT GitHub and now the board has started to work normally again. It even booted the correct klipper firmware I had previously flashed.
There was no messing on my part with tools like dfu-util or "make flash..." leading up to the point when it went inop and it had undergone quite a number of automatic flashing procedures on RatOS 2 before so I am not sure what happened here.
i guess there was some transient flaw in the flashing scripts that existed when I redeployed the bullseye based RatOS 2a image causing the bootloader to break, possibly by not using the correct offset when writing the image.
I also guess that the inability to install firmware via SD-card also could be explained by a broken bootloader.
The upside to all this is that it is quite easy to rescue these boards using the STM32 programmer.
The spare Octopus board remains in the antistatic bag for now. 🙂
18 replies
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 1/24/2023 in #ratos-support
Unable to flash Octopus 1.1 on RatOS 2 alpha5
I will try that when I am back at the printer next week. If everything fails I have a spare Octopus board ready.
18 replies
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 1/24/2023 in #ratos-support
Unable to flash Octopus 1.1 on RatOS 2 alpha5
It should be added that it is not out of the question that it has some kind of hardware issue. It did have a little accident when I added a cooling fan some time back when the fan connector was yanked from its socket when powered on. That seems to have fried the fan PWM regulator IC since none of the fan outputs work. All the other fans is on the EBB42 so I could still use the board.
18 replies
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 1/24/2023 in #ratos-support
Unable to flash Octopus 1.1 on RatOS 2 alpha5
And I am trying to think about something I did but the only thing that was done to the card was to upgrade klipper using the RatOS alpha 5 GUI - after which it did work as well.
18 replies
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 1/24/2023 in #ratos-support
Unable to flash Octopus 1.1 on RatOS 2 alpha5
Exactly.
18 replies
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 1/24/2023 in #ratos-support
Unable to flash Octopus 1.1 on RatOS 2 alpha5
Ah, thanks for pointing that out @miklschmidt! I forgot that the short name was directly under /dev.
The remaining issue is why it wont boot with the boot0 jumper removed. I did use the configurator to configure the octopus and toolboard when redeploying with alpha5 and that worked just fine and everything worked. And then at some point, the board would no longer show up after a reboot unless in DFU mode.
18 replies
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 1/24/2023 in #ratos-support
Unable to flash Octopus 1.1 on RatOS 2 alpha5
So I found a 16GB SD card which i formated with (Linux) fdisk with 1 primary partition of type W95 FAT32 on which i created a vfat file system. There is no specific mkfs.fat32 in Linux and vfat should be backwards compatible.
Copied the printer_data/config/firmware_binaries/firmware-btt-octopus-11.bin to firmware.bin on the root of the sd-card partition, removed boot0 jumper on the octopus and powered on with sd-card and it will not upgrade.
Enabling boot0 and resetting the board puts it into DFU mode again in which I tried to flash the same firmware with
dfu-util -d ,0483:df11 -R -a 0 -s 0x8008000:leave -D ~pi/printer_data/config/firmware_binaries/firmware-btt-octopus-11.bin
This sort if suceeds since it resets and presents a serial device named:
/dev/serial/by-id/usb-Klipper_stm32f446xx_btt-octopus-11-if00
That name is of course not what it should be given the RatOS Octoups firmware config file.
Resetting the board without boot0 will not cause it to not to show up at all again but DFU works with boot0 jumper in.
Could I have borked the bootloader perhaps?
18 replies
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 1/24/2023 in #ratos-support
Unable to flash Octopus 1.1 on RatOS 2 alpha5
Haven't tried that actually. When I previously have attempted flashing via SD-card I have never succeeded. I tried the first time but it would never take so I suspected I got the wrong combination of SD card size, block size, FAT parameters (on Linux) and since I had better success with dfu-util or stm32cube programmer.
But if course, if I can fix it that way...
18 replies
RRCRat Rig Community [Unofficial]
•Created by Vausch on 12/9/2022 in #ratos-support
Can't install firmware on Octopus v1.1
I gave up trying to find a suitable SD card for reflashing my bricked Octopus 1.1. Since I had extensive experience DFU flashing mu EBB42 I was initially stumped trying to find out how to get the Octopus into DFU mode - the manual says that it supports DFU but not how to enable it (or my reading skills are not sufficient). After some more googling I came to the following recipe to flash the Octopus 1.1 using DFU:
1) Install the boot0 jumper and press the reset button for a few seconds, verify with "dmesg" in the RPi that a STM32446 device in DFU mode has been discovered. 2) Proceed it to flash in from klipper with 'make flash FLASH_DEVICE=0483:df11' and check output for errors. 3) Power down, remove boot0 jumper and power on.
27 replies
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 12/3/2022 in #ratos-support
Print job gets paused waiting for filament
Yep, that was definitely it. Learning something every day...
5 replies
RRCRat Rig Community [Unofficial]
•Created by Erik Persson on 12/3/2022 in #ratos-support
Print job gets paused waiting for filament
I checked the Gcode for the print and found this before the start of the print:
;COLOR_CHANGE,T0,#6EBB38
; custom gcode: color_change_gcode
M600
; custom gcode end: color_change_gcode
I guess that is responsible for this behaviour meaning that this is more a superslicer support issue. I have a "Color change gcode" defined in the printer settings as M600 but that is nothing new and until now nothing I have really reflected upon. Question is why the slicer has started to issue an M600 at the start of the print.
5 replies