cgsl_0409: Data transfer for component deployment
ID: Title | cgsl_0409: Data transfer for component deployment | |
---|---|---|
Description | To model data transfers: | |
A | Use signals between callable functions. | |
B | When branching or merging transfer signals, in the Embedded Coder dictionary, add
$X to the Function Naming Rule fields.
Compliance with this rule is enforced during code generation. | |
C | Do not branch data transfer signals to the root-level output port. Compliance with this rule is enforced during code generation. | |
Notes | When merging data transfer signals, ensure that both signals are mutually exclusive. | |
Rationale | The generated code aligns with the data communication method required by the platform environment for concurrent execution. | |
Model Advisor Check | A Model Advisor check is not provided for this guideline. | |
Examples |
void CD_accumulator(void) . . . tmpIrvIRead = get_CD_accumulator_DataTransfer(); . . . void CD_integrator(void) . . . tmp = set_CD_integrator_DataTransfer(); . . . void CD_Aperiodic2(void) . . tmp = set_CD_Aperiodic2_DataTransfer(); . . . |
See Also
Code Interfaces and Code Interface Specification (Embedded Coder)
Data Transfer Service Interfaces (Embedded Coder)
Data Communication Methods (Embedded Coder)
Embedded Coder Dictionary (Embedded Coder)
Target Environment Services (Embedded Coder)
Select Code Generation Output for Target Platform Deployment (Embedded Coder)
Configure Signal Data for C Code Generation (Embedded Coder)
get
(Embedded Coder)
set
(Embedded Coder)