Bare-Metal, RTOS, or Embedded Linux
Use the simplest platform that meets the product’s timing, interface, and power needs. Bare-metal suits single-purpose devices, an RTOS suits a microcontroller juggling several jobs with deadlines, and embedded Linux suits products that need a camera pipeline, a rich display, or large software libraries. PDE builds on all three, including FreeRTOS, ThreadX, and Zephyr, and helps choose the processor so it has the memory and peripherals the firmware needs.
- Bare-metal C/C++: a main loop and interrupt handlers with no scheduler. The smallest footprint and the least overhead, and the easiest to reason about. A good fit for a sensor node, a simple controller, or an accessory.
- RTOS (FreeRTOS, ThreadX, Zephyr): a scheduler on a microcontroller such as an ARM Cortex-M. A good fit when a radio stack, a display, sensor sampling, and user input all have to run at once and meet their deadlines. Zephyr also brings its own networking and Bluetooth stacks.
- Embedded Linux: an application processor with external memory. A good fit for camera pipelines, rich graphical interfaces, filesystems, and large third-party libraries. The cost is more power, a longer boot, a higher bill of materials, and an operating system to maintain for the life of the product.
- List what runs at the same time. One job points to bare-metal. Several independent jobs point to an RTOS.
- Find the hard deadlines. Motor control, radio timing, and sampling rates decide how much scheduling precision the platform needs.
- Check the power budget. A product that has to run for months on a battery rules out most Linux-class processors.
- Then choose the processor. Flash, RAM, and peripherals are sized to what the firmware needs.
The iGuard handles radar, touch, temperature sensing, three wireless protocols, and its display on a single ARM Cortex-M33 microcontroller. The 3Z RF Vision needed an augmented reality overlay on a live camera feed, which called for embedded Linux: PDE built that system from the ground up and tuned the OS configuration for the device's memory and processing constraints. When a function needs tighter timing than software can promise, such as high-rate data acquisition, PDE designs FPGA logic in Verilog or VHDL.