Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17267 Discussions

How to include a HPS with block symbol file

Altera_Forum
Honored Contributor II
‎09-02-2017 01:59 PM
2,689 Views

Hello, 

 

I'm quite new in the HPS development process and the toolchain from ALTERA. 

Could someone give me some instruction how I can implement the generated HPS System with QSys in a Block diagram file? 

After it should look like that the HPS is the central symbol block and the other logic is conneted to it's interfaces. 

The logic itself from the different blocks should be implemented in VHDL Code. 

 

Actually when I create a blank block diagram file and insert the generated block symbol file from the HPS which is generated by QSys I get always errors: 

 

Error: The auto-constraining script was not able to detect any instance for core < hps_sdram_p0 > 

Error: Verify the following: 

Error: The core < hps_sdram_p0 > is instantiated within another component (wrapper) 

Error: The core is not the top-level of the project 

Error: The memory interface pins are exported to the top-level of the project 

Error: Alternatively, if you are no longer instantiating core < hps_sdram_p0 >, 

Error: clean up any stale SDC_FILE references from the QSF/QIP files. 

 

How can I fix this issue and where can I find a guideline how to use block symbol files? 

 

Thanks
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎02-20-2018 10:59 PM
1,672 Views

You should add only the .qip file to your Quartus Project. And the top level entity souldn't be named like your Qsys System, your top level entity is your schematic file.

0 Kudos
Copy link
Reply

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.