Occasional Contributor
Super ContributorSorry for the late reply. Could you refer to the document link on 2.10.1. Static IP Components - Typical Usage of the add_hdl_instance Command for Static Components?
Check that you have followed the correct usage of the add_hdl_instance for static components.
Let me know if it helps to solve the issue.
Best Regards,
Richard Tan
p/s: If any answer from the community or Intel support are helpful, please feel free to give Kudos.
Occasional ContributorI had a quick look at what is being suggested as the TCL orchestrated solution above, see below.
All I can say is that configuring IP with VHDL generics just might be a simpler and less kludgy way to integrate Intel/Altera generated IP into HDL?
proc generate { entity_name } {
# get the autogenerated name for emif_instance_name added
# via add_hdl_instance
set autogeneratedfixedname [get_instance_property \
emif_instance_name HDLINSTANCE_GET_GENERATED_NAME]
set fileID [open "generated_toplevel_component.v" r]
set temp ""
# read the contents of the file
while {[eof $fileID] != 1} {
gets $fileID lineInfo
# replace the top level entity name with the name provided
# during generation
regsub -all "substitute_entity_name_here" $lineInfo \"${entity_name}" lineInfo
# replace the autogenerated name for emif_instance_name added
# via add_hdl_instance
regsub -all "substitute_autogenerated_emifinstancename_here" \
$lineInfo"${autogeneratedfixedname}" lineInfo \
append temp "${lineInfo}\n"
}
