Uploaded March 2026 | Updated September 2026, 2 weeks ago
At Embedded World 2026, Electromaker visited the SEGGER booth to see emApps, a new approach to firmware architecture for microcontrollers. The system introduces a modular firmware model where applications run in isolated environments instead of sharing full access to the device.
Traditional firmware gives a single program access to the entire system. emApps changes this by introducing a small executor that runs a virtual core on the microcontroller. This executor requires only about 2 KB of ROM and loads small applications that run inside a sandbox.
Each application receives controlled access to APIs and memory. The executor monitors behavior and stops the app if it accesses restricted memory or functions. This architecture allows developers to add or replace functionality after deployment without affecting the core firmware.
Manufacturers use this approach to create controlled extension platforms. An OEM can ship a device with core firmware and allow partners or rebranders to add features through restricted apps. Developers test and build apps through an online compiler and run them inside the executor on hardware such as SEGGER flashers or on a PC.
Learn more about SEGGER emApps:
segger.com/products/virtualization/emapps/?mtm_campaign=ew26&mtm_kwd=emapps&mtm_source=elektromaker.io
Timestamps:
Introduction to SEGGER emApps – 0:00
Challenges with Traditional Firmware Design – 0:08
Why Modular Firmware Matters – 0:15
Origin of the emApps Concept – 0:37
Virtual Core and Executor Architecture – 1:32
Sandboxed Applications on Microcontrollers – 2:14
Controlled API and Memory Access – 2:23
Protecting the Main Firmware System – 3:04
OEM and Rebranding Use Cases – 3:29
Developing Apps with the Online Compiler – 4:41
Running emApps on Hardware or PC – 5:06
▬ Support Us! ▬▬▬▬▬▬▬▬▬▬
For all the latest products, projects and articles, visit our website at electromaker.io
💡 **Stay Connected with Electromaker!**
youtube.com/channel/UCiMO2NHYWNiVTzyGsPYn4DA?sub_confirmation=1
facebook.com/electromaker.io
twitter.com/ElectromakerIO
linkedin.com/company/electromaker
At Embedded World 2026, Electromaker visited the SEGGER booth to see emApps, a new approach to firmware architecture for microcontrollers. The system introduces a modular firmware model where applications run in isolated environments instead of sharing full access to the device.
Traditional firmware gives a single program access to the entire system. emApps changes this by introducing a small executor that runs a virtual core on the microcontroller. This executor requires only about 2 KB of ROM and loads small applications that run inside a sandbox.
Each application receives controlled access to APIs and memory. The executor monitors behavior and stops the app if it accesses restricted memory or functions. This architecture allows developers to add or replace functionality after deployment without affecting the core firmware.
Manufacturers use this approach to create controlled extension platforms. An OEM can ship a device with core firmware and allow partners or rebranders to add features through restricted apps. Developers test and build apps through an online compiler and run them inside the executor on hardware such as SEGGER flashers or on a PC.
Learn more about SEGGER emApps:
segger.com/products/virtualization/emapps/?mtm_campaign=ew26&mtm_kwd=emapps&mtm_source=elektromaker.io
Timestamps:
Introduction to SEGGER emApps – 0:00
Challenges with Traditional Firmware Design – 0:08
Why Modular Firmware Matters – 0:15
Origin of the emApps Concept – 0:37
Virtual Core and Executor Architecture – 1:32
Sandboxed Applications on Microcontrollers – 2:14
Controlled API and Memory Access – 2:23
Protecting the Main Firmware System – 3:04
OEM and Rebranding Use Cases – 3:29
Developing Apps with the Online Compiler – 4:41
Running emApps on Hardware or PC – 5:06
▬ Support Us! ▬▬▬▬▬▬▬▬▬▬
For all the latest products, projects and articles, visit our website at electromaker.io
💡 **Stay Connected with Electromaker!**
youtube.com/channel/UCiMO2NHYWNiVTzyGsPYn4DA?sub_confirmation=1
facebook.com/electromaker.io
twitter.com/ElectromakerIO
linkedin.com/company/electromaker
