AT-based Modem Support in the Zephyr Project: Present and Future
summary
Zephyr adds a reusable modem context that centralizes read/write, a shared AT command parser, and a POSIX-like socket offload (replacing the older net offload) for the 2.0 release. A UART-based interface implementation and modem shell exist now, enabling LTE Cat-M1/NB‑IoT modems (e.g. SARA‑R4, SparkFun shield, Nordic nRF9160 SiP) to present sockets to Zephyr’s network stack and run LwM2M/MQTT. It works and shrinks per-driver boilerplate; gaps remain around modem pins, eDRX/power control and persistent config storage.
AI-written summary · about
chapters (21)
- 0:00Introduction
- 0:46Agenda
- 1:50Michaels Story
- 3:19Network Stack
- 4:31Modem Implementation
- 5:39Modem Context Driver
- 7:41Offloaded APIs
- 8:24Socket APIs
- 9:54Modem Receiver
- 10:59Modem Context
- 12:22UART
- 13:22Command Parsing
- 14:11Modem Command Define You
- 15:57Config Helper
- 17:00Socket offload API
- 18:07How to get started
- 19:55Modems covered
- 20:50SparkFun R4
- 21:29Nordic 90160
- 23:03whats next
- 24:44questions
related talks
36mConnecting Zephyr Devices at Scale Using Open Source Solutions
49mThe Zephyr™ Project – An Updated Overview
30mZephyr ❤️ Internet: How Zephyr Speeds Implementation for New IoT Devices
36mConnecting Zephyr Devices at Scale Using Open Source Solutions
35mLoRa Meets Zephyr
45mImplementing Network Protocols in Zephyr Project
20mZephyr Network Subsystem Status and Overview
41mWiFi and Secure Socket Offload in Zephyr