MCU Reference¶

Reference material for some of the MCU/control boards Happy Hare's installer knows about - pinouts, connection diagrams, and firmware-flashing notes for the ones with images available, plus the complete current list of every board menuconfig's Board type screen offers. Picking one there sets up the default pin layout for your setup automatically; pins can still be customized afterward in Advanced Settings if needed. See Getting Started with Box Turtle for what that screen actually looks like.

Popular MCUs¶

Standard EASY-BRD (SAMD21)¶

Fysetc Burrows ERB v2¶

BTT MMB CAN v1.0¶

BTT MMB CAN v2.0¶

BTT EBB CAN (EBB42 / EBB36)¶

The BTT EBB CAN board has gone through three hardware revisions, each with a different pinout, offered in both an EBB42 and EBB36 size. The installer's BTT EBB 42 CANbus V1.2 board choice (and the per-gate EBB MCU choice used by EMU designs) targets the v1.1/v1.2 revision below - its default pin layout matches that hardware directly.

v1.0¶

BTT EBB42:

BTT EBB36:

v1.1 / v1.2¶

BTT EBB42:

BTT EBB36:

Gen2¶

BTT EBB42:

BTT EBB36:

Mellow EASY-BRD CAN v1¶

Mellow EASY-BRD CAN v2¶

Solo Lane Board v1¶

AFC Pro v1.0¶

AFC Lite v1.0¶

All Supported Boards¶

Every board menuconfig's Board type screen offers, direct from the installer's own Kconfig source - not just the ones with a pinout image above. Most MMU types choose from the general list; per-gate MCU designs (EMU) get their own list instead, and two MMU types (Box Turtle/KMS and BTT ViViD) have a single fixed board rather than a choice at all.

General boards¶

Offered for any MMU type except a per-gate MCU design, Box Turtle/KMS, or BTT ViViD:

Per-gate boards (EMU multi-MCU designs)¶

A per-gate MCU setup (--emu/-e on the installer, see Installation) picks one of these per gate instead of a single board for the whole unit:

Fixed boards¶

These two MMU types skip the board-choice screen entirely - the board is part of the design:

See Getting Started with BTT ViViD for that design's own MCU connection walkthrough.

Flashing Firmware¶

Klipper firmware needs flashing to the MCU before it'll talk to Klipper at all:

1. SSH into your Raspberry Pi.

2. Open a shell there and run:

   cd ~/klipper
   make menuconfig
   

3. Configure your board's firmware settings (chip, bootloader, communication interface) - specific to the MCU chip on your board, not something this page can give one universal answer for.

4. Save and exit (Q).

5. You will need the correct device name. You can use lsusb to list all USB devices. E.g

   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 007: ID 2e8a:0003 Raspberry Pi RP2 Boot
   Bus 001 Device 004: ID 1d50:614e OpenMoko, Inc. stm32f446xx
   

   ID 2e8a:0003 should match you new device. Then flash it:

   make flash FLASH_DEVICE=2e8a:0003
   

   Alternatively you can find you device with ls -l /dev/serial/by-id and flash:

   make flash FLASH_DEVICE=/dev/serial/by-id/<your-mcu-id>
   

See also¶