Examples, Netlist_type=<map|cmp|asm, Override_partition_netlist_type=<value – Altera Quartus II Scripting User Manual

Page 40: Post_map[=on|off

Advertising
background image

2–14

Chapter 2: Command-line Executables

quartus_cdb

Quartus II Scripting Reference Manual

© July 2013

Altera Corporation

Examples

## Run Analysis & Synthesis for Stratix II revision
quartus_map myproject -c myfpga

## Run Fitter for Stratix II revision
quartus_fit myproject -c myfpga

## Run MIF Dependency Check for Stratix II revision
quartus_cdb myproject -c myfpga --mif_dependency=mif_check

## Run MIF Dependency Check cleanup for Stratix II revision
quartus_cdb myproject -c myfpga --mif_dependency=cleanup

--netlist_type=<map|cmp|asm>

Loads the specified atom netlist type. This option is used in combination with the "-write_equation_file"
option. Use "map" to specify the post Analysis & Synthesis netlist. Use "cmp" to specify the post Fitter
netlist. Use "asm" to specify the post Assembler netlist. The post Assembler netlist is only supported for
designs using the HardCopy device family.

--override_partition_netlist_type=<value>

Overrides the netlist type setting for the specified Design Partition for this compililation. The option must
be used with the --merge option.

<value> takes the form of "<partition name>=<netlist type>", including the double quotes. For example, to
use netlist type POST_SYNTH for a partition named "alu", use the following argument:

--override_partition_netlist_type="alu=POST_SYNTH"

For non-imported partitions, the following netlist type values can be used:

POST_SYNTH
POST_FIT
STRICT_POST_FIT
EMPTY

For imported partitions, the following netlist type values can be used:

IMPORT
IMPORT_BASED_POST_FIT
EMPTY

To override the netlist type for more than one partition, use the override_partition_netlist_type option as
many times as needed.

--post_map[=on|off]

Limits the --export_database and --import_database options to only export and import the output of
Analysis and Synthesis (quartus_map) to and from the version-compatible database.

Note: This option must be used with either the --export_database or the --import_database option.

--remove_existing_regions_in_bottom_up_scripts[=on|off]

When this option is enabled, generated Tcl scripts contain commands that remove any LogicLock regions
that exist in the project the script is being called within.

This option is enabled by default. Add the flag --remove_existing_regions_in_bottom_up_scripts=off to
disable.

Advertising