Download Filter Design HDL Coder User`s Guide

Integration With Third-Party EDA Tools
1
An initialization (Init) phase. The Init phase performs required setup actions,
such as creating a design library or a project file. Some arguments to the Init phase
are implicit, for example, the top-level entity or module name.
2
A command-per-file phase (Cmd). This phase of the script is called iteratively, once
per generated HDL file or once per signal. On each call, a different file or signal
name is passed in.
3
A termination phase (Term). This is the final execution phase of the script. One
application of this phase is to execute a simulation of HDL code that was compiled in
the Cmd phase. The Term phase does not take arguments.
The coder generates scripts by passing format strings to the fprintf function. Using the
GUI options (or generatehdl properties) summarized in the following sections, you can
pass in customized format strings to the script generator. Some of these format strings
take arguments, such as the top-level entity or module name, or the names of the VHDL
or Verilog files in the design.
You can use legal fprintf formatting characters. For example, '\n' inserts a newline
into the script file.
Customizing Script Generation Using CLI Properties
This section describes how to set properties in the generatehdl function to enable or
disable script generation and customize the names and content of generated script files.
Enabling and Disabling Script Generation
The EDAScriptGeneration property controls the generation of script files. By
default, EDAScriptGeneration is set 'on'. To disable script generation, set
EDAScriptGeneration to 'off', as in the following example.
generatehdl(Hd,'EDAScriptGeneration','off')
Customizing Script Names
When HDL code is generated, the code generator forms script names by appending a
postfix string to the filter name Hd.
When test bench code is generated, the code generator forms script names by appending
a postfix string to the test bench name testbench_tb.
6-37