run-凯发k8网页登录
run-time software modeling, at a basic level, is taking simulink® components and modeling, simulating, and targeting them for embedded software frameworks (e.g. autosar, arinc, or your custom domain-specific framework). simulink provides a range of modeling abstractions that help enhance your algorithm model to be suitable for mapping to scheduling, communication, memory, and diagnostic services that are provided by such frameworks. for instance, you can use:
- specific modeling styles to partition your design for run-time scheduling
- buses to capture software interfaces
- simulink functions to map to diagnostic and memory services
- schedule editor and stateflow® to create simple test harnesses and to simulate the composition
- messages to tie into communication middleware
- irt subsystems combined with state charts (from stateflow) to define complex power-cycle and mode-transition logic
in addition, using model reference, variant, and data management capabilities, you can build your components for maximal reuse within an application and even across multiple software frameworks. complemented by the simulink platform for simulating large compositions and the capabilities of embedded coder® for producing custom code for your software frameworks, you will have a full range of capabilities to specify, elaborate, test, and validate your software components. explore the related features videos to learn more about the capabilities simulink provides.
run-time software modeling helps you implement large-scale run-time systems by defining the components in a composition, simulating and testing them, generating code, and integrating the code into a larger system.
partition and schedule models with the export function modeling style to integrate functions into your software environment easily and have a clear mapping from model to code.
rate-based subsystems can be partitioned and scheduled as well, allowing you to combine modeling styles with schedulable components.
use simulink functions to model software services. a function caller block can model and generate code for the client’s call to services, especially i/o services, and a simulink function block provides those services.
explicitly schedule the execution of your model components, including export functions and rate-based models, with schedule editor for both simulation and code generation, where every specified partition has an entry point in the generated code.
what are messages in simulink? use messages to model and generate c code for software compositions with message-based communication.