Hardware Guide
STM32H7 for Anomaly Detection with TensorFlow Lite Micro
The STM32H7 is an excellent match for anomaly detection with TFLite Micro. 1024 KB SRAM delivers 32.0x the 32 KB minimum while 480 MHz processes 15 KB models in real time. DSP extensions and double-precision FPU accelerate inference.
Published 2026-04-02
Hardware Specs
| Spec | STM32H7 |
|---|---|
| Processor | ARM Cortex-M7 @ 480 MHz |
| SRAM | 1024 KB |
| Flash | 2 MB |
| Key Features | Double-precision FPU, L1 cache (16 KB I + 16 KB D), JPEG codec, Chrom-ART Accelerator (DMA2D) |
| Connectivity | Ethernet, USB OTG HS/FS |
| Price Range | $8 - $20 (chip), $30 - $80 (dev board) |
Compatibility:
At 1024 KB SRAM, the STM32H7 provides 32.0x the 32 KB minimum for anomaly detection. This generous headroom means the 15 KB model tensor arena, sensor input buffers, and application logic (vibration/current/temperature polling, Ethernet stack, state management) all fit without contention. The remaining 986 KB after model allocation supports complex application features. Flash storage at 2 MB comfortably houses the TFLite Micro runtime, the 15 KB model binary, application firmware, and OTA update partitions for field upgrades. Flash usage is well within budget for this configuration. The STM32H7 at 480 MHz with double-precision FPU and ART accelerator is among the highest-performance Cortex-M MCUs in ST's lineup. Its 1 MB SRAM accommodates models that smaller MCUs cannot fit in memory. Dual-bank flash enables safe OTA firmware updates during operation. For anomaly detection, connect a vibration sensor (e.g., ADXL345 accelerometer via I2C/SPI) via SPI and a current sensor (e.g., ACS712 via ADC) via ADC and a temperature sensor (e.g., DS18B20 or TMP36 via ADC) via ADC to the STM32H7. Sample at 50-200 Hz and collect windows of 64-256 samples as model input. The DSP extensions efficiently compute FFT features from raw sensor data. TFLite Micro's static memory allocation model maps well to the STM32H7's memory architecture — define a fixed tensor arena at compile time with no runtime heap fragmentation risk. The framework's operator coverage supports dense and convolutional layers needed for anomaly detection. Model conversion uses the standard TFLite converter with int8 post-training quantization. At $8-20 per chip ($30-80 for dev boards), the STM32H7 offers strong value for anomaly detection deployments. 22 PlatformIO-listed boards provide decent hardware selection. Key STM32H7 features for this workload: Double-precision FPU, L1 cache (16 KB I + 16 KB D), JPEG codec, Chrom-ART Accelerator (DMA2D).
Getting Started
- 1
Set up STM32H7 development environment
Install STM32CubeIDE with the latest STM32Cube firmware package. Create a project targeting the STM32H7 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
Collect vibration training data
Connect a vibration sensor (e.g., ADXL345 accelerometer via I2C/SPI) and current sensor (e.g., ACS712 via ADC) and temperature sensor (e.g., DS18B20 or TMP36 via ADC) to the STM32H7 via I2C. Write a data logging sketch that captures vibration readings at the target sample rate and outputs via serial/SD card. Collect 500+ labeled samples across all classes. Include normal operating conditions and edge cases in your dataset.
- 3
Train and quantize model for TFLite Micro
Build an autoencoder (3-4 dense layers) 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 15 KB to fit the STM32H7's 1024 KB SRAM with room for application code.
- 4
Deploy and validate on STM32H7
Include the TFLite Micro runtime and compiled model in your STMicroelectronics project. Allocate a tensor arena of 23-38 KB in a static buffer. Run inference on live vibration data and compare predictions against your test set. Log results to serial for desktop validation. Measure inference latency and peak RAM usage to verify they meet application requirements.
Alternatives
i.MX RT1062 with TFLite Micro
NXP cortex-m7 at 600 MHz with 1024 KB SRAM. $6-12 per chip. Compared to STM32H7: cheaper. Excellent rated.
ESP32-S3 with TFLite Micro
Espressif xtensa-lx7 at 240 MHz with 512 KB SRAM. $3-8 per chip. Compared to STM32H7: less RAM but lower cost, cheaper. Excellent rated.
nRF52840 with TFLite Micro
Nordic Semiconductor cortex-m4f at 64 MHz with 256 KB SRAM. $5-8 per chip. Compared to STM32H7: less RAM but lower cost, cheaper. Excellent rated.
Compare Hardware for Anomaly Detection
Explore More
FAQ
- What is the power consumption for anomaly detection on STM32H7?
- Power consumption during inference depends on clock configuration, active peripherals, and duty cycle. Consult the STM32H7 datasheet for detailed power profiles at 480 MHz. For battery-powered anomaly detection, use duty cycling: run inference at intervals and enter low-power sleep mode between cycles. Profile your specific workload to estimate battery life accurately.
- What vibration sampling rate does STM32H7 support for anomaly detection?
- The STM32H7 can sample accelerometers at 10+ kHz via SPI (faster) or ADC. For anomaly detection, 50-200 Hz is typically sufficient. Collect windows of 64-256 samples for gesture/motion classification. The STM32H7's DSP instructions compute FFT efficiently in firmware.
- How do I update the anomaly detection model on STM32H7 in production?
- Without wireless connectivity, model updates require physical access via USB/JTAG. For field deployments, consider adding a wireless module or using an MCU with built-in connectivity. Always validate model integrity with a checksum before switching to the new version.
Orchestrate Anomaly Detection with ForestHub
Sensors and devices flag anomalies; ForestHub on the Linux edge gateway correlates them over MQTT/Modbus/OPC-UA and acts on the line as a deterministic, auditable graph.
Get Started Free