Hierarchy flattening enables you to remove subsystem hierarchy from the HDL code generated from your design.
HDL Coder™ considers blocks within a flattened subsystem to be at the same level of hierarchy, and no longer grouped into separate subsystems. This consideration allows the coder to reorganize blocks for optimization across the original hierarchical boundaries, while preserving functionality.
To preserve the modularity of the design and have a one-to-one mapping from
subsystem name to corresponding HDL
entity name, do not flatten the hierarchy. The generated HDL
code is more readable when you don't flatten the hierarchy.
Flatten hierarchy to:
Enable more extensive area and speed optimization.
Reduce the number of HDL output files. For every subsystem that you flatten, HDL Coder generates one less HDL output file.
Before you flatten the hierarchy, you must have the
MaskParameterAsGeneric property set to
off. For more information, see Generate parameterized HDL code from masked subsystem.
When you use optimizations such as resource sharing or streaming with hierarchy flattening, in certain cases, HDL Coder might retain the subsystem hierarchy in the generated model. However, the HDL code generated for the flattened subsystems is inlined, which reduces the number of HDL files.
When you use floating-point data types in
Point mode, HDL Coder might not flatten the hierarchy. This is because
floating-point designs generate hundreds of lines of code and inlining the
HDL files makes the generated code less readable.
By default, a subsystem inherits its hierarchy flattening setting from the parent subsystem. However, you can enable or disable flattening for individual subsystems. This table lists options you can specify for hierarchy flattening options for a subsystem are listed in the following table.
|Hierarchy Flattening Setting||Description|
|inherit (default)||Use the hierarchy flattening setting of the parent subsystem. If this subsystem is the highest-level subsystem, do not flatten.|
|on||Flatten this subsystem.|
|off'||Do not flatten this subsystem, even if the parent subsystem is flattened.|
To set hierarchy flattening using the HDL Block Properties dialog box:
In the Apps tab, select HDL Coder. The HDL Code tab appears. Select the Subsystem and then click HDL Block Properties. For FlattenHierarchy, select on, off, or inherit.
Right-click the Subsystem and select HDL Code > HDL Block Properties. For FlattenHierarchy, select on, off, or inherit.
To set hierarchy flattening from the command line, use
For example, to turn on hierarchy flattening for a subsystem,
hdlset_param('my_dut', 'FlattenHierarchy', 'on')
A subsystem cannot be flattened if the subsystem is:
A Synchronous Subsystem or uses the State Control block in
A model reference implementation.
A Triggered Subsystem when Use trigger signal as clock is enabled.
A masked subsystem that contains any of the following:
Enumerated data type.
Lookup table blocks: 1-D Lookup Table, 2-D Lookup Table, Cosine HDL Optimized, Direct LookupTable (n-D), Prelookup, Sine HDL Optimized, n-D Lookup Table.
MATLAB System block.
Stateflow® blocks: Chart, State Transition Table, Sequence Viewer.
Blocks with a pass-through or no-op implementation. See Pass through, No HDL, and Cascade Implementations.
This option removes subsystem boundaries before code generation. It does not necessarily generate HDL code with a completely flat hierarchy.
To see the hierarchy flattening information in the report, before you generate code for each subsystem or model reference, enable the optimization report. To enable this report, in the HDL Code tab, select Report Options, and then select Generate optimization report.
The report displays subsystems in your model that have
FlattenHierarchy set to
off, hierarchy flattening status, and the HDL files that are
inlined. You can use the report to more effectively flatten the subsystem hierarchy
and improve opportunities for optimizations such as clock-rate pipelining on the
If hierarchy flattening is unsuccessful, the report shows a table that contains subsystems that are not flattened, and reasons for not flattening the subsystem. Subsystems that have a * highlighted beside it indicates whether the HDL files are inlined though hierarchy flattening failed.