> For the complete documentation index, see [llms.txt](https://docs.siboor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siboor.com/other-products/klipper-expander/flashing-instructions.md).

# Flashing Instructions

Connect the board to the host Raspberry Pi via USB.

1. Connect to your host raspberry pi via SSH.
2. Install the boot jumper and reset the board. This will put the board into DFU mode.
3. Run `lsusb` from the command prompt
   * Make sure you see an STM32 in DFU mode listed
4. Run `dfu-util --list` from the command prompt
   * note the text inside the \[xxxx:yyyy]
5. Run `cd ~/klipper` from the command line to enter the Klipper directory
6. Run `make menuconfig` settings should be:

<figure><img src="/files/cdvscFysV5lWRJpaeN77" alt=""><figcaption></figcaption></figure>

* Set the "Optional features" to

<figure><img src="/files/XPivwNpBHKn4uUtooaOA" alt=""><figcaption></figcaption></figure>

* Hit `Q` to Exit and Save

1. Run `make clean` to clean up the make environment.
2. Run `make flash FLASH_DEVICE=xxxx:yyyy` (using xxxx:yyyy from above)
3. Remove the boot jumper and press the reset button.
4. After completion `ls /dev/serial/by-id/*` should return a device begining with `/dev/serial/by-id/usb-Klipper_stm32f042x6...`
5. Copy this serial port name (`/dev/serial/by-id/usb-Klipper_stm32f042x6...`) and place it in your \[mcu expander] section of the config file.

Your board should now be usable with Klipper. Use the example config file to get started Best option is to copy the example config file into the same directory as `printer.cfg` then add `[include klipperExpander.cfg]` to the end of your `printer.cfg` to include the file.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.siboor.com/other-products/klipper-expander/flashing-instructions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.