diff options
| -rw-r--r-- | html/blog/2026-09-04+EBB36_Artery_Clone:_Klipper_Install+guide+tech.tmpl.html | 16 | ||||
| -rw-r--r-- | static/media/EBB36_Clone_Config.jpg | bin | 0 -> 71198 bytes |
2 files changed, 16 insertions, 0 deletions
diff --git a/html/blog/2026-09-04+EBB36_Artery_Clone:_Klipper_Install+guide+tech.tmpl.html b/html/blog/2026-09-04+EBB36_Artery_Clone:_Klipper_Install+guide+tech.tmpl.html new file mode 100644 index 0000000..8d7a4ff --- /dev/null +++ b/html/blog/2026-09-04+EBB36_Artery_Clone:_Klipper_Install+guide+tech.tmpl.html @@ -0,0 +1,16 @@ +{{ define "article" }} +<article> + <h2>{{ .Title }}</h2> + <p><i>This is part of a larger effort to revive my donated Voron V2.4 FDM printer. With a lot of headache and difficulty finding information for Chinese clone hardware (of which this printer has a few pieces), I decided to put up some information here for my future self and others to reference.</i></p> + <p>Starting with the hardware. I have a clone of a BigTreeTech EBB36, labeled (un-)helpfully as "36 PRO V1.2", which has an Artery AT32F415CBT7 microchip. Digging a bit lead me to the conclusion that it is a drop-in replacement (mostly) for the STM32F103 series found in many eletronics boards. From what I can tell, the Artery chip was chosen to hit a lower price point as well as filling a hole during the early chip shortage.</p> + <p>Compiling Klipper firmware for it is pretty straightforward once you know what settings are required. Namely, you can target the STM varient, and it will work as expected. This <a href="https://global.bttwiki.com/EBB%20Series.html" target="_blank" rel="noopener noreferrer">BIGTREETECH wiki guide</a> was helpful in getting started, but these are my settings when running <code>make menuconfig</code>:</p> + <figure> + <img src="/static/media/EBB36_Clone_Config.jpg" alt="Make menuconfig options: [*] Enable extra low-level configuration options \n Micro-controller Architecture (STMicroelectronics STM32) \n Processor Model (STM32F103) \n Bootloader offset (No bootloader) \n Clock Reference (8 MHz crystal) \n Communication interface (CAN bus (on PB8/PB9)) \n (1000000) CAN bus speed. Leave other options default value/same as other guide." width="623" height="350" /> + <figcaption>Target STM32F103 chip, No bootloader offset, 8 MHz crystal, and CAN communication on PB8/PB9</figcaption> + </figure> + <p>Some things to note. This printer was set up to communicate via CAN, so that's how mine is configured. Specifically pins PB8/PB9 worked for me. This is pretty common for this board setup, but trial and error works as well to find a different pin layout with no ill effects. If you plan to communicate over USB or another method, select that instead.</p> + <p>I flashed mine over USB in DFU mode. The guide on getting into DFU mode worked on my board, but the buttons were in very different locations. This was my other big hurdle. The flash command specified in the guide kept giving an error 255. This ended up being an issue with the Artery chip not having the complete featureset of the ST chip. You can modify the makefile or run <code>dfu-util</code> instead: <code>sudo dfu-util -d <dev:id> -a 0 -s 0x08000000 -D out/klipper.bin</code> making sure to replace <code><dev:id></code> with the id listed when running <code>lsusb</code>.</p> + <p>After a power cycle, that should be it, now running a new version of Klipper firmware.</p> + <p><b>Created:</b> {{ .Date }}</p> +</article> +{{ end }} diff --git a/static/media/EBB36_Clone_Config.jpg b/static/media/EBB36_Clone_Config.jpg Binary files differnew file mode 100644 index 0000000..f59e780 --- /dev/null +++ b/static/media/EBB36_Clone_Config.jpg |
