Pinout & GPIO
Pinout & GPIO
Pin-by-pin map of how the Sixfab Edge AI Expansion Board for Raspberry Pi 5 connects to its host. Power flows up to the Raspberry Pi 5 through pogo pins on the GPIO header underside; data flows through the 40 mm PCIe FFC and a USB Bridge PCBA. Every one of the 40 GPIO pins passes through unused, so the entire header stays free for a top-mounted HAT or your application.
The Sixfab Edge AI Expansion Board for Raspberry Pi 5 mounts under the Pi 5 and contacts four pogo points on the underside of the GPIO header: two 5 V pins and two GND pins. No GPIO data pins are consumed. Every one of the 40 pins on the GPIO header passes through unused, including the HAT+ EEPROM bus on BCM 0 / BCM 1, so any standard top-mounted HAT can sit on the Pi 5 at the same time. The high-speed link to the DEEPX NPU runs over a separate 40 mm PCIe FFC, and the NVMe SSD and LTE/5G modem reach the Pi 5 through a dedicated USB Bridge PCBA. Neither pathway touches the GPIO header.
Pogo-pin power map
The Expansion Board back-powers the Raspberry Pi 5 through four spring-loaded pogo pins that touch the underside of the Pi 5's 40-pin GPIO header. There is no data on these contacts: only the 5 V rail and ground return.
Electrical headroom on the pogo path
Pogo-pin power delivery is reliable only when the 5 mm M2.5 male-female spacers between the Expansion Board and the Pi 5 are securely tightened. Loose spacers cause intermittent contact, brown-outs, and SSD disconnects. Finger-tight is enough; do not over-torque.
High-vibration deployments (drones, mobile robots) have not yet been validated. Long-term reliability of the pogo connection under sustained vibration is unverified.
40-pin GPIO header pass-through
The Expansion Board does not consume any GPIO pins for communication. The 5 V and GND pogo points sit under the header for power, but every signal pin (every GPIO, SPI, I²C, UART, PWM, and even the HAT+ EEPROM bus on BCM 0 / BCM 1) remains fully available to your application or a stacked HAT.
Unlike a HAT, the Expansion Board mounts under the Raspberry Pi 5 and does not present a HAT+ EEPROM. BCM 0 / BCM 1 (pins 27 and 28) are free, so a top-mounted HAT+ board can use the ID bus normally; its EEPROM will be the only one on the bus.
PCIe FFC connector
The Expansion Board reaches the Raspberry Pi 5's PCIe interface through a dedicated 40 mm × 8.5 mm FFC (Flexible Flat Cable), separate from the GPIO header. This cable carries the high-speed PCIe Gen 2 (default) or PCIe Gen 3 link to the DEEPX DX-M1 NPU installed in the M.2-PCIE slot.
Cable specification
40 mm × 8.5 mm. Sixfab-manufactured FFC, included in the box.Electrical envelope
dtparam=pciex1_gen=3 in /boot/firmware/config.txt.
~400–450 MB/slspci from first boot; no bootloader configuration is required for discovery.
Signal groups on the FFC
The 40 mm FFC follows the standard Raspberry Pi 5 PCIe FFC convention. The cable carries the PCIe Gen 2 / Gen 3 x1 differential pairs, the 100 MHz reference clock, the PCIe sideband control signals, and interleaved ground returns. The high-level signal groups are summarized below.
The 40 mm FFC has two clearly labeled ends. Connect the end marked RPI5 to the Raspberry Pi 5's PCIe FFC port, and the end marked EDGE_AI to the Expansion Board's connector. Inserting the cable backwards prevents NPU detection on lspci. If the NPU is missing from lspci after a fresh build, the labels facing OUT and contacts facing IN is the first thing to re-verify.
Always power off the Pi 5 and disconnect the USB-C cable before connecting or disconnecting the FFC. The Edge AI Expansion Board does not support hot-plug. The full mount, cable, and power-on sequence is documented in the Quickstart.
USB Bridge PCBA
Storage and cellular do not reach the Raspberry Pi 5 through the PCIe FFC, and they do not use the GPIO header either. Instead, an internal USB 3.2 Gen 1 hub on the Expansion Board connects to one of the Pi 5's blue USB 3.0 ports through a short USB Bridge PCBA. The NVMe SSD and the LTE/5G modem are children of this hub.
Verifying the bridge after assembly
After the Pi 5 boots, the internal hub and its devices appear in lsusb. The Realtek bridge (NVMe) and the cellular modem each enumerate under the hub:
lsusb
- Bus 002 Device 003 is the LTE/5G modem. The VID:PID depends on which M.2 Key-B module is installed;
2c7c:0125corresponds to the Quectel RM520N-GL. - Bus 002 Device 002 is the Realtek RTL9210 USB-to-NVMe bridge. This VID:PID (
0bda:9210) is fixed for any NVMe in the M.2-SSD slot. - Bus 002 Device 001 is the internal USB 3.0 root hub that hosts the bridge and the modem.
M.2 slots
The Expansion Board carries three M.2 slots. Each is labeled on the silkscreen and routed to a different data path: PCIe for the AI accelerator, USB for storage and cellular.
M.2-PCIE
Key MDirect PCIe Gen 2 / Gen 3 x1 via the 40 mm FFC. Intended for the DEEPX DX-M1 NPU; other M.2 PCIe devices (e.g. Raspberry Pi NVMe, Hailo) work but are unsupported.
M.2-SSD
Key MUSB 3.0 via the on-board Realtek RTL9210B-CG USB-to-NVMe bridge. NVMe SSDs only; M.2 SATA is not supported. Validated up to 2 TB.
CELLULAR LTE/5G
Key BUSB 3.2 Gen 1 via the internal hub. Pairs with one nano-SIM slot; eUICC nano SIMs supported, no on-board eSIM chip.
Mounting hardware per slot
M2 × 6 mmFan connector, test points, jumpers
A few practical reference facts about what is, and what is intentionally not, populated on the Expansion Board.
Fan connector
There is no dedicated fan connector on the Expansion Board itself. The Expansion Board is designed to work alongside the Raspberry Pi 5's own cooling infrastructure: the official Raspberry Pi 5 Active Cooler plugs into the Pi 5's 4-pin JST-SH fan header, which sits on top of the Pi 5 and is unaffected by anything happening below. PWM speed control through the Pi 5 header works exactly as it does on a bare Pi 5.
The Expansion Board mounts under the Pi 5 and is fully compatible with the Active Cooler installed on top.
Test points and debug pads
None. The Expansion Board does not expose hardware test points or debug pads. Diagnostics are software-side: lspci for the NPU, lsusb for the SSD and modem, dxrt-cli -s and dxtop for the runtime, dmesg | grep -i dx for boot-time kernel evidence.
Solder jumpers
None. There are no solder jumpers (SJ) or user-configurable hardware bridges on the Expansion Board. All configuration happens in software (config.txt, raspi-config, the sixfab-dx package).
Power-on button and watchdog
The Expansion Board has no power-on button of its own. To safely shut down the stack, use the Raspberry Pi 5's own button, or sudo shutdown -h now from the OS. There is no Expansion-Board-side watchdog: the hardware watchdog you can use is the one already on the Raspberry Pi 5.
HAT stacking
Because the Expansion Board consumes zero GPIO pins and mounts under the Raspberry Pi 5, the Pi 5's 40-pin header stays fully available on top. A standard HAT can sit on the Pi 5 at the same time as the Expansion Board sits under it.
Stacking compatibility
Board layout
Top-side and bottom-side images of the Expansion Board PCB are distributed as a draftsman file packaged with the product (per Q&A Q47). The file marks all major connectors, the 3× M.2 slots, the nano-SIM tray, the USB-C PD input, the PCIe FFC connector, the four LEDs, the four pogo-pin contacts, and the mounting holes (4× M2.5 + 3× M3). Key dimensional facts are summarized below.
Key dimensional facts
87 × 88 mm88.46 × 89.19 mm. Including USB-A protrusion (X-axis) and USB-C protrusion (Y-axis).~36.26 mm. From the bottom of the 15 mm stand-offs to the tallest component on the Pi 5 (the dual USB 3.0 connector).Updated 5 days ago
