Nucleus Process Model
The Nucleus process model adds task and library isolation, as well as memory protection, to the real-time embedded platform. This results in a significant increase in product reliability due to faster isolation of software faults and the ability of deployed systems to self-diagnose.
Developers can dynamically update application software during system operation, allowing the target to be kept up to date, even in mission critical environments.
- Isolate user tasks from kernel and middleware resources
- Isolate user tasks from each other
- Enhance product stability prior to product shipment
- Allow post-mortem analysis of field failures
- Perform graceful, controlled system restarts when a critical bug surfaces
- Dynamically load and unload processes from execution memory, sourced in Flash, file systems, and/or network connections
Full isolation of kernel and middleware resources
Scribblers, stack overflows, accessing rogue pointers, etc. in application code can no longer corrupt or interfere with system software operation.
Self-contained user processes and libraries
Once a user process or library module has been debugged, another user process cannot destabilize it.
Dynamic loading and unloading of user code modules
Code modules can be loaded from nonvolatile storage, file systems, and/or networking links. Unloading releases all code and data memory allocated upon load.