How gblach/hexgateway works
Project type and purpose
• This is a hardware-centric gateway board (“HexGateway”) combining three network-capable chips (nRF52840, ESP32-C3, ENC28J60) into a single PCB design.
• Purpose: receive Bluetooth LE / OpenThread / Zigbee on the nRF52840, WiFi on the ESP32-C3, and Ethernet on the ENC28J60, and forward traffic between them (e.g., BLE → WiFi/Ethernet).
File structure
• Top level:
• KiCad project files (HexGateway.kicad_sch, .kicad_pcb, sym-lib-table, fp-lib-table, component libraries and 3D models under .pretty and .models).
• boards/arm/hexgw1: Zephyr board definition (CMakeLists.txt, Kconfig, DTS, pin-control, defconfig).
• You also have CSV BOM, Gerber ZIP, footprint libraries, and device programming connector schematics.
Extract insights from README
• Hardware modules U1 (nRF52840), U101 (ESP32-C3), U201 (ENC28J60).
• Programmers and connectors: Segger J-Link on J1/J2 for nRF52840, ESP-Prog on J101/J102 for ESP32-C3.
• Software stack: nRF52840 runs user code on Zephyr RTOS (custom board in boards/arm/hexgw1), ESP32-C3 runs AT firmware, ENC28J60 is controlled via SPI by nRF52840 or ESP32-C3 (depending on design).
Elements
• Clear labels: “nRF52840 + Zephyr”, “ESP32-C3 + ESP-AT”, “ENC28J60”, “Power Regulator”, “RJ45”, “Antennas”, “Programmer Headers”
• Data flows between MCUs and controllers (SPI/UART lines)
• External network flows in/out of antennas/ethernet port
• Programming flows into MCUs
• Firmware/software blocks in another (e.g., green)
1. Power & ground bus at the center bottom.
2. Three rectangular blocks above it: nRF52840 on left, ESP32-C3 center, ENC28J60 right.
6. Block with firmware: “Zephyr RTOS + your application” on nRF52840, “ESP-AT firmware” on ESP32-C3, “SPI Ethernet Controller” on ENC28J60.