MCU selection analysis
Documented evaluation of microcontroller options based on your requirements.
Custom embedded hardware engineered for your specific application, with the right balance of power, speed, and reliability built in from the first schematic.
Modern microcontrollers are remarkably capable devices, integrating processors, memory, peripherals, and analog functions into single chips. I work across the full range of embedded applications, from battery-powered IoT devices demanding ultra-low power to industrial controllers needing robust communication, wearables in compact form factors, and high-performance systems chasing maximum throughput. My experience spans major families including ARM Cortex-M (STM32, NXP, Nordic), ESP32 and ESP8266 for WiFi and Bluetooth, PIC and AVR for cost-sensitive designs, and application-specific processors for motor control and signal processing. A frequent focus is low-power sensor and data-logger design, where the sensing chain, storage, and duty cycle are budgeted so the product runs for months or years on a single battery or an energy-harvesting source. Much of this work is battery-powered device design where an ultra-low-power sleep budget, sometimes down to the sub-microamp range, decides whether the product lasts weeks or years on a charge.
Documented evaluation of microcontroller options based on your requirements.
Microcontroller circuit with proper power supply, reset, clock, and peripheral connections.
Debug and programming connections (SWD, JTAG, UART bootloader).
Interface circuits for sensors, displays, communication modules, and other peripherals.
Low-power design with appropriate sleep modes and wake sources.
ESD protection, reverse polarity protection, and I/O protection.
Pin assignments, peripheral configuration, and design notes for firmware development.
Crystal oscillator failures from improper loading capacitors or PCB layout.
Brown-out detection problems or noise-induced resets.
Battery life far shorter than expected due to improper sleep mode implementation.
Inadequate protection on I/O pins exposed to external connections.
Pin multiplexing issues preventing use of needed peripherals.
Missing or inaccessible programming and debug connections.
I define processing requirements, peripheral needs, power constraints, and cost targets, and identify any specific features required such as ADC resolution, communication interfaces, and security features.
I evaluate candidate microcontrollers against the requirements, considering availability, development ecosystem, and long-term support, and verify the pin count accommodates all peripheral needs.
I design the supporting circuitry: power supply, clock source, reset circuit, programming interface, and all peripheral connections, and plan pin assignments with PCB routing in mind.
I create detailed schematics following manufacturer recommendations, including all decoupling capacitors, pull-up and pull-down resistors, and protection components.
I review against manufacturer guidelines and application notes, verify power sequencing, reset behavior, and peripheral configuration, and prepare the design for PCB layout.
An electronics design engineer with 20+ years of professional experience across analog, digital, RF, and power designs, delivered to clients in 15+ countries. Your project is handled by the person who has shipped hardware like it, start to finish.
See the project portfolioCustom embedded hardware around microcontrollers for sensing, signal processing, control and connected products, with the right trade-off between power, speed and reliability.
Yes. If you already have a platform in mind, such as an ESP32 or an STM32, that is a useful constraint and I design the board around it. If not, I help choose one that fits the requirements.
I can deliver the hardware and the firmware as a package, or just the hardware and bring-up if the firmware is handled by your team.
Yes. I build and test the prototype so the hardware is proven before you scale it.
Yes. Low-power sensor and data-logger design is a frequent focus: choosing the sensing chain, sizing storage and the memory strategy, and budgeting sleep and duty cycle so the device runs for months or years on a single battery or an energy-harvesting source. The result is verified with real current measurements on the bench.
Yes. Battery-powered device design starts from the energy budget: the sensing chain, the sleep and wake duty cycle, and the quiescent draw of every rail are chosen so the board holds an ultra-low-power, sometimes sub-microamp, sleep current. That is what lets a low-power sensor or data logger run for months or years on a single cell or a harvested source.
From simple sensor nodes to complex control systems, I design microcontroller hardware for reliable operation and efficient firmware development. Send me the requirements and I will take it from there.
Start the Conversation