← Back to the chapter · Previous detail · Next detail →

Technical detail · Choosing a Prototyping Kit

Firmware, operations, and supply migration

Provisioning gives a device its identity, settings, and credentials; test first setup and replacement. A signed over-the-air (OTA) update lets a device verify who authorized new software before installing it. Rollback returns to a known working version if the new one fails. Test a rejected signature and an interrupted or unhealthy update.

The hidden cost often appears at the interface between kit software and product responsibilities. A vendor SDK may publish MQTT topics with a schema the team never designed; a tutorial may store credentials in source; a cloud dashboard may make retry, buffering, or duplicate-message behavior invisible; a breakout board may rely on pull-ups, level shifting, or regulator margin that disappears on a custom PCB. Those are not reasons to reject every convenient kit, but they are reasons to write a boundary before the evidence is reused.

← Back to the chapter · Previous detail · Next detail →