Platform Expertise

    Deep experience with ESP32, STM32, and Raspberry Pi Pico

    Choosing the right microcontroller can make or break a product. I work across the ESP32 family, STM32 series, and Raspberry Pi Pico — selecting the optimal platform for each project's power, performance, connectivity, and cost requirements.

    Raspberry Pi PicoESP32 familySTM32 seriesArduino ecosystemFreeRTOSPlatform migration

    ESP32 Family

    The ESP32 line (including ESP32-S3, ESP32-C3, ESP32-C6) is my go-to for WiFi and Bluetooth-enabled products. I use ESP-IDF for production firmware, leveraging dual-core task partitioning, hardware crypto, and RTC deep-sleep modes. For projects requiring video, I've implemented camera interfaces and RTMP streaming on the ESP32-S3.

    • ESP32, ESP32-S3, ESP32-C3, ESP32-C6 variants
    • ESP-IDF and ESP-ADF frameworks
    • WiFi + BLE dual-stack connectivity
    • Camera, audio, and display peripherals on ESP32-S3
    • Deep-sleep power optimization for battery products

    STM32 Series

    For projects demanding raw processing power, hardware DSP, or advanced peripherals (DCMI, LTDC, Ethernet MAC), the STM32 family is the right tool. I've worked with STM32F4, STM32H7 (dual-core), and STM32L4 (ultra-low-power) — using STM32CubeMX for peripheral configuration and bare HAL or FreeRTOS for application logic.

    • STM32F4, STM32H7 (dual-core Cortex-M7+M4), STM32L4
    • STM32CubeIDE / CubeMX for peripheral configuration
    • DCMI camera interface and DMA2D graphics acceleration
    • LTDC display controller with LVGL UI framework
    • Ethernet and USB host/device stacks

    Raspberry Pi Pico (RP2040)

    The RP2040 offers an excellent price-to-performance ratio with dual Cortex-M0+ cores, PIO state machines, and a clean C SDK. I use it for industrial controllers, sensor hubs, and cost-sensitive IoT devices — often paired with external modems (SIM7020, SIM7060) for cellular connectivity.

    • Pico SDK in C/C++ for production firmware
    • PIO (Programmable I/O) for custom protocols and LED driving
    • Dual-core task partitioning for parallel workloads
    • USB device and host capabilities
    • MicroPython for rapid prototyping on RP2040

    Platform Migration & Selection

    Existing product stuck on an expensive or discontinued MCU? I handle platform migrations — porting firmware, adapting peripheral drivers, and re-validating hardware. For new projects, I evaluate BOM cost, power budget, peripheral needs, and connectivity to recommend the best-fit platform before any code is written.

    • MCU selection based on power, cost, peripherals, and availability
    • Firmware porting between ESP32, STM32, and RP2040 families
    • Peripheral driver abstraction for multi-platform support
    • Arduino-to-production SDK migration (ESP-IDF, Pico SDK, STM32 HAL)

    Tools & Technologies

    ESP-IDF / ESP-ADF
    Pico SDK
    STM32CubeIDE
    FreeRTOS
    Arduino IDE (prototyping)
    PlatformIO
    OpenOCD / pyOCD debuggers

    Frequently Asked Questions

    Which MCU should I use for my product?

    It depends on your connectivity needs, power budget, processing requirements, and target cost. ESP32 is ideal for WiFi/BLE products; STM32H7 for high-performance vision or industrial systems; RP2040 for cost-sensitive controllers. I'll recommend the best fit during the initial consultation.

    Can you migrate my Arduino prototype to a production SDK?

    Yes. I regularly migrate Arduino-based prototypes to ESP-IDF, Pico SDK, or STM32 HAL — gaining better performance, lower power consumption, and production-grade reliability.

    Do you work with other MCU families?

    My core expertise is ESP32, STM32, and RP2040. For other platforms (nRF52, SAMD, PIC), I evaluate on a per-project basis. The firmware patterns and hardware design principles transfer across families.

    Need platform expertise for your project?

    Let's discuss your requirements and find the best approach for your hardware project.