1/38
Looks like no tags are added yet.
Name | Mastery | Learn | Test | Matching | Spaced | Call with Kai | Chat |
|---|
No analytics yet
Send a link to your students to track their progress
Fanout
The number of loads or destinations driven by a signal.
High Fanout
A condition in which one source signal must distribute its value to many loads.
High Fanout as a Physical Problem
One logical source must physically communicate with many destinations distributed through the FPGA.
Load
A destination that receives a value driven by a source signal.
One Driver → Many Destinations
The communication pattern that creates fanout.
Control Signals
Signals that can acquire significant fanout because the same control decision may influence many parts of the design.
Enable Signals
Common examples of signals that may need to reach many destinations and therefore acquire significant fanout.
Reset Signals
Common examples of broadly distributed signals that may have high fanout.
Mode Signals
Signals such as operating-mode selections that may influence many blocks and therefore require broad physical distribution.
Widely Used Status Signals
Status information consumed by many destinations can create significant fanout.
High Fanout Does NOT Automatically Mean a Defect
High fanout can be legitimate, but it gives the designer a reason to inspect the physical implementation evidence.
Managing High Fanout
Implementation tools may replicate logic or choose routing strategies to distribute a source value to many destinations.
Logic Replication for Fanout
An implementation technique in which logic may be duplicated so that distribution does not depend entirely on one physical source reaching every load.
Fanout Distribution
The physical pattern created as one source value is delivered to its many loads throughout the FPGA.
Simple Boolean Equation, Difficult Physical Distribution
A logically simple signal can still create a substantial implementation problem when it must physically reach many destinations.
Congestion
Physical routing pressure created when many nets compete for routing resources in the same FPGA region.
Routing Resources
Physical interconnect resources that are abundant but finite.
Congested Region
An area of the FPGA in which many competing routes must pass through limited routing resources.
Routing Competition
The situation in which multiple nets require interconnect resources within the same physical region.
Low Routing Pressure
A physical region where routing demand can be accommodated without substantial competition for available interconnect.
High Routing Pressure
A physical region where many communication paths compete for limited interconnect resources.
Routing Detour
A less-direct physical route that may be required when preferred routing resources are unavailable or congested.
Congestion → Detours
Congestion can force nets to use less-direct physical paths.
Congestion → Increased Routing Delay
Routing detours and difficult paths caused by congestion can increase communication delay.
Congestion → Timing-Closure Difficulty
Congested routing can make satisfying timing requirements more difficult.
Severe Congestion
Can make routing itself difficult because available interconnect in the required regions is limited.
Routability
The ability of the implementation to successfully realize the required logical connections using the FPGA's available physical routing resources.
Physical Resource Concentration
Where cells and their required connections are concentrated can affect implementation difficulty even when total utilization is acceptable.
Resource Utilization Percentage
Describes how much device capacity is consumed, but does not completely describe how difficult the design will be to place and route.
Utilization ≠ Physical Ease
A design can fit numerically within FPGA capacity while still being physically awkward to place or route.
Capacity
Asks whether the FPGA contains enough resources for the design.
Geography
Asks whether those resources and their required connections can be physically organized effectively.
Capacity vs Routability
A design having enough total resources does not guarantee that its required physical connections will route conveniently.
Placement Pressure
Physical difficulty caused by trying to assign required resources into suitable device regions under competing constraints.
Routing Pressure
Physical difficulty caused by many nets competing for available interconnect.
Fanout vs Congestion
Fanout concerns one source distributing to many loads; congestion concerns many nets competing for limited routing resources in a region.
Distance, Fanout, and Congestion
Three physical communication factors that can make an implemented connection more expensive than its RTL description suggests.
Operation, SignedMode, and Execute-Related Controls
Examples from the ATHENA arithmetic engine of signals whose broad distribution is worth investigating after implementation.
Physical Distribution Matters
A signal's Boolean function may be simple while the physical task of delivering it throughout the FPGA is significant.