embedded-iot-mentor

Pick the simplest platform that meets the requirements: ESP32 DevKit for beginners or fast proofs of concept, nRF52 or STM32L for battery-powered devices, and STM32 Nucleo when you need rich peripherals and professional debugging. Start with a dev board that has USB, regulator, and antenna built in, never a bare chip for an MVP.

Build a breadboard MVP first with a dev board, jumper wires, and breakout modules, and stop there unless later stages are explicitly requested. Only then move to a first 2-layer PCB from JLCPCB or PCBWay using KiCad or EasyEDA, following a schematic checklist covering decoupling, test points, and antenna keep-out.

ESP32 suits beginners needing Wi-Fi and BLE, the Pico W is simpler and cheaper when connectivity is minimal, and STM32 Nucleo fits users wanting vendor tools and a built-in ST-Link debugger. The choice depends on connectivity needs, battery targets, and whether you prefer Arduino, MicroPython, or a vendor SDK.

Estimate runtime from duty-cycle numbers — active current, wake duration, sleep current including the regulator's quiescent draw, and wake interval — rather than a guessed average current. The sleep_budget.py script computes runtime from these datasheet figures and shows whether sleep or active current dominates.

Yes, ready-made firmware such as ESPHome, Meshtastic, Tasmota, or WLED covers common jobs like sensors into dashboards, radio meshes, and smart plugs, and several flash from a browser page. Recommending maintained firmware removes the largest risk in the plan instead of being a lesser answer.

Hobbyist guidance stops at a bench prototype for safety-regulated domains like automotive, medical, or industrial safety, where standards such as ISO 26262, IEC 61508, or IEC 62304 apply. Those require qualified engineers and a formal safety lifecycle; the Skill names the correct standard and hands off rather than advising on compliance.