Represent enabled subsystem that has synchronous reset and enable behavior
HDL Coder / HDL Subsystems
An Enabled Synchronous Subsystem is an Enabled
Subsystem that uses the
of the State Control block. If an S symbol
appears in the subsystem, then it is synchronous.
To create an Enabled Synchronous Subsystem block,
add the block to your Simulink® model from the HDL Subsystems
block library. You can also add a State Control block
with State control set to
an Enabled subsystem.
For more information, see Data Types Supported by Simulink in the Simulink documentation.
Cause Simulink software to display labels for the subsystem's ports on the subsystem's icon.
Does not display port labels on the subsystem block.
If the corresponding port icon displays a signal name, display the signal name on the subsystem block. Otherwise, display the port block's name.
Display the name of the corresponding port block on the subsystem block.
If a name exists, display the name of the signal connected to the port on the subsystem block; otherwise, the name of the corresponding port block.
Control user access to the contents of the subsystem.
Enables opening and modification of subsystem contents.
Enables opening but not modification of the subsystem. If the subsystem resides in a block library, you can create and open links to the subsystem and can make and modify local copies of the subsystem but cannot change the permissions or modify the contents of the original library instance.
Disables opening or modification of subsystem. If the subsystem resides in a library, you can create links to the subsystem in a model but cannot open, modify, change permissions, or create local copies of the subsystem.
Enter name of a function to be called if an error occurs while Simulink software is executing the subsystem.
Simulink software passes two arguments to the function: the handle of the subsystem and a character vector that specifies the error type. If no function is specified, Simulink software displays a generic error message if executing the subsystem causes an error.
Specify whether to resolve names of workspace variables referenced by this subsystem.
Resolve all names of workspace variables used by this subsystem, including those used to
specify block parameter values and Simulink data objects (for example,
Resolve only names of workspace variables used to specify block parameter values, data store memory (where no block exists), signals, and states marked as “must resolve”.
Do not resolve any workspace variable names.
Causes Simulink software to treat the subsystem as a unit when determining the execution order of block methods.
Cause Simulink software to treat the subsystem as a unit when determining the execution order of block methods. For example, when it needs to compute the output of the subsystem, Simulink software invokes the output methods of all the blocks in the subsystem before invoking the output methods of other blocks at the same level as the subsystem block.
Cause Simulink software to treat all blocks in the subsystem as being at the same level in the model hierarchy as the subsystem when determining block method execution order. This can cause execution of methods of blocks in the subsystem to be interleaved with execution of methods of blocks outside the subsystem.
This parameter enables:
Causes Simulink software to treat the subsystem as a unit when propagating variant conditions from Variant Source blocks or to Variant Sink blocks.
Simulink treats the subsystem as a unit when propagating variant conditions from Variant Source blocks or to Variant Sink blocks. For example, when Simulink computes the variant condition of the subsystem, it propagates that condition to all the blocks in the subsystem.
Simulink treats all blocks in the subsystem as being at the same level in the model hierarchy as the subsystem itself when determining their variant condition.
Treat as grouped when propagating variant conditions enables this parameter.
Specify the code format to be generated for an atomic (nonvirtual) subsystem.
Simulink Coder software chooses the optimal format for you based on the type and number of instances of the subsystem that exist in the model.
Simulink Coder software inlines the subsystem unconditionally.
Simulink Coder software explicitly generates a separate function in a separate file. Subsystems with this setting generate functions that might have arguments depending on the Function interface parameter setting. You can name the generated function and file using parameters Function name and File name (no extension). These functions are not reentrant.
Simulink Coder software generates a function with arguments that allows reuse of subsystem code when a model includes multiple instances of the subsystem.
This option also generates a function with arguments that allows subsystem code to be reused in the generated code of a model reference hierarchy that includes multiple instances of a subsystem across referenced models. In this case, the subsystem must be in a library.
Double | Single | Boolean | Base Integer | Fixed-Point | Enumerated | Bus
HDL Code Generation