Microcontroller (MCU)
A whole computer on one die: CPU core, flash, RAM, and peripherals in a single package, running firmware directly with no operating system underneath it — or a small RTOS at most. The low end of the embedded-systems spectrum, measured in kilobytes and milliwatts.
Integration is the competition
Nuvoton’s NSC128L42 is the clean example: an Arm Cortex-M23 core is the least interesting thing about it, and what the vendor is selling is the 24-bit sigma-delta ADC, analog front end, LCD driver and Class-D amplifier on the same die. The argument is component count — one part instead of an MCU plus a precision ADC plus a discrete amp — which decides board area and bill of materials in exactly the products that can’t afford either.
So at this end of the field, “faster” is rarely the pitch. What analog did the die swallow is, and mixed-signal integration is where a metrology-grade part distinguishes itself from a commodity one.
Arm Cortex-M as the substrate
Cortex-M is the common core across most of the category (M23 in the Nuvoton part), which means the differentiation lives in peripherals rather than instruction sets, and the toolchain is broadly shared. The exceptions in awesome-iot‘s hardware list are the wireless-first parts — ESP32/ESP8266 (Espressif, Xtensa or RISC-V, Wi-Fi and Bluetooth integrated — paged in full at esp32) and the RP2040/Pico — where the radio or the price, not the analog, is the integration story. Paged in full at raspberry-pi-pico (2026-08-08), whose RP2350 generation adds the odd property of booting either Arm Cortex-M33 or Hazard3 RISC-V cores from the same silicon.
The MCU board
Between a bare chip and an SBC sits the development board: an MCU with power regulation, a USB connector, and headers. Arduino, the Pico, and the ESP32 modules are all this, and it’s the layer most projects actually build on — The Open Book is a Pico plus a display plus a custom PCB. The chip is the subject of a datasheet; the board is what people design with.
The part is not the product
The board layer is also where the corpus’s one commercial claim sits, and it is worth naming as a claim rather than a finding. microcontroller-side-business argues that “it’s never the chip that sells, it’s the object you hide it inside” — margin comes from integration and presentation, and the design rule offered is to give the MCU exactly one job.
That rhymes with the integration argument above, which is why it is linked here. It is also a T4 paywalled stub with nothing behind it: no prices, no revenues, no unit costs, and no evidence that anyone built a business this way. Treat it as a framing the corpus has heard once, not as support for the integration thesis, which stands on the datasheets instead.
Related
embedded-systems · single-board-computer · nuvoton-nsc128l42-mcu · the-open-book-ereader · awesome-iot · microcontroller-side-business · synthesis