← Back to the chapter · Previous detail

Technical detail · Choosing a Hardware Platform

Software defaults and module assumptions

A board support package (BSP) is software that helps an operating system use a board’s hardware. Linux udev rules configure devices when the system detects them. An antenna keep-out is the clear space required around an antenna for it to work as designed. A matching network is a circuit that helps transfer radio power between the radio and antenna. Software layers can hide risks too. An Arduino core may hide ESP-IDF configuration, a vendor BSP may hide clock and pin defaults, and a Raspberry Pi image may hide Linux service dependencies, filesystem writes, udev rules, NetworkManager behavior, and shutdown recovery. A board that works in the lab can still fail the evidence question if it cannot expose boot logs, watchdog resets, radio reconnects, flash wear, certificate storage, or signed-update failure paths. When the platform includes a radio module, check the module datasheet and reference layout assumptions: antenna keep-out, ground plane, matching network, regulatory modular approval, and enclosure effects are not proven by a USB-powered bench demo.

The platform has done its job when it exposes the next risk clearly enough to choose the next form. That may mean moving from an Arduino-class starter board to an ESP32 or nRF52 connected node, from loose modules to a carrier board, from a laptop-hosted script to an embedded gateway, or from a module carrier to a custom PCB. Base the next step on a measured result. Do not move on just because the current board feels familiar.

← Back to the chapter · Previous detail