Intel® Quartus® Prime Pro Edition User Guide: Platform Designer

ID 683609
Date 12/12/2022
Public

A newer version of this document is available. Customers should click here to go to the newest version.

Document Table of Contents

4.10.3. Design Guidelines for Adding Component Instances

In order to promote standard and predictable results when generating static and generated components, follow these best-practices:

  • For two different parameterizations of a component, a component must never generate a file of the same name with different instantiations. The contents of a file of the same name must be identical for every parameterization of the component.
  • If a component generates a nested component, it must never instantiate two different parameterizations of the nested component using the same instance name. If the parent component's parameterization affects the parameters of the nested component, the parent component must use a unique instance name for each unique parameterization of the nested component.
  • Static components that generate differently based on parameterization have the potential to cause problems in the following cases:
    • Different file names with the same entity names, results in same entity conflicts at compilation-time
    • Different contents with the same file name results in overwriting other instances of the component, and in either file, compile-time conflicts or unexpected behavior.
  • Generated components that generate files not based on the output name and that have different content results in either compile-time conflicts, or unexpected behavior.
  • If preserving a custom component as part of an Intel® Quartus® Prime Archive (.qar), you must first explicitly add the component _hw.tcl file to the project to ensure that the .qar includes the component. Click Project > Add/Remove Files in Project to add files to your project.