Download quicksimII_advanced_..

Custom Design Checks
Name Checking Example
The figure on the previous page shows a name checker rules file. This file can be
created using any text editor, but must be compiled before it can be used by the
run-time check commands. The ASCII file name must include the “.mgc_nc”
suffix so that the Design Manager can recognize it as a special object. Example
names are ascii_rules.mgc_nc and cpu_name_rules.mgc_nc.
Once you complete your rules file for the Name Checker, you use the config_nc
compiler to check the file for errors and to compile it into a binary format. You
can invoke config_nc from the shell or the Design Manager. If your file has any
errors, config_nc does not produce the binary file.
You run the name checks against your design using the Miscellaneous > Check
Design menu item or the Check Design command in DVE. You can run these
checks with DVE open in either standard or batch mode. When you have DVE
open in standard mode, the user interface is visible and you can list the errors in
the Design Syntax Messages window. When you have DVE open in batch mode,
no user interface is displayed and the messages are listed to the transcript, or to a
file if the -File switch is specified.
Regardless of how DVE is run, you use the Check Design command or
$check_design() function to check the design. To perform name checks and have
the messages appear in the Design Syntax Messages window, enter:
CHEck DEsign -NC -NC_Bin_file "$CPU_PROJECT/nc_checks/nc_rules.bin"
To generate a synonym file that contains synonym and alias mapping, enter the
same command, but include the -Nc_syn_file switch and the pathname to the file:
CHEck DEsign -NC -NC_Bin_file "$CPU_PROJECT/nc_checks/nc_rules.bin"
-NC_Syn_file "$CPU_PROJECT/nc_checks/nc_syn"
i
For additional information on the Check Design command or
$check_design() function, refer to the $check_design() reference page in
the Design Viewpoint Editor User's and Reference Manual.
QuickSim II Advanced Training Workbook, 8.5_1
November 1995
6-15