Hardware Guide
i.MX RT1062 for Image Classification with TensorFlow Lite Micro
The i.MX RT1062 is an excellent match for image classification with TFLite Micro. 1024 KB SRAM delivers 8.0x the 128 KB minimum while 600 MHz processes 150 KB models in real time. DSP extensions and double-precision FPU accelerate inference.
Published 2026-04-02
Hardware Specs
| Spec | i.MX RT1062 |
|---|---|
| Processor | ARM Cortex-M7 @ 600 MHz |
| SRAM | 1024 KB |
| Flash | Up to 8 MB (external) |
| Key Features | Crossover MCU (600 MHz Cortex-M7), 1 MB on-chip SRAM (double of RT1052), L1 cache (32 KB I + 32 KB D), FlexRAM (configurable ITCM/DTCM/OCRAM), No on-chip flash (external QSPI/HyperFlash) |
| Connectivity | Ethernet, USB OTG HS/FS |
| Price Range | $6 - $12 (chip), $25 - $40 (dev board) |
Compatibility:
With 1024 KB of internal SRAM, the i.MX RT1062 provides 8.0x the 128 KB minimum for image classification. This generous headroom means the 150 KB model tensor arena, sensor input buffers, and application logic (camera polling, Ethernet stack, state management) all fit without contention. The remaining 649 KB after model allocation supports complex application features. The i.MX RT1062 provides 8 MB of flash memory, which comfortably houses the TFLite Micro runtime, the 150 KB model binary, application firmware, and OTA update partitions for field upgrades. Flash usage is well within budget for this configuration. The i.MX RT1062 runs at 600 MHz on a Cortex-M7 core, placing it among the higher-performance MCU options for ML inference. Its 1 MB SRAM and external memory interface support larger models including small vision networks. NXP's eIQ ML software provides optimized kernels for the RT series. Image Classification requires camera input. The i.MX RT1062 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 i.MX RT1062'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 image classification. Model conversion uses the standard TFLite converter with int8 post-training quantization. At $6-12 per chip ($25-40 for dev boards), the i.MX RT1062 offers strong value for image classification deployments. Key i.MX RT1062 features for this workload: Crossover MCU (600 MHz Cortex-M7), 1 MB on-chip SRAM (double of RT1052), L1 cache (32 KB I + 32 KB D), FlexRAM (configurable ITCM/DTCM/OCRAM), No on-chip flash (external QSPI/HyperFlash).
Getting Started
- 1
Set up i.MX RT1062 development environment
Install MCUXpresso IDE with the MCUXpresso SDK. Create a project targeting the i.MX RT1062 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 camera training data
Connect a camera module (e.g., OV2640 via DVP/SPI) to the i.MX RT1062. 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
Train and quantize model for TFLite Micro
Build a quantized MobileNetV2 or EfficientNet-Lite 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 150 KB to fit the i.MX RT1062's 1024 KB SRAM with room for application code.
- 4
Deploy and validate on i.MX RT1062
Include the TFLite Micro runtime and compiled model in your NXP project. Allocate a tensor arena of 225-375 KB in a static buffer. Run inference on live camera 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
STM32H7 with TFLite Micro
STMicroelectronics cortex-m7 at 480 MHz with 1024 KB SRAM. $8-20 per chip. Excellent rated.
ESP32-S3 with TFLite Micro
Espressif xtensa-lx7 at 240 MHz with 512 KB SRAM. $3-8 per chip. Compared to i.MX RT1062: less RAM but lower cost, cheaper. Excellent rated.
STM32F7 with TFLite Micro
STMicroelectronics cortex-m7 at 216 MHz with 512 KB SRAM. $8-15 per chip. Compared to i.MX RT1062: less RAM but lower cost. Excellent rated.
Compare Hardware for Image Classification
Explore More
FAQ
- Why choose TFLite Micro over other frameworks for i.MX RT1062?
- TFLite Micro has the widest operator coverage and largest community for cortex-m7 targets. It supports int8 and float32 models with a static memory allocation model that eliminates heap fragmentation. The i.MX RT1062's 1024 KB SRAM works well with TFLite Micro's predictable memory usage. Alternative: Edge Impulse wraps TFLite Micro with a simpler workflow if you prefer cloud-based training.
- Can i.MX RT1062 run image classification inference in real time?
- The i.MX RT1062 runs at 600 MHz with DSP acceleration. Whether this enables real-time image classification depends on your specific model architecture and acceptable latency. A 150 KB int8 model is a reasonable target for this hardware class. Larger models may require duty-cycled inference or model optimization (pruning, distillation). Benchmark your specific model on hardware to validate timing.
- What is the power consumption for image classification on i.MX RT1062?
- Power consumption during inference depends on clock configuration, active peripherals, and duty cycle. Consult the i.MX RT1062 datasheet for detailed power profiles at 600 MHz. For battery-powered image classification, use duty cycling: run inference at intervals and enter low-power sleep mode between cycles. Profile your specific workload to estimate battery life accurately.
Orchestrate Image Classification with ForestHub
Your device classifies on-device; ForestHub on the Linux edge gateway collects results over MQTT/Modbus, reasons across the fleet, and triggers actions as an inspectable graph.
Get Started Free