Yup - that is intended since I did not tell it to leave it.
Sorry that is what I meant, after pressing the button it shows: biqu@BTT-CB1:~/klipper$ lsusb Bus 006 Device 004: ID 0483:df11 STMicroelectronics STM Device in DFU Mode
Even if you unplug it completely?
unfortunately it is really time for bed here - if you want a klipper on it now you can flash @mykepredko menuconfig
with make flash FLASH_DEVICE=0483:df11 as you initially did.
I really appreciate your help!
After restarting it, no, itâs not in DFU mode. However it still will not load, I will try that. Thank you!
ok, now I am back to this.
MCU Protocol error
This is frequently caused by running an older version of the
firmware on the MCU(s). Fix by recompiling and flashing the
firmware.
Your Klipper version is: v0.12.0-286-g81de9a86
MCU(s) which should be updated:
btt_adxl345: Current version v0.11.0-259-geb539911
Up-to-date MCU(s):
mcu: Current version v0.12.0-286-g81de9a86
Once the underlying issue is corrected, use the "RESTART"
command to reload the config and restart the host software.```I finally got this resolved. My original issue, I believe, was that the ADXL board wasnât in boot mode, so it never got updated, and I think somehow I got mixed up and loaded the wrong config to the MCU instead of the ADXL board.
Shout out to @mykepredko and @docgalaxyblock. I appreciate your patience and guidance on this; there would be no way I could have fixed this without you guys!
Iâm very sure youâve done everything below, but I feel like weâre missing something.
Iâve listed the steps below in painful detail to load Klipper into an Octopus and I would like you to go through them exactly as written.
If there are any problems with any of these steps, you donât get what I specify or you have any questions, please stop and ask for guidance.
- Go into the mainsail web page and go to the âMachineâ tab and do a screenshot of the Klipper version. It should be the same version as what is here:
Note your host OS will be different. - Disconnect everything from your BTT PI (This means the Octopus and the SB2040/SB2209 that came up before).
- In SSH, execute
make menuconfigwith the following parameters:
This will provide the latest version of Klipper for the STM32F446 Octopus V1.1 with the âWORK_LEDâ which is located here:
- In SSH, execute
make cleanfollowed bymakeand copy and paste the response in your reply. If the build fails, stop here. - Make sure the jumper at J68 is not present:
This jumper is used to allow the host computer to power the Octopus. Letâs make sure thatâs out. - Connect your Octopus to your BTT Pi with the USB cable and power it on. I presume that you are using a power supply for this which is separate from the BTT Piâs power supply.
- Just out of curiosity, in SSH, execute
lsusbandls /dev/serial/by-id/*and put the results into your reply. There is no good/bad result here as in the other steps. - Now, put your Octopus into DFU mode. To do that, put a jumper on J75 (marked âBOOT0â) and then press the Reset button (marked âSW1â) on the end of the board:
- Letâs check that your Octopus is in DFU mode. In SSH, execute
lsusb
and you should see ID 0483:df11 STMicroelectronics STM Device in DFU Mode: like:
- Burn in the new firmware using the command:
sudo dfu-util -a 0 -D ~/klipper/out/klipper.bin --dfuse-address 0x08000000:force:mass-erase:leave -d 0483:df11
- Remove the jumper on J75 and press reset.
If everything worked correctly, the LED at the top left corner should now be on and when you execute lsusb in SSH, you should get an âOpenMokoâ device.
Next, In SSH, execute ls /dev/serial/by-id/* and report back what you get.
Yup, buttin out 
1 Like
@bigb206 Some post infos:
With the detailed instructions by @mykepredko your octopus no longer has the btt bootloader.
If it works now for you this is totally fine - it would be even possible to reflash the octopus without pressing buttons or setting jumpers.
But if you ever sell it it may create an unfortunate sitation for the new user since the original flashing by sd card instructions do not work.
That is why I personally recommend the flash-sdcard.sh script. It uploads the firmware binary to the inserted sd card, resets the board so that the booloader flashes it and checks after the flash if it succeeded - all with visual representation.
So you maybe want to try this out and then order a or some 128MB card(s) at ali. If they arrive you can ask back in this thread.
Or just leave it as it is since it just worksâ˘ď¸
I will order some cards and give it a try. At this point Iâm just happy the damn thing loaded, but probably a good learning experience to try the sdcard method.
Just curious, how did you guys become so versed in this? A lot experience or do you work as part of your employment?
Sorry for the long set of instructions. Are things working for you now?
Nothing professional (although I did design the board I posted a few weeks back). Just a lot of time trying things and spending 'way too much money.
Yes, all good now!
Thanks for your help!!
1 Like
Glad to hear things are running.
Let me know if you have any other questions and I look forward to see what you print!
Same as @mykepredko here.
Nothing professional yet - just reading and try & error.
I even cannot write code but know how to get and write the binary (compiled code) to microcontrollers
As @mykepredko wrote: If you have problems again do not hesitate to ask again. He, myself or maybe others will answer your question(s)
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.