Iterate fast on hardware with Nerves
summary
Nerves uses Erlang/OTP and the BEAM plus Elixir and Buildroot to boot a read only Linux image that runs the VM as PID 1, provides AB partitions with automatic rollback, signed FWUP firmware streaming and binary deltas, and hot code updates via the IEx REPL and Livebook. Demos show mix firmware, mix burn and mix upload to Raspberry Pi targets, remote consoles and fleet updates (NervesHub / Nerves Cloud) across ~150,000 devices with staged deployments of ~30MB images and 10 concurrent updates for safer rollouts.
AI-written summary · about
chapters (18)
- 0:00Nerves and embedded Elixir
- 3:55Speaker background
- 8:32Why choose Nerves
- 12:08Development workflow
- 15:22Updating firmware
- 17:38Hot code updates
- 19:49Livebook for debugging
- 25:07Host-based development
- 25:49Shipping mistakes
- 26:50Fault recovery layers
- 28:58Firmware updates safety
- 31:05NervesHub for fleet
- 34:12Device authentication
- 35:38Debugging emergencies
- 38:46Health monitoring
- 39:50Real-world hardware challenges
- 41:55Nerves advantages
- 42:16Conclusion
related talks
36mGet Cooking With Nerves
31mUpdating the Edge
31mUpdating the Edge
36mContinuous Deployment of IoT Sensors
37mHardware Onboarding and Burn in with Ironic in the CERN
10mLightning Talk: Using Zephyr to Power the Sustainable Cloud
40mBoard Farms for Everyone: Making Hardware Debugging Easier and Sharing Boards...
34mScheduling in CI/CD systems
