Forum Discussion
Altera_Forum
Honored Contributor
7 years agoI have determined that you do not need a dummy top module, but I was only able to succeed via command-line:
in developer project: quartus_syn to synthesize quartus_cdb --export_partition root_partition --snapshot synthesized (to export the synthesized root_partition) in consumer project: quartus_syn --analysis_and_elaboration (to elaborate design and obtain hierarchy for partitions) Add the following to QSF: set_instance_assignment -name partition <partition-name-in-consumer> -to <instance-in-consumer-hierarchy> -entity <consumer-top-module> set_instance_assignment -name qdb_file_partition <qdb-file> -to <instance-in-consumer-hierarchy> -entity <consumer-top-module> quartus_syn (to synthesize) quartus_cdb --export_partition root_partition --snapshot synthesized (to export the root_partition) Recurse if necessary (e.g. consumer project becomes developer project, and a new consumer project is created). The only problem that remains for me is that I must use an 'entity' declaration in my stub file. In Quartus Standard and other tools, a simple component declaration is sufficient. I hope this is a bug and not intended as it further complicates the VHDL.