<p>I ended up not using the supplied CB1 image from BTT instead a vanilla/standard Armbian distribution was installed. This installation did not have the problems listed on the question.</p>
<p>Running Klipper now on my CoreXY HyperCube Evolution.</p>

CC BY-SA 4.0
2024-08-03T18:43:32.437Z
2024-12-04T08:25:13.977Z
2024-12-04T08:25:13.977Z
0scar
<p>I'm in the process of converting my main CoreXY printer to Klipper firmware. I acquired a BTT (BigTreeTech) Pi v1.2 and a BTT Octopus Pro v1.1. The latter is using the STM32H723ZET6 microprocessor.</p>
<p>I downloaded the BTT Pi image (as it is not compatible with Raspbian) using their official image <code>CB1_Debian11_Klipper_kernel5.16_20240319.img.xz</code> found <a href="https://github.com/bigtreetech/CB1/releases" rel="nofollow noreferrer">here</a>.</p>
<blockquote>
<p><em>Note that the WiFi of the BTT Pi only supports 2.4 GHz!</em></p>
</blockquote>
<p>I proceeded by creating a <code>firmware.bin</code> file (called/renamed from the <code>klipper.bin</code> in the <code>~/klipper/out/</code> directory) after compiling the firmware using the following options for my controller board:</p>
<pre><code>Micro-controller Architecture (STMicroelectronics STM32)  ---&gt;
Processor model (STM32H723)  ---&gt;
Bootloader offset (128KiB bootloader)  ---&gt;
Clock Reference (25 MHz crystal)  ---&gt;
Communication interface (USB to CAN bus bridge (USB on PA11/PA12))  ---&gt;
CAN bus interface (CAN bus (on PD0/PD1))  ---&gt;
USB ids  ---&gt;
(1000000) CAN bus speed
</code></pre>
<p>From the configuration:</p>
<p><a href="https://i.sstatic.net/6TiAZbBM.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/6TiAZbBM.png" alt="Screenshot of &quot;make menuconfig&quot;" /></a></p>
<p>I copied the <code>firmware.bin</code> onto an SD card and booted the Octopus board.</p>
<p>To give your BTT Pi access to the MCU of the controller board, the Klipper documentation, more precisely: &quot;<a href="https://www.klipper3d.org/FAQ.html" rel="nofollow noreferrer">Where's my serial port?</a>&quot; can be consulted to find the address of the USB connection using <code>ls /dev/serial/by-id/*</code>. However this doesn't work!</p>
<p>Looking up the problems hints to using <code>ls /dev/serial/by-path/*</code> instead, but this also fails!</p>
<p>This is because the <code>/serial/</code> directory doesn't exist!</p>
<p><a href="https://i.sstatic.net/oJTiaKSA.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/oJTiaKSA.png" alt="Listing of /dev" /></a></p>
<p>How do I connect the BTT Pi to the Octopus Pro MCU over the serial connection?</p>

CC BY-SA 4.0
2024-08-06T12:34:44.727Z
No idea WRT to Klipper and special RPi OS's. But since there are no responses over 2 days I can suggest general Linux approaches. The method described above might work. But instead of looking at /dev/serial..., just look at /dev w/ & w/oi the BTT USB serial port plugged into the RPi and note any new devices. Unless there are unusual UDEV rules, there should be a new device appearing in the /dev directory. Probably w/a name like "ttyUSB0" or "ttyUSB1".
st2000
CC BY-SA 4.0
2024-08-06T21:30:02.643Z
Yes it should be one of those. I ditched the BTT Pi and use a RPi 4 now, works as a charm. As a side project I'm now in the process of configuring Armbian and use KIAUH to install the rest on the BTT Pi, note that the latter doesn't run recent versions of Armbian, an older version does seem to boot.
0scar
<firmware><klipper><serial-connection><btt-pi>
BTT Pi fails to list USB connection with `ls /dev/serial/by-id/*` (or /by-path/*); how to connect to the controller board MCU?
0scar
# BTT Pi fails to list USB connection with `ls /dev/serial/by-id/*` (or /by-path/*); how to connect to the controller board MCU?

(Asked by: username_0 on 2024-08-03)

I'm in the process of converting my main CoreXY printer to Klipper firmware. I acquired a BTT (BigTreeTech) Pi v1.2 and a BTT Octopus Pro v1.1. The latter is using the STM32H723ZET6 microprocessor.
I downloaded the BTT Pi image (as it is not compatible with Raspbian) using their official image CB1_Debian11_Klipper_kernel5.16_20240319.img.xz found here.

Note that the WiFi of the BTT Pi only supports 2.4 GHz!

I proceeded by creating a firmware.bin file (called/renamed from the klipper.bin in the ~/klipper/out/ directory) after compiling the firmware using the following options for my controller board:
Micro-controller Architecture (STMicroelectronics STM32)  --->
Processor model (STM32H723)  --->
Bootloader offset (128KiB bootloader)  --->
Clock Reference (25 MHz crystal)  --->
Communication interface (USB to CAN bus bridge (USB on PA11/PA12))  --->
CAN bus interface (CAN bus (on PD0/PD1))  --->
USB ids  --->
(1000000) CAN bus speed

From the configuration:

I copied the firmware.bin onto an SD card and booted the Octopus board.
To give your BTT Pi access to the MCU of the controller board, the Klipper documentation, more precisely: "Where's my serial port?" can be consulted to find the address of the USB connection using ls /dev/serial/by-id/*. However this doesn't work!
Looking up the problems hints to using ls /dev/serial/by-path/* instead, but this also fails!
This is because the /serial/ directory doesn't exist!

How do I connect the BTT Pi to the Octopus Pro MCU over the serial connection?

**Tags:** firmware, klipper, serial-connection, btt-pi
> **Comments:**
> **username_1**: No idea WRT to Klipper and special RPi OS's. But since there are no responses over 2 days I can suggest general Linux approaches. The method described above might work. But instead of looking at /dev/serial..., just look at /dev w/ & w/oi the BTT USB serial port plugged into the RPi and note any new devices. Unless there are unusual UDEV rules, there should be a new device appearing in the /dev directory. Probably w/a name like "ttyUSB0" or "ttyUSB1".  
> **username_0**: Yes it should be one of those. I ditched the BTT Pi and use a RPi 4 now, works as a charm. As a side project I'm now in the process of configuring Armbian and use KIAUH to install the rest on the BTT Pi, note that the latter doesn't run recent versions of Armbian, an older version does seem to boot.  

---

## 1 answers

### Answer by username_0 on 2024-08-03. Score: 1 | Accepted answer

I ended up not using the supplied CB1 image from BTT instead a vanilla/standard Armbian distribution was installed. This installation did not have the problems listed on the question.

Running Klipper now on my CoreXY HyperCube Evolution.


---

