You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -41,33 +41,34 @@ A graphical window will now pop up when you run VPR.
41
41
42
42
Navigation
43
43
----------
44
-
* Click on the **Zoom-Fit** button to get an over-encompassing view of the FPGA architecture.
44
+
* Click on the **ZoomFit** button to get an over-encompassing view of the FPGA architecture.
45
45
* Click and drag with the left mouse button to pan the view, or scroll the mouse wheel to zoom in and out.
46
-
* Click on the **Window** button, then on the diagonally opposite corners of a box, to zoom in on a particular area.
46
+
* Click on the **Zoom Select** button, then on the diagonally opposite corners of a box, to zoom in on a particular area.
47
47
* Click on **Save** under the **Misc.** tab to save the image on screen to PDF, PNG, or SVG file.
48
-
* **Done** tells VPR to continue with the next step in placing and routing the circuit.
48
+
* **Next Step** tells VPR to continue with the next step in placing and routing the circuit.
49
49
50
50
51
51
.. note:: Menu buttons will be greyed out when they are not selectable (e.g. VPR is working).
52
52
53
-
Visualizing Placement
53
+
Placement
54
54
--------------------------------
55
55
By default VPR's graphics displays the FPGA floorplan (block grid) and current placement.
56
56
57
57
.. figure:: ../Images/Overall_view.png
58
58
:align:center
59
-
:height:300
59
+
:width:50%
60
60
61
61
FPGA floorplan (block grid)
62
62
63
63
If the **Placement Macros** drop down is set, any placement macros (e.g. carry chains, which require specific relative placements between some blocks) will be highlighted.
To visualize nets, first enable the **Display Nets** switch under the **Net** Tab.
73
74
@@ -78,6 +79,7 @@ The Inter-Cluster Nets and Intra-Cluster Nets options allow the user to choose w
78
79
79
80
.. figure:: ../Images/Net_Settings.png
80
81
:align:center
82
+
:width:25%
81
83
82
84
Net Tab
83
85
@@ -86,47 +88,48 @@ Multiple nets can be highlighted by pressing ctrl + mouse click.
86
88
87
89
.. figure:: ../Images/show_nets.gif
88
90
:align:center
91
+
:width:100%
89
92
90
93
Visualizing Nets
91
94
92
95
When the **Highlight Block Fan-in and Fan-out** option is enabled, clicking on an internal block will draw its fan-in, fan-out, and internal flylines in blue, red, and yellow, respectively.
93
96
94
97
.. figure:: ../Images/highlight_flylines.png
95
98
:align:center
99
+
:width:50%
96
100
97
101
Highlight Block Fan-in and Fan-out Flylines
98
102
99
103
Clicking on a clb (not the internal physical blocks) will also highlight all the fan-in and fan-out routed nets in blue and red, respectively.
100
104
101
-
Visualizing the Critical Path
105
+
Critical Path
102
106
-----------------------------
103
-
During placement and routing you can click on the **Crit. Path** drop-down menu under the **Misc.** tab to visualize the critical path.
107
+
During placement and routing you can click on the **Display Critical Path** switch under the **Net** tab to visualize the critical path.
104
108
Each stage between primitive pins is shown in a different colour.
105
109
106
110
.. figure:: ../Images/crit_path.png
107
111
:align:center
108
-
:height:200
112
+
:width:100%
109
113
110
-
Crit. Path drop-down list under the Misc. tab
111
-
112
-
The **Crit. Path** drop-down will toggle through the various visualizations:
114
+
Critical Path with all options enabled.
113
115
114
116
* During placement the critical path is shown only as flylines.
115
117
* During routing the critical path can be shown as both flylines and routed net connections.
Critical Path flylines during placement and routing
121
124
122
-
Visualizing Routing Architecture
125
+
Routing Architecture
123
126
--------------------------------
124
127
125
128
During the route stage, the **Route** tab provides various options to visualize router resources and statistics.
126
129
127
130
.. figure:: ../Images/Routing_Options.png
128
131
:align:center
129
-
:height:300
132
+
:width:25%
130
133
131
134
Routing Options
132
135
@@ -140,6 +143,7 @@ Multiple routing resources can be highlighted by pressing ctrl + mouse click.
140
143
141
144
.. figure:: ../Images/show_rr_graph.gif
142
145
:align:center
146
+
:width:100%
143
147
144
148
Visualizing Routing Architecture
145
149
@@ -177,52 +181,51 @@ The points at which wiring segments connect to clb pins (connection box switches
177
181
178
182
Switch box connections will have buffers (triangles) or pass transistors (circles) drawn on top of them, depending on the type of switch each connection uses.
179
183
180
-
Visualizing Routing Congestion
184
+
Routing Congestion
181
185
------------------------------
182
186
When a routing is shown on-screen, clicking on the **Congestion** drop-down menu under the **Routing Options** tab will show a heat map of any overused routing resources (wires or pins).
183
187
Lighter colours (e.g. yellow) correspond to highly overused resources, while darker colours (e.g. blue) correspond to lower overuse.
184
188
The overuse range shown at the bottom of the window.
When a routing is shown on-screen, clicking on the **Routing Util** drop-down menu will show a heat map of routing wire utilization (i.e. fraction of wires used in each channel).
194
199
Lighter colours (e.g. yellow) correspond to highly utilized channels, while darker colours (e.g. blue) correspond to lower utilization.
During placement and routing you can adjust the level of block detail you visualize by using the **Toggle Block Internal** option under the **Block Settings** tab.
209
+
During placement and routing you can adjust the level of block detail you visualize by using the **Block Internal** option under the **Block** tab.
204
210
205
211
.. figure:: ../Images/Block_Settings.png
206
212
:align:center
207
-
:height:300
213
+
:width:100%
208
214
209
215
Block Settings
210
216
211
217
Each block can contain a number of flip flops (ff), look up tables (lut), and other primitives. The higher the number, the deeper into the hierarchy within the cluster level block you see.
218
+
The format of the internal block names is <block_type_name>[<placement_index>]:<mode_name>.
The view menu is displayed when vpr is targeting a stacked multi-die architecture (more than 1 layer).
228
+
The layers dropdown is displayed when vpr is targeting a stacked multi-die architecture (more than 1 layer).
226
229
Layers are drawn in ascending order for many drawing features (e.g. blocks); that is layer 0 is drawn first, and (if visible), layer 1 is drawn on top of it etc.
227
230
The visibility and transparency of a layer can be changed, which will affect blocks, nets, routing, and critical path.
228
231
Cross-layer connections refer to connections that are in different layers.
@@ -307,26 +310,28 @@ The manual moves feature allows the user to specify the next move in placement.
307
310
308
311
.. figure:: ../Images/manual_move.png
309
312
:align:center
310
-
:height:200
313
+
:width:25%
311
314
312
315
Misc. Tab
313
316
314
317
To enable the feature, activate the **Manual Move** toggle button under the **Misc.** tab and press Done. Alternatively, the user can activate the **Manual Move** toggle button and click on the block to be moved.
On the manual move window, the user can specify the Block ID/Block name of the block to move and the To location, with the x position, y position and subtile position. For the manual move to be valid:
320
324
321
325
- The To location requested by the user should be within the grid's dimensions.
322
326
- The block to be moved is found, valid and not fixed.
323
327
- The blocks to be swapped are compatible.
324
-
- The location choosen by the user is different from the block's current location.
328
+
- The location chosen by the user is different from the block's current location.
325
329
326
330
If the manual move is legal, the cost summary window will display the delta cost, delta timing, delta bounding box cost and the placer's annealing decision that would result from this move.
0 commit comments