Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
17258 Discussions

Warning: ... entity does not exist in design

Altera_Forum
Honored Contributor II
‎06-26-2012 04:09 PM
4,241 Views

After compiling my project, I got this error: Can't set a partition on "clipper:c1" which is not a hierarchy in the user design. 

 

I also get a warning after doing Analysis & Elaboration which I think is related to my problem. Warning: Ignored assignments for entity "test" -- entity does not exist in design. 'test' is the top-level entity. 

 

I had successfully compiled my design using incremental synthesis, but since changing the top-level entity by going into Assignments -> Device... -> General, my design no longer compiles. The top-level entity had been 'out', which is now a sub-module of 'test'. 

 

Since making this change, I am not able to expand the top level entity in the hierarchy tab of the Project Navigator. I have a file named test.v which contains a module called 'test'. This file is listed under Device Design Files in the Files tab of the Project Navigator. 

 

I am using Quartus II v 5.0.
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎06-26-2012 04:43 PM
2,746 Views

I solved the problem by switching the top-level entity from 'test' back to 'out', unchecking 'set as design partition' for each partition, compiling, changing the top-level entity from 'out' to 'test', compiling, checking 'set as design partition' for each partition again, and re-compiling.

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.