Altera Quartus II Scripting - Manual (Page 31)

Chapter 2: Command-line Executables 2–5
quartus_cdb
© July 2013 Altera Corporation Quartus II Scripting Reference Manual
--bottom_up_scripts_virtual_input_pin_delay[=]
Specifies a delay, in nanoseconds, used to constrain all paths from any of the newly created virtual input
pins in the lower-levels. This is to help guide the lower-level placement and produce a better quality
top-level result.
The value represents the maximum acceptable delay for an inter-partition signal to arrive at the project's
virtual input pin from another module. The value helps guide lower-level placement.
--bottom_up_scripts_virtual_output_pin_delay[=]
Specifies a delay, in nanoseconds, used to constrain all paths to any newly created virtual output pins in
the lower-levels. This helps guide the lower-level placement and produces a better quality top-level result.
The value represents the maximum acceptable delay for an inter-partition signal driven by the virtual
output pin to arrive at its destination. The value helps guide lower-level placement.
--create_companion[=]
Creates a HardCopy companion revision based on the current revision.
If is specified, it is used to create the HardCopy companion revision. Otherwise, the
default companion revision name is used unless the COMPANION_REVISION_NAME assignment is
found in the current revision's Quartus II Settings File (.qsf).
Reverse migration also supported when the originating revision is a HardCopy device (HardCopy II or
newer). The companion created will be targeted to FPGA revision with a proper companion name if the
is not specified and the COMPANION_REVISION_NAME assignment is not
found.
The current revision should be fully compiled for this option to migrate all pin locations.
Usage
quartus_cdb [-c ] --create_companion=[]
Note that is the new current revision after executing this option.
Examples
## The following example illustrates the option usage using
## Stratix II and HardCopy II migration scenario
## Compile the Stratix II revision
quartus_sh --flow compile myproject -c myfpga
## Create a HardCopy II revision named "myhcii" based on "myfpga"
quartus_cdb myproject -c myfpga --create_companion=myhcii
## Compile the HardCopy II revision
quartus_sh --flow compile myproject -c myhcii
## **********************************
## Or you can simply do the following
## **********************************
## Compile the Stratix II revision
quartus_sh --flow compile myproject
## The following command will create the
## HardCopy II revision named "myproject_hcii"
## unless the COMPANION_REVISION_NAME assignment
## is found in myproject.qsf.
quartus_cdb myproject --create_companion