Skip to content

Commit 74c8dbe

Browse files
tangxifanvaughnbetz
authored andcommitted
[Architecture File] Add comments for titan architecture to clarify the choice of pin equivalence
1 parent 48124bf commit 74c8dbe

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

vtr_flow/arch/titan/stratixiv_arch.timing.xml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4471,6 +4471,15 @@
44714471
<input name="control_in" num_pins="7" equivalent="full"/>
44724472
<input name="cin" num_pins="1" equivalent="none"/>
44734473
<input name="sharein" num_pins="1" equivalent="none"/>
4474+
<!-- Stratix IV does have instance equivalence only for the data_out port
4475+
where ALM outputs can be swapped to reach the most suitable pin location
4476+
for routers. However, it may require significant changes to packing results
4477+
which is not supported yet.
4478+
Therefore, we assume full equivalence here, so that ALM outputs can be swapped
4479+
through a local routing architecture without changing packing results.
4480+
Please note that this may cause optimistic routing results, being
4481+
better in routability than what actual hardware can support
4482+
-->
44744483
<output name="data_out" num_pins="40" equivalent="full"/>
44754484
<output name="cout" num_pins="1" equivalent="none"/>
44764485
<output name="shareout" num_pins="1" equivalent="none"/>

0 commit comments

Comments
 (0)