Give your ESP32s the Gift of Serviceability
summary
ESP32 becomes remotely serviceable by running a small virtual machine and language that sandbox applications, let the cloud orchestrator install or replace code, and survive buggy updates; the platform ships a Toit VM that takes about 1 MB flash / 30–40 KB RAM and uses gRPC + protobuf APIs to push encrypted source strings and binaries to fleets. Target hardware is a dual‑core 240 MHz ESP32 with ~0.5 MB RAM and ~10 µA deep sleep; demos show a faulty Fibonacci crash without bricking the device.
AI-written summary · about
chapters (14)
- 0:00Intro
- 6:03ESP32 Software Development
- 9:40Firmware vs Software
- 12:50What is Serviceability
- 16:05Virtual Machines
- 17:24Cloud Management
- 22:18Custom Programming
- 31:22Combined Tables
- 33:50Demonstration
- 39:00Instructions
- 39:57The Challenge
- 43:10The Future of IoT
- 44:18Security Concerns
- 45:45Memory Footprint
related talks
20mEvaluating AtomVM for Fault-Tolerant ESP32-Based Systems
39mClojureScript on Microcontrollers
50mPrototyping New Ideas with the ESP32 and Azure
48mFatal Fury on ESP32: Time to Release Hardware Exploits
25mMicroPython for ESP32
54mSqueezing Your Microcontroller
43mConnecting Microcontrollers to the Cloud Using MQTT, BLE, and HTTP
15mWOOD: Extending a WebAssembly VM with Out-of-Place Debugging for IoT applications