IPT-DSPBUILDER Altera, IPT-DSPBUILDER Datasheet - Page 173

• Manufacturer Part Number: IPT-DSPBUILDER
• Description: DSP BUILDER SOFTWARE
• Manufacturer: Altera
• Type: DSPr

Specifications of IPT-DSPBUILDER

• Function: DSP Builder
• License: Initial License
• Software Application: IP CORE, DSP BUILDER
• Core Architecture: FPGA
• Core Sub-architecture: Arria, Cyclone, Stratix
• Supported Families: Arria GX, Arria II GX, Cyclone, Stratix
• Rohs Compliant: NA
• Lead Free Status / RoHS Status: Not applicable / Not applicable

Chapter :
Integration of Multiple Models in a Top-Level Quartus II Project
Integration of Multiple Models in a Top-Level Quartus II Project
© June 2010 Altera Corporation
1
2. Re-analyze the model by clicking Analyze in the Advanced tab of the Signal
To integrate multiple DSP Builder (standard blockset) designs in a top-level Quartus
II project, you need the .mdl and .ipx files.
Use the Quartus II IP (.qip) file as the single source file for each DSP Builder model.
The .qip file is a single file that contains paths for all the files for an IP design. The .qip
file allows you to add an IP design to the project by adding only one file, rather than
adding all the necessary files individually. You only need the .qip file for Quartus II
archiving for DSP Builder, which does not use it for generation.
If the DSP Builder design includes HDL import or IP MegaCore functions, the
top-level .qip may reference embedded .qip file(s). Also, some older versions of IP
MegaCore functions (before v8.0) and HDL import blocks may have absolute paths in
the generated .qip files. If you migrate the files from a different location, it may be
necessary to manually edit their corresponding .qip files to reflect the new
environment. By running the Analyze process from the Signal Compiler block in
the new location, the .qip file updates automatically with the new path settings. These
embedded .qip file(s) contain the information concerning the projects, libraries and
source HDL required by the Quartus II software for successful integration of these
external entities into DSP Builder.
In addition to the .qip source files, the top-level project also requires an IP Index (.ipx)
file that specifies additional paths for the IP Librarian to find components. SOPC
Builder uses the same IP librarian to search for SOPC Builder components.
Specifically for DSP Builder designs, the Quartus II software needs the .ipx file for the
HDL import and IP MegaCore function blocks that your model uses. Essentially, the
DSP Builder system is an entity composed of DSP Builder blocks, (which themselves
are entities but are easily discoverable), and non-native entities like HDL import and
MegaCore functions. Use the IP Librarian with .ipx files to find all entities.
The DSP Builder specifies the main entities in the main Quartus II .ipx file and need
no special action—you just need to add the extra HDL import and MegaCore function
entities.
To update the IP librarian search path for the top-level Quartus II project, create an
additional directory <project directory>/ip/<module name> and create a file <module
name>.ipx in that subdirectory.
The .ipx file has the following contents:
1
Compiler block to regenerate the auxiliary files (.mdlxml, .qip, .ipx) associated
with the model.
<library>
</library>
<path path='../../../<module name>/**/*'/>
If the ..\DSPBuilder_<mdl name>_import subdirectory copies and the
design files, skip this step.
Preliminary
DSP Builder Standard Blockset User Guide
12–5