Hardware Guide

ESP32-C3 for People Counting with TensorFlow Lite Micro

The ESP32-C3 handles people counting effectively with TFLite Micro. 400 KB SRAM at 160 MHz provides 2.1x headroom over the 192 KB requirement for 200 KB models. Built-in Wi-Fi 802.11 b/g/n enables wireless result reporting.

Hardware Specs

Spec ESP32-C3
Processor Single-core RISC-V @ 160 MHz
SRAM 400 KB
Flash Up to 4 MB (external)
Key Features RISC-V architecture, Ultra-low cost, Hardware crypto acceleration
Connectivity Wi-Fi 802.11 b/g/n, Bluetooth 5.0 LE
Price Range $1 - $3 (chip), $4 - $10 (dev board)

Compatibility: Good

At 400 KB SRAM, the ESP32-C3 delivers 2.1x the 192 KB minimum needed for people counting. The 200 KB quantized model fits in the tensor arena with enough remaining capacity for input buffers and core application logic. More demanding features (multi-sensor fusion, large protocol stacks) may require careful allocation planning. For firmware and model storage, the 4 MB flash comfortably houses the TFLite Micro runtime, the 200 KB model binary, application firmware, and OTA update partitions for field upgrades. Flash usage is well within budget for this configuration. As a single-core RISC-V chip, the ESP32-C3 is cost-optimized ($1-3) for high-volume deployments. Its 400 KB SRAM handles most sensor-based ML models. No hardware ML acceleration, but the low power consumption makes it ideal for battery-powered edge nodes. People Counting requires camera input. The ESP32-C3 lacks native peripheral support for some of these sensors, requiring external interface circuitry. A camera interface (DVP/DCMI) is not available — SPI-based camera modules may work but with reduced frame rates. Evaluate whether the peripheral gap justifies an alternative MCU with native support. TFLite Micro's static memory allocation model maps well to the ESP32-C3's memory architecture — define a fixed tensor arena at compile time with no runtime heap fragmentation risk. The framework's operator coverage supports convolutional, depthwise-separable, and pooling layers needed for people counting. Model conversion uses the standard TFLite converter with int8 post-training quantization. At $1-3 per chip ($4-10 for dev boards), the ESP32-C3 is a reasonable investment for people counting deployments. 16 PlatformIO-listed boards provide decent hardware selection. Key ESP32-C3 features for this workload: RISC-V architecture, Ultra-low cost, Hardware crypto acceleration.

Getting Started

  1. 1

    Set up ESP32-C3 development environment

    Install ESP-IDF (recommended for production) or Arduino framework via PlatformIO. Create a project targeting the ESP32-C3 and verify basic functionality (blink LED, serial output). For TFLite Micro, clone the framework repository and add it as a library dependency. Ensure the toolchain supports C++11 or later for the ML runtime.

  2. 2

    Collect camera training data

    Connect a camera module (e.g., OV2640 via DVP/SPI) to the ESP32-C3. Write a data logging sketch that captures camera readings at the target sample rate and outputs via serial/SD card. Collect 1000+ labeled samples across all classes. Capture images at the model input resolution (96×96 or lower).

  3. 3

    Train and quantize model for TFLite Micro

    Build a quantized MobileNet-SSD or YOLO-Tiny in TensorFlow or PyTorch. Apply int8 post-training quantization — this typically reduces model size by 4x with minimal accuracy loss. Convert to .tflite and generate a C array (xxd -i model.tflite > model_data.h). Target model size: under 200 KB to fit the ESP32-C3's 400 KB SRAM with room for application code.

  4. 4

    Deploy and validate on ESP32-C3

    Include the TFLite Micro runtime and compiled model in your Espressif project. Allocate a tensor arena of 300-500 KB in a static buffer. Run inference on live camera data and compare predictions against your test set. Report results via MQTT or HTTP for remote validation. Measure inference latency and peak RAM usage to verify they meet application requirements.

Alternatives

STM32H7 with TFLite Micro

STMicroelectronics cortex-m7 at 480 MHz with 1024 KB SRAM. $8-20 per chip. Compared to ESP32-C3: more RAM, faster clock. Excellent rated.

ESP32-S3 with TFLite Micro

Espressif xtensa-lx7 at 240 MHz with 512 KB SRAM. $3-8 per chip. Excellent rated.

i.MX RT1062 with TFLite Micro

NXP cortex-m7 at 600 MHz with 1024 KB SRAM. $6-12 per chip. Compared to ESP32-C3: more RAM, faster clock. Excellent rated.

Explore More

More ESP32-C3 guides More People Counting guides All resources Find the right MCU

FAQ

How does ESP32-C3 report people counting results wirelessly?
The ESP32-C3's Wi-Fi transmits inference results via MQTT (lightweight, pub/sub), HTTP REST (simple integration), or WebSocket (real-time streaming). Send only classification results and confidence scores — not raw sensor data — to minimize bandwidth. The Wi-Fi stack requires a significant portion of RAM — consult the ESP-IDF documentation for exact memory requirements and account for this in your budget alongside the 200 KB model. ESP-IDF's esp_mqtt and esp_http_client libraries handle reconnection and TLS automatically.
How does ESP32-C3 report people counting results wirelessly?
The ESP32-C3's Wi-Fi transmits inference results via MQTT (lightweight, pub/sub), HTTP REST (simple integration), or WebSocket (real-time streaming). Send only classification results and confidence scores — not raw sensor data — to minimize bandwidth. The Wi-Fi stack requires a significant portion of RAM — consult the ESP-IDF documentation for exact memory requirements and account for this in your budget alongside the 200 KB model. ESP-IDF's esp_mqtt and esp_http_client libraries handle reconnection and TLS automatically.
How does ESP32-C3 report people counting results wirelessly?
The ESP32-C3's Wi-Fi transmits inference results via MQTT (lightweight, pub/sub), HTTP REST (simple integration), or WebSocket (real-time streaming). Send only classification results and confidence scores — not raw sensor data — to minimize bandwidth. The Wi-Fi stack requires a significant portion of RAM — consult the ESP-IDF documentation for exact memory requirements and account for this in your budget alongside the 200 KB model. ESP-IDF's esp_mqtt and esp_http_client libraries handle reconnection and TLS automatically.

Build Vision AI Pipelines in ForestHub

Connect cameras to on-device inference — design detection workflows visually and compile to optimized firmware.

Get Started Free