armhub.dev
Systems · 16 pages
Systems

System designs — overview

How real products are actually built — block-level walkthroughs of seven everyday embedded systems, from Wi-Fi routers to flight controllers.

1 min read · 240 wordsupdated · May 12, 2026

The rest of armhub treats topics one at a time: a peripheral, a core, an RTOS. This section flips that orientation — we pick a finished product and walk it backwards into the silicon and firmware that make it work.

The goal is grounded. When you read about Cortex-A53, you can come here to see one of the millions of devices it actually ships in. When you read about hard real-time, you can see why a drone flight controller picks one core architecture over another.

What each page covers

  • At-a-glance specs — chip class, RAM/flash, OS, peripherals, certifications.
  • Block diagram — the silicon you'd see if you decap'd the SoC.
  • What the cores do — every CPU/coprocessor and what it owns.
  • Software stack — bootloader, OS/RTOS, key middleware.
  • The hard parts — failure modes, certifications, non-obvious tradeoffs.
  • Real products — concrete examples you can buy and tear down.

The seven devices

How to read these

Each page assumes you've read the relevant background pages — but you can absolutely jump straight in. Cross-references are everywhere, and you'll often find that one device touches half the rest of the site: a Wi-Fi router uses Cortex-A, Linux boot flow, DMA, USB, and vendor SoCs.

A flight controller touches Cortex-M7, SPI, I²C, DMA cache coherency, Rust on Cortex-M, FreeRTOS, and linker scripts for ITCM placement.

That's the point of this section — to make the rest of the site useful in context.