ESP32-H2-MINI-1 carrier PCB: design, layout, and gate checks

A dependable carrier for the ESP32-H2-MINI-1 starts by treating it as a specific surface-mount module, not as an interchangeable member of the ESP32-H2 family. This version is built around ESP32-H2, uses 32-bit RISC-V, and occupies 13.2 × 16.6 × 2.4 mm. Its physical implementation is 53-pad compact castellated module with PCB antenna. Those details determine the land pattern, carrier outline, programming access, antenna or connector clearance, and which signals are genuinely available after the module maker has used its own pins.

H2-MINI-1 is a compact 802.15.4/BLE module with no Wi-Fi, intended for Thread, Zigbee, and low-power mesh endpoints.

Typical reasons to choose it include Thread and Zigbee endpoints and Matter sensors using a border router. The useful comparison is therefore not merely processor speed: it is whether the exact memory, radio, connector, power path, exposed I/O, and mechanical envelope match the product that will be built. The row below is the integration baseline that should agree with the schematic, footprint, BOM, assembly drawing, and firmware target.

The carrier power tree must satisfy 3.0–3.6 V while every external signal respects 3.3 V; GPIO is not 5 V tolerant. These are separate checks. A board can accept USB or VIN at one connector while its GPIO remains strictly 3.3 V, and an onboard regulator can be safe at idle yet lose regulation during a radio, display, motor, or memory-current burst. Document which source owns each rail, what happens when USB and carrier power are both present, and where bulk and high-frequency decoupling close the current loop.

Keep the 2.4 GHz antenna clear, route H2 USB GPIO26/27 as a pair when used, and expose commissioning plus production-programming controls.

• The H2 is a 2.4 GHz 802.15.4 and BLE device, not a Wi-Fi part. Preserve the module antenna keepout and plan the product's Thread, Zigbee, or Matter topology without assuming a direct Wi-Fi link.
• Provide a stable 3.3 V rail, CHIP_EN pull-up and reset timing, boot access, and a short native-USB path when USB Serial/JTAG is used for provisioning or test.

Route from a verified pin table rather than a reseller graphic. In particular, treat H2 straps, USB Serial/JTAG GPIO26/27, dense pads and antenna keepoutas design constraints that must survive schematic capture, footprint numbering, layout, production programming, and enclosure assembly. Mark orientation on copper or silkscreen, retain recovery/debug access, and make every antenna, cable, card, switch, or connector operable after the carrier is fully populated—not only while it is open on a bench.

A generic DRC run cannot know that a technically connected pin is the wrong boot strap, that a development-board header was mirrored, or that copper under an antenna will ruin range. The useful release check combines KiCad connectivity and fabrication rules with the product-specific conditions below. Each item should be supported by the selected module datasheet, hardware guide, board schematic, or mechanical drawing—not by a footprint name alone.

1. Check module land pattern, antenna option, all-layer RF keepout, exposed ground pads, and the exact flash ordering code.
2. Check CHIP_EN, strapping pins, 3.3 V decoupling, USB polarity and CC resistors, and the chosen production-programming connection.
3. Confirm no schematic or BOM claim depends on Wi-Fi, because ESP32-H2 provides 802.15.4 and Bluetooth LE instead.
4. For ESP32-H2-MINI-1, verify USB GPIO26/27, H2 straps, 802.15.4 antenna clearance, and that the system includes any required border-router path.

After those checks, refill every copper zone, run ERC and DRC from the same revision used to generate fabrication data, and inspect the actual Gerbers, drill file, BOM, and placement output. Confirm that the module ordering code in the BOM matches the memory and radio assumptions in firmware. A carrier is not release-ready when its prototype happens to boot; it is ready when the exact build configuration can be reproduced and inspected.

These failures recur because family names conceal physical and electrical differences. For this particular integration, watch for the following concrete mistakes:

• Copying C6 requirements can create an impossible expectation that the H2 joins a Wi-Fi network directly.
• Selecting H2 as a drop-in Wi-Fi replacement for C3 or C6 even though its radio feature set is different.
• Putting ground, a battery, or enclosure metal beneath the antenna area and erasing the benefit of the certified module.

Sourcing note. Specify flash and antenna suffixes and validate the module's Thread/Zigbee certification path for the intended ecosystem. Record the complete manufacturer code, approved alternates, module or board revision, antenna and cable when applicable, memory population, and the firmware build that was tested. If a substitute changes any of those facts, reopen the footprint, power, pinout, radio, and production-programming review instead of treating it as a purchasing-only change.