Hardware

This page lists the recommended parts and supported boards for building an OpenMANET node. The project is designed for Raspberry Pi–based devices running OpenWrt, using Wi‑Fi HaLow boards from Morse Micro (MM6108/MM8108).


Supported Hardware (Firmware-Dependent)

SBC

Device Status Notes
Raspberry Pi 4 / CM4 ✅ Tested Onboard Wi‑Fi works in AP mode on SPI-based builds
Raspberry Pi 3B ✅ Supported Requires selecting the correct image for your HaLow interface
Raspberry Pi Zero 2 W (Pi2W) ✅ Supported Uses the rpi3 firmware images; requires selecting the correct HaLow interface

HaLow

Device Interface MM Chipset Notes
Seeed WM1302 + Wio-WM6108 SPI 6108 Common “Seeed board” setup
Silex SX-SDMAH SDIO 6108  
Alfa AHPI6108E SDIO 6108  


Board Interface Types: SDIO vs SPI

HaLow modules connect to the Raspberry Pi through different interfaces depending on the board design:

Interface Description Supported on
SDIO High-speed 4-bit data bus. Offers better throughput and lower latency. Image-dependent (common on Pi 4 / Pi 3B / CM4)
SPI Serial Peripheral Interface used by some HaLow HATs (for example Seeed boards). Easier to wire but typically slower than SDIO. Image-dependent (Pi 4 / CM4 / Pi 3B / Pi2W supported on current firmware)

Notes:

  • Select firmware downloads carefully: the board type, Morse Micro chipset (MM6108 vs MM8108), and interface (SPI vs SDIO) are part of the firmware filename.
  • On SDIO-based HaLow builds, onboard Wi‑Fi usually cannot be used due to SDIO bus conflicts.
  • On SPI-based HaLow builds, onboard Wi‑Fi can be used for client access (AP mode).
  • In general, spi images are for SPI-based Seeed HaLow boards; sdio images are for SDIO-based modules (for example Silex or Alfa).

Radio Calibration (BCF Files)

HaLow radios use board configuration files (BCF) to set calibration and regulatory parameters. Some cards or devices, may need to acquire the BCF file from the manufacturer, and be copied to each device.


Optional / Advanced Parts

Compute Module 4 (CM4) Builds

Most Raspberry Pi Compute Module 4 (CM4) carrier boards work with the OpenMANET image.
A good option is the WaveShare CM4 Dual ETH WiFi6 Base, which includes:

  • Two Ethernet ports for bridging or mesh uplink
  • An M.2 slot for a standard Wi-Fi card (AX200 or AX210)
  • Full GPIO header and USB ports for power and debug

CM4 boards are ideal for advanced builds, providing better expandability and efficiency for multi-interface mesh nodes.

WaveShare CM4 build overview

WaveShare CM4 internals

Other tested CM4 Carrier Boards

WaveShare CM4-IO-Base-X Version A and B have been tested and work as expected CM4-IO-BASE-A CM4-IO-BASE-B

Notes:

  • A M.2 M Key slot for communcation cards
  • Full GPIO Header
  • Same form factor as a Pi4

MCUZone CM4_WiFi6 This is a slightly larger carrier board than the WaveShare boards.

Can be found on AliExpress

Notes:

  • A M.2 A Key slot for communications cards. This is limited to the 2230 form factor.
  • Full GPIO Header
  • Better for height constrained use cases, but a larger length and width form factor.

M.2 Wi-Fi Cards for CM4 Boards

Module Band Support Current Use
Intel AX200 2.4 / 5 GHz Wi-Fi 6 Works as an access point
Intel AX210 2.4 / 5 / 6 GHz Wi-Fi 6E Works as an access point

These cards currently operate as normal Wi-Fi access points.

M.2 Wi-Fi Cards that support 802.11s

Chipset Interface 802.11s Notes
Intel AX2XX M.2 AE Key no Can only operate in AP mode
QCNA765 M.2 E Key no  
WCN6856 M.2 E Key no  
QCA6174 M.2 E Key yes You can only have one wifi network defined when using 802.11s
MT7921 M.2 E Key no  
MT7915DAN M.2 BM Key yes Dual Band AX; 802.11s mesh works, but stability may vary by kernel/driver
MT7916AED M.2 AE Key yes Dual Band AX; 802.11s mesh works, but stability may vary by kernel/driver

Work is underway to support bonding of HaLow (915 MHz) and 2.4 GHz links together using BATMAN-V for multi-band uplinks.


Development Notes and Future Plans

  • Separate firmware builds for SDIO and SPI boards simplify setup.
  • CM4 carrier boards are increasingly recommended for advanced configurations.
  • Future releases will expand multi-gateway mesh support and improve multicast reliability.