Main Content

cgsl_0402: Signal interfaces for component deployment

ID: Titlecgsl_0402: Signal interfaces for component deployment
Description

At the root level of a component, signal interfaces shall be modeled by using only one type of signal:

  • In Bus Element and Out Bus Element blocks

  • Inport and Outport blocks

A

For structured signals that use In Bus Element and Out Bus Element blocks, set block parameters as follows:

  • Data type to Bus: <object name>.

  • Bus virtuality to nonvirtual.

Configure the interface for each In Bus Element and Out Bus Element block individually.

B

For structured signals that use Inport and Outport blocks, set block parameters as follows:

  • Data type to Bus: <object name>.

  • Specify that the outport bus is nonvirtual at the root level by selecting Outport block parameter Output as nonvirtual bus in parent model.

  • Specify that the output for a top-level Inport block used to load bus data is nonvirtual by selecting Inport block parameter Output as nonvirtual bus.

Notes

Do not use datastore memory for signal interfaces.

Rationale

Reduces complexity and provides model clarity.

Model Advisor CheckVerify this guideline by using Model Advisor check Check signal interfaces (Embedded Coder)

Version History

expand all

Introduced in R2022b