CPU / main boards

ESP32-H2-DevKitM

No Wi-Fi. Bluetooth or 802.15.4 for locks, lamps and leaf nodes.

CPU / main boards No Wi-Fi802.15.4 ESP32-H2

01 Overview

The ESP32-H2 is a wireless SoC without Wi-Fi, featuring only BLE 5 and 802.15.4 (Thread/Zigbee). It addresses products that need short-range, low-power communication without touching a router.

Typical use cases: smart locks, lamp controls, sensor leaf nodes that join a Thread or Zigbee network but do not connect to the cloud directly.

The cloud path is delegated to a nearby gateway (like a C6 or ESP32 with Wi-Fi); this board handles only local wireless and logic.

It is not a general-purpose board: no Wi-Fi, so no direct MQTT or HTTP to the cloud; also not suited for high-throughput data.

The devkit is small, with enough pins for a local product, suitable for prototyping and as the core of a final product.

02 Hardware

  • Chip: ESP32-H2, RISC-V core, supports BLE 5 and 802.15.4.
  • Radio: BLE 5 + 802.15.4, no Wi-Fi; keep antenna area clear.
  • USB: DevKit programming port for flashing and debugging.
  • Power: USB-powered on board; see schematic for voltage range.
  • I/O: small board, enough pins for a local product; follow silkscreen.
  • Peripherals: GPIO, SPI, I2C, UART, ADC; see schematic for pin mapping.
  • Watch: do not copy Wi-Fi Station / MQTT examples; pair it with a gateway.
  • Layout: keep antenna area free of copper and traces for RF performance.

03 Software flow

Set ESP-IDF target to ESP32-H2. No Wi-Fi — do not copy Station / MQTT-to-cloud examples.

Flash blink first to verify download and clock, then initialize BLE or 802.15.4 stack.

BLE mode: configure GATT services, handle pairing and connection events, exchange data via characteristics.

802.15.4 mode: join a Thread or Zigbee network as a leaf node, communicate with the gateway.

Keep cloud path on the gateway; this board handles only local radio and logic.

For low power: use sleep modes, wake on timer or event, and configure GPIO properly.

Use this board's silkscreen for pins; do not copy from other devkits.

04 Core points

Use H2 when the device must not join a router. If it must reach the internet itself, pick C3, C6 or ESP32.

BLE and 802.15.4 may not be used simultaneously; confirm chip support, but typically choose one to avoid conflicts.

Low-power design: watch GPIO pull-ups/downs to avoid leakage.

Antenna matching: follow the official reference design; do not alter antenna traces arbitrarily.

Firmware updates: use BLE OTA or 802.15.4 firmware push; reserve partitions.

中文

主控 / CPU

ESP32-H2-DevKitM

不上网，走蓝牙或 802.15.4。适合近场锁、灯、子节点。

主控 / CPU 无 Wi-Fi802.15.4 ESP32-H2

01 项目概述

ESP32-H2 是一颗不带 Wi-Fi 的无线 SoC，只保留 BLE 5 和 802.15.4（Thread/Zigbee）。它解决的是“近场、低功耗、不碰路由器”的产品需求。

典型场景：智能门锁、灯控、传感器子节点，需要挂到 Thread 或 Zigbee 网络里，但自身不直接上云。

上云路径交给旁边的网关（如带 Wi-Fi 的 C6 或 ESP32），本板只负责本地无线通信和逻辑控制。

它不是万能板：没有 Wi-Fi，不能直接跑 MQTT 或 HTTP 到云端；也不适合需要高速数据传输的应用。

开发板尺寸小，引脚按近场产品够用，适合做原型验证和最终产品核心。

02 项目硬件描述

  • 芯片： ESP32-H2，RISC-V 内核，支持 BLE 5 和 802.15.4。
  • 无线： BLE 5 + 802.15.4，无 Wi-Fi，注意天线区域净空。
  • USB： DevKit 下载口，用于烧录和调试。
  • 电源： 板上 USB 供电，具体电压范围见原理图。
  • 引出： 小尺寸，引脚按近场产品够用，具体丝印见板子。
  • 外设： 支持 GPIO、SPI、I2C、UART、ADC 等，具体引脚分配见原理图。
  • 注意： 不能直接抄 Wi-Fi Station / MQTT 示例；要配对网关。
  • 布局： 天线区域避免覆铜和走线，保证射频性能。

03 项目软件流程描述

ESP-IDF 目标选 ESP32-H2。没有 Wi-Fi，不要抄 Station / MQTT 直连云。

先 blink 确认下载和时钟，再初始化 BLE 或 802.15.4 协议栈。

BLE 模式：配置 GATT 服务，处理配对和连接事件，数据通过特征值收发。

802.15.4 模式：加入 Thread 或 Zigbee 网络，作为子节点，与网关通信。

上云路径放在网关侧，本板只负责本地无线和逻辑。

低功耗：使用 sleep 模式，定时唤醒或事件唤醒，注意 GPIO 配置。

脚号按本板丝印，不要照抄其他开发板。

04 项目核心点

产品不进路由器、只要手机或 802.15.4 时用 H2。必须自己上网，选 C3/C6/ESP32。

BLE 和 802.15.4 不能同时用？确认芯片支持，但通常二选一，避免冲突。

低功耗设计：注意 GPIO 上拉/下拉，避免漏电。

天线匹配：参考官方参考设计，不要随意改天线走线。

固件升级：通过 BLE OTA 或 802.15.4 固件推送，需预留分区。