Components

Create the structure and behavior of component models intended for code generation

A component is a modeling construct that you can design and configure to meet code generation requirements. A component publishes its interface to interact with other components in a system composition. You configure a component for deployment to a target platform. When designing a component model that is intended for code generation, consider application algorithm requirements, the expected platform environment, and how to best map the embedded system architecture to the Simulink® modeling environment. To achieve optimal code generation results, use recommended modeling styles and patterns that align with your component requirements. Consider requirements for scheduling, communication, and service interfacing.

To get started, see Component Model Design for Deployment.

Topics

Component Model Design

Component Model Design for Deployment
Represent components as top-level algorithm models that interface with a target platform environment.
Multi-Instantiation
Design a component or subcomponent with the goal of using multiple instances within the context of an application.

Function Interfaces

Periodic and Aperiodic Function Interfaces
A target platform initiates execution of a component by calling generated execution entry-point functions.
Startup, Reset, and Shutdown Function Interfaces
A target platform initiates execution of component startup, reset, or shutdown processing by calling generated initialize, reset, and terminate entry-point functions.

Communication Interfaces

Receive and Send Communication Interfaces
Design a component that communicates with middleware by receiving and sending data.
Message Communication Interfaces
Design a component that communicates with middleware by using triggered messages.
Client-Server Communication Interfaces
Design a component that uses client-server communication.
Device Driver I/O
Design a component that reads input from or writers output to hardware devices.

Service Interfaces

Data Transfer Interfaces
Design a component that transfers data between functions called by middleware.
Nonvolatile Memory Interfaces
Design a component that needs to retain stored information across system power cycles.
Parameter Tuning Interfaces
Design a component that enables middleware to provide access to parameters that you might need to reset during execution.
Measurement Interfaces
Design a component that provides middleware with access to signal data that you might need to measure or monitor during execution.

Featured Examples

Model Single-Core, Single-Tasking Platform Execution

A model designed and configured for embedded system code generation intended to execute on a single-core, single-tasking platform. The application algorithm is captured in a single model hierarchy, making it possible to use Simulink® time-based, single-task scheduling to simulate the model and execute the generated code.

Open Live Script

Model Single-Core, Multitasking Platform Execution

Use Simulink® time-based, multitask scheduling to simulate and generate code for an application algorithm captured in a single model hierarchy. The model is designed and configured for an embedded system intended to execute on a single-core, multitasking platform. The model simulates and the generated code executes based on the model configuration and a rate monotonic scheduling algorithm.

Open Live Script