What does message: "# No signals matching" mean?

Description

Scripts from Active-HDL 8.3 and earlier that added signals to the waveform did not require the full hierarchy path, e.g. wave /clk. If a script is run in Active-HDL 9.1, the user will receive the "No signals matching" message and no signals will be added to the waveform.

Solution

Starting with Active-HDL 9.1, users will now need to provide the full signal path, e.g. wave /testbench/UUT/clk. The requirement to provide the full signal or entity path was created to prevent confusion between components that had the same name within the current hierarchy and within the root hierarchy.

Advantages

• Unified notation in hierarchical names

• Removes ambiguities that may appear when using multiple top-level units during simulation

The use of the relative hierarchical names with a reference to the design region defined by using the env command remains unchanged. Some macros or HDL code using ambiguous hierarchical names for single top-level module simulations may require an update.

All the debugging tools (e.g. Advanced Dataflow, Watch, Memory Viewer, Waveform Viewer, HDL Editor, etc.) working in the GUI mode present absolute hierarchical paths as the standardized hierarchical paths. Similarly, the hierarchical paths returned by the simulator begin with the hierarchy separator followed by the name of the top-level unit.

For more information, refer to the Using Active-HDL | Hierarchical Names topic of the Active-HDL help.