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.
Component Model Design
- 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.
- 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.
- 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.