Zephyr Extensions: How to Dynamically Load an Application
summary
Claims that Zephyr can load extensions as ELF modules from persistent storage and run them on-device, with a CANopen stack and a simple counter plugin built and demonstrated on an STM32 Cortex‑M4. Tools used: Zephyr LL EXT subsystem, ELF relocation, filesystem config, GDB symbol loading and Simulink for functional comparison; results show identical outputs to simulation and no realtime penalty, with measured load times of 10 ms for a tiny counter and ~160 ms for the CANopen stack. Raises concrete cybersecurity and certification questions.
AI-written summary · about
chapters (9)
- 0:00Zephyr Extensions intro
- 8:54Developing LL_EXT
- 13:32CANopen stack extension demo
- 17:10LL_EXT performance
- 20:03LL_EXT industry use
- 22:49Cybersecurity and safety considerations for extensions
- 27:08Contributing to Zephyr
- 32:07Live LL_EXT demo
- 32:29Q&A debugging & plans
related talks
39mZephyr Extensions: How to Dynamically Load an Application
32mFuzzing Zephyr Apps - Struggles of Dynamic Analysis on Embedded Applications
27mZephyr and Trusted Execution Environments
27mZephyr and Trusted Execution Environments
31mUsing Zephyr for Embedded Controllers
15mExtending Applications Safely and Efficiently
05mZephyr
16mDesigning Secure Systems for CRA Compliance leveraging Zephyr