Hardware Guide

i.MX RT1062 for Object Detection with CMSIS-NN

The i.MX RT1062 is an excellent match for object detection with CMSIS-NN. 1024 KB SRAM delivers 4.0x the 256 KB minimum while 600 MHz processes 250 KB models in real time. DSP extensions and double-precision FPU accelerate inference.

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: Excellent

With 1024 KB of internal SRAM, the i.MX RT1062 provides 4.0x the 256 KB minimum for object detection. This generous headroom means the 250 KB model tensor arena, sensor input buffers, and application logic (camera polling, Ethernet stack, state management) all fit without contention. The remaining 399 KB after model allocation supports complex application features. Flash storage at 8 MB comfortably houses the CMSIS-NN runtime, the 250 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. Object Detection 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. CMSIS-NN provides ARM-optimized neural network kernels that leverage the i.MX RT1062's DSP instructions and floating-point unit for maximum inference throughput on Cortex-M. The kernels are hand-optimized in assembly for critical operations (Conv2D, DepthwiseConv2D, FullyConnected). Combine with TFLite Micro's CMSIS-NN delegate for the best performance on ARM targets. At $6-12 per chip ($25-40 for dev boards), the i.MX RT1062 offers strong value for object detection 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. 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 CMSIS-NN, 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 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. 3

    Train model and prepare for CMSIS-NN deployment

    Train a quantized MobileNet-SSD or YOLO-Tiny in TensorFlow/Keras. Apply int8 post-training quantization via the TFLite converter — this is essential for CMSIS-NN's optimized kernels. The quantized model should be under 250 KB. Use tflite_micro's CMSIS-NN delegate to automatically route operations to optimized ARM kernels on the i.MX RT1062's cortex-m7 core.

  4. 4

    Deploy and validate on i.MX RT1062

    Include the CMSIS-NN runtime and compiled model in your NXP project. Allocate a tensor arena of 375-625 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

Explore More

FAQ

What camera resolution works for object detection on i.MX RT1062?
On-device object detection models typically use 96×96 or 128×128 pixel grayscale input. The i.MX RT1062's 1024 KB SRAM constrains this: a 96×96 grayscale frame is ~9 KB, while 128×128 RGB would need ~49 KB. Without a native camera interface, use an SPI camera module (e.g., ArduCAM Mini) with reduced frame rates. Always downsample in firmware before inference.
How do I update the object detection model on i.MX RT1062 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.
What size object detection model fits on i.MX RT1062?
The i.MX RT1062 has 1024 KB SRAM and 8 MB flash. A typical object detection model is 250 KB after int8 quantization. The tensor arena needs 375-500 KB at runtime. After model allocation, approximately 524 KB remains for application logic, sensor drivers, and Ethernet stack.

Build Vision AI Pipelines in ForestHub

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

Get Started Free