Success! Subscription added.
Success! Subscription removed.
Sorry, you must verify to complete this action. Please click the verification link in your email. You may re-send via your profile.
When integrating multiple DSP Builder models into one Quartus II project, you may run into Quartus II compilation issues due to multiple copies of MegaCore libraries being sourced and/or conflicts between multiple HDL source files with the same entity names. It is difficult and tedious to hand edit the included files to avoid these issues.
Error (10430): VHDL Primary Unit Declaration error at alt_dspbuilder_<>.vhd(#): primary unit
"alt_dspbuilder_<>" already exists in library "work"
One way to avoid the file name clashes is to export each of the DSP Builder generated Quartus II project as a post-synthesis .qxp netlist. This will compile each DSP Builder model into a single file which can be instantiated into another Quartus II project in the same way as DSP Builder Exported HDL. The Top qxp export scripting package automates the process of exporting the DSP Builder model as a .qxp file into an easy to use double-clickable script.
Advantages of the DSP Builder exported .qxp module include avoiding naming clashes, single file consolidation of DSP Builder models, and faster Analysis and Elaboration during compilation.
Using the Top qxp export script package to export a DSP Builder model as a .qxp file
Manually exporting a DSP Builder model as a .qxp file
Integrating the DSP Builder model .qxp into a new Quartus II project
© 2010 Altera Corporation. The material in this wiki page or document is provided AS-IS and is not
supported by Altera Corporation. Use the material in this document at your own risk; it might be, for example, objectionable,
misleading or inaccurate.
Community support is provided Monday to Friday. Other contact methods are available here.
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
For more complete information about compiler optimizations, see our Optimization Notice.