Error with firmware flash

Great, thank you! I will keep you posted!

If the restore works you can try putting the firmware binary to an sdcard or try using klippers scripts/flash-sdcard.sh utility.

Well, I was able to download the bootloader to the chip, but I am still not getting anything for devices. ls: cannot access '/dev/serial/by-id/*': No such file or directory

You only have a bootloader on your board and no main programm (klipper)
Try supplying the firmware file with the sdcard and let the bootloader flash it.
Onl a klipper flashed board will announce itself to linux and then a device in/dev/serial/by-id/ gets created

I believe there is a limit on the SD card size. I only have a 32gb sd card; I will need to order a 4gb size before I can flash the config using scripts/flash-sdcard.sh correct?

Uhm I do not remember what the requirement was.
Could be that it needs to be partioned as FAT/FAT16 or the type of the sd standard classic SD vs SD-HC or newer (SD card - Wikipedia)

Just try it with a FAT32 formated card if that does not work try formating it to the classic FAT/FAT16.

If @bigb206 has been using dfu-util, then the BTT supplied bootloader has been overwritten.

He can put the BTT bootloader back onto the board, but he will have to use dfu-util to do it (unless he has an ST-Link).

With what he’s reporting, it seems like there is a problem in the Octopus to BTT Pi USB link. We’re going to have to figure out what it is.

Should I reload the PI software to see if that works?

He has the bootloader restored to the board - at least the assumption that the process succeeded.

No since a not flashed board will not “announce itself” when connected to a host device.
Try putting your compiled firmware.bin for your octopus on a sdcard formated as said above.

If successfully flashed it will announce itself as a usb device


If that does not work we can try flashing the firmware with dfu-util without overwriting the bootloader.

Can we test that assumption?

@bigb206 you just asked:

Should I reload the PI software to see if that works?

What level are you working at now?

I just checked my systems and the latest seems to be v0.12.0-286-g81de9a86 - can you confirm what your level is?

Going back to seeing that the firmware is being updated, @bigb206 once you have the latest version of Klipper, could you do a new make menuconfig with the following parameters:

I just noticed above that you didn’t have the “Bootloader Offset” option; I suspect you had a too downlevel version of Klipper (I know I should have checked the klippy.log - sorry).

After loading this firmware, you should have the “WORK_LED” lighting - it wouldn’t have been on before.

Please let me know how things work out for you.

This menuconfig would overwrite the stock bootloader again - “No Bootloader” instead of “32KiB bootloader”

I am at v0.12.0-125-gbfb71bc2

If the stock bootloader is gone, it’s gone. You’re not getting it back unless you install it again.

DFU is the most reliable, easiest way of getting Klipper in and it provides visual confirmation that it took place.

Update it.

By using the install make?

Sure.
He should have restored it with the btt pdf manual - stm32cubeprogramme also gives visual feedback if it took place

Yes, there was visual feedback that it downloaded successfully.

But since then, I tried to download the config using the DFU.

Ok then we use dfu-util to write klipper to the right place with a 32KiB bootlaoder offset

Configure your make menuconfig as you previously posted and build (make) it.
Instead of make flash use

sudo dfu-util -a 0 -d 0483:df11 -D ~/klipper/out/klipper.bin --dfuse-address 0x08008000

to flash it while the octopus is connected in DFU mode.
After flashing press the reset/RST button and check by lsusb if the board appears.

Looks good, but still is showing in DFU mode after the download.

biqu@BTT-CB1:~/klipper$ make menuconfig
Loaded configuration '/home/biqu/klipper/.config'
No changes to save (for '/home/biqu/klipper/.config')
biqu@BTT-CB1:~/klipper$ make
make: Nothing to be done for 'all'.
biqu@BTT-CB1:~/klipper$ sudo dfu-util -a 0 -d 0483:df11 -D ~/klipper/out/klipper.bin --dfuse-address 0x08008000
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0483:df11
Run-time device DFU version 011a
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 2048
DfuSe interface name: "Internal Flash  "
Downloading to address = 0x08008000, size = 31812
Download        [=========================] 100%        31812 bytes
Download done.
File downloaded successfully