Back to Home

Microcontrollers for GPS gadget

The article analyzes microcontrollers for wearable GPS gadget: STM32H743, Renesas RA8, NXP i.MX RT1176. Considers RAM, cryptography, NPU, RTOS. Recommendations for choosing for prototype with JLCPCB.

Assembling a sports tracker: MCU analysis
Advertisement 728x90

Choosing a Microcontroller for a Wearable GPS Gadget

Developing a wearable device for sports tracking requires a compact form factor with autonomous power, a GNSS module, IMU sensors, Wi-Fi/BLE, and a high-contrast display. Key characteristics include minimal power consumption, water resistance, and support for an RTOS to handle telemetry data processing, GUI, and network stacks. The architecture assumes external radio modules like the u-blox MAYA-W276-00B or ESP32-C6-MINI-1U-N4 via SDIO, a GNSS ATGM332D-5N-7X with BeiDou reception, and a hardware cryptographic processor for TLS 1.2+ (RSA-2048/3072, ECC).

The microcontroller must provide real-time processing of IMU algorithms (Madgwick, Kalman), GNSS correction (particle filters), a file system on SD/SPI Flash, OTA updates, and edge AI. Minimum specifications:

  • RAM ≥ 640 KB for the BLE stack (NimBLE), NetX Duo, RTOS, and buffers.
  • Flash ≥ 1 MB for firmware, GUI resources, and certificates.
  • Frequency ≥ 200 MHz.
  • 2× SDIO host (radio + SD card).
  • QFP package for prototyping.
  • Hardware cryptography (AES, SHA, RSA/ECC, TRNG).

Comparing MCU Families

STM32H743

Cortex-M7 @ 480 MHz, 2 MB Flash, 1 MB RAM (non-contiguous blocks). Supports 2× SDMMC, Ethernet, USB HS, CRYP (AES-256, SHA-256), TRNG. Ecosystem includes STM32CubeIDE/CubeMX with HAL, FreeRTOS, Azure RTOS (ThreadX/NetX), FatFS, LwIP. Debugging via ST-LINK/V3. A mature solution with a large community, but the core is from 2014 and lacks Helium.

Google AdInline article slot

STM32N657

Cortex-M55 @ 800 MHz (Helium MVE, TrustZone), 4.2 MB of contiguous RAM, ST Neural-ART NPU (600 GOPS). No built-in Flash (requires OSPI/Hexa-SPI), BGA only. Peripherals: 2× SDMMC, H.264 codec, NeoChrom GPU, SAES/PKA (RSA-4096, ECC). STM32Cube.AI for ML models. Suitable for AI inference but complicates the BOM.

Renesas RA8M1

Cortex-M85 @ 480 MHz (Helium, TrustZone), 2 MB Flash, 1 MB RAM. LQFP-144 for manual soldering, SDRAM controller, 2× SDIO, RSIP-E51A (RSA-4096, ECC). FSP with FreeRTOS, Azure RTOS (NetX Secure with TLS acceleration). e² studio, RA Smart Configurator. A balance of price and novelty for DSP/ML.

Renesas RA8P1

Cortex-M85 @ 1 GHz + Ethos-U55 NPU, 1 MB Flash, 2 MB SRAM. BGA only, Gigabit Ethernet, SDRAM controller. Shared ecosystem with RA8M1. Ideal for high-load tasks with AI.

Google AdInline article slot

NXP i.MX RT1176

Dual-core: Cortex-M7 @ 1 GHz + M4 @ 400 MHz, 2 MB RAM, no Flash (QSPI). BGA-289, CAAM (RSA-4096), 2× Ethernet. MCUXpresso SDK with FreeRTOS, Linux support. High performance but requires external memory.

GigaDevice GD32H759

Cortex-M7 @ 600 MHz, 3.5 MB Flash, 1 MB RAM, LQFP176. 2× SDIO. An STM32H7 clone with improved memory, an affordable alternative.

Selection Criteria for Prototyping

Selection depends on the development stage:

Google AdInline article slot
  • Prototyping: Prefer QFP packages (STM32H743, RA8M1, GD32H759) for manual soldering.
  • Production: BGA with NPU (STM32N657, RA8P1) for AI features (activity recognition, self-learning).
  • Energy Efficiency: Helium (M85/M55) accelerates IMU/GNSS filters by 4x.
  • Security: RSIP-E51A/CAAM minimize CPU load during TLS handshake.
  • Ecosystem: STM32 leads in middleware, Renesas in TLS integration.

For a garage budget, JLCPCB is optimal: assembly of boards with these MCUs.

Key Takeaways

  • Radio Independence: External modules via SDIO extend lifecycle.
  • Helium MVE: Accelerates DSP/ML for real-time telemetry processing.
  • Hardware Crypto: Essential for OTA, cloud services (AWS IoT, Azure).
  • RTOS Stack: ThreadX/NetX Duo with GUI, file systems, and network protocols.
  • NPU for Edge AI: STM32N657/RA8P1 enable local activity analysis without the cloud.

— Editorial Team

Advertisement 728x90

Read Next