Joins newer routers, and can head toward Thread or Zigbee.
CPU / main boardsWi-Fi 6802.15.4ESP32-C6
01 Overview
The ESP32-C6 is Espressif's first RISC-V MCU with Wi-Fi 6, also integrating BLE 5 and 802.15.4 (Thread/Zigbee). It solves the problem of older devices dropping off new Wi-Fi 6 routers and the need for two chips in a multi-protocol gateway.
Typical use cases: smart appliances that must reliably join a Wi-Fi 6 LAN, or as the control core of a Thread/Zigbee border router, speaking IP on one side and managing low-power sensor networks on the other.
It is not a simple upgrade of the C3; it is designed for multi-protocol coexistence. If your product only needs legacy Wi-Fi 4/5 and cost is tight, the C3 is a better fit. If the site is already Wi-Fi 6 or the roadmap includes Thread/Zigbee, the C6 is the right choice.
The DevKitC board breaks out standard pin headers and includes a USB-UART for flashing, making it good for rapid prototyping. But note: enabling multiple radios simultaneously significantly increases antenna and RF front-end design complexity.
For certification, Wi-Fi 6, BLE, and 802.15.4 must be evaluated together, not one at a time, to avoid costly late-stage fixes.
02 Hardware
Chip: ESP32-C6 (RISC-V, single-core 160 MHz)
Radio: Wi-Fi 6 (2.4 GHz), BLE 5, 802.15.4 (Thread/Zigbee)
USB: USB-UART on typical DevKits (e.g., CP2102 or similar) for flashing and logs
I/O: standard pin headers, GPIO at 3.3 V, mind default states on some pins
Antenna: onboard PCB antenna or IPEX connector; layout is picky on Wi-Fi 6, follow the reference design strictly
Power: 3.3 V supply, mind current peaks, add decoupling capacitors
Watch: for multi-radio coexistence, antenna matching and isolation must be validated separately; do not copy a single-radio design
03 Software flow
1. Install ESP-IDF, set target to esp32c6, and first flash hello_world to confirm flashing and logging work.
2. Run a Wi-Fi example (e.g., station) alone to verify stable connection to a Wi-Fi 6 router; log RSSI and reconnect behavior.
3. Run a Thread or Zigbee example (e.g., OpenThread) alone to confirm 802.15.4 RF TX/RX works.
4. Do not enable Wi-Fi 6, BLE, and 802.15.4 together in an unplanned project; validate each radio individually first, then consider coexistence.
5. If RF tests fail, check antenna layout and matching before blaming the protocol stack.
6. Before certification, run multi-radio concurrent stress tests on final hardware to ensure coexistence performance meets specs.
04 Core points
Use C6 when the site is Wi-Fi 6 or the roadmap includes Thread/Zigbee. For an old AP and a low price, C3 is enough.
Enabling multiple radios increases memory and CPU usage; plan task stacks and heap size early.
Antenna layout is picky on Wi-Fi 6; do not copy the C3 reference design, re-layout per C6 RF guidelines.
Certify the radios together, not one protocol in isolation, to avoid costly rework.
802.15.4 and Wi-Fi share the 2.4 GHz band; plan coexistence strategies (e.g., time-slicing) in advance.