Programmable Devices
CPLDs, FPGAs, SoC FPGAs, Configuration, and Transceivers
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.
21615 Discussions

MAX_FANOUT problem

Altera_Forum
Honored Contributor II
‎01-21-2012 09:25 AM
1,977 Views

Hi  

 

I have set a global fanout constraint to 25 and the tool is also inserting cells as shown in the info generated. 

But still when i see the fitter report there are NON-GLOBAL signals with fanouts of 400 . 

Even by using the assignment editor if i set the instance fanout assignments for those signals the tool is accepting it and no report for ignored fanout assignments are genrated but still the signals are having the same fanout if i check the fitter rpt. 

The state is quite confusing that the assignment is not ignored and not even implemented. 

Please guide me with this. 

Thanks
0 Kudos

Link Copied

2 Replies
Altera_Forum
Honored Contributor II
‎01-21-2012 09:52 AM
820 Views

There could be answer that the signals are outputs of a combinatorial black and the max_fanout constraint applies only to registers . 

Is there a way to constraint the fanouts of combinatorial blocks.
0 Kudos
Copy link
Altera_Forum
Honored Contributor II
‎01-22-2013 08:24 PM
820 Views

Hi, 

 

Synthesis report <project>.map.rpt has "Registers Duplicated to Honor Maximum Fanout Requirements" section. 

It lists all the registers, required fanout and number of duplicated registers created for those registers. 

 

Thanks, 

Evgeni
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.