Skip to content

Commit d2d7ad1

Browse files
author
Tim Ansell
authored
Merge pull request #51 from gatecat/clarify-site-pip-usage
docs: Clarify correct usage of site PIPs
2 parents b3ab097 + 404fbec commit d2d7ad1

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

docs/device_resources.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -242,6 +242,19 @@ entered via the site port corresponding to the site pin. The first site wire
242242
in the site will be the site wire attached to the output BEL pin of the site
243243
port. From there site routing continues per above.
244244

245+
It is important to note that site PIPs can only be used to access placed cells
246+
inside that site. Site PIPs cannot be used as general route-thrus, to route
247+
from site input to output. General route-thrus across entire sites should use
248+
tile pseudo PIPs as described below - even if a site pin is being validly used
249+
for one sink pin of a net that is located inside the site; site PIPs cannot
250+
also be used to leave the site again to reach other sinks.
251+
252+
LUT route-thrus, for example, might require both site PIPs and tile pseudo
253+
PIPs. The site PIP would be used to route through the LUT in order to access
254+
an associated flipflop input inside the site. The tile PIP would be used to
255+
route across the entire site as part of the general, inter-tile, routing
256+
problem.
257+
245258
![Wire and nodes](https://symbiflow.readthedocs.io/projects/arch-defs/en/latest/_images/rrgraph-wire.svg)
246259

247260
### Tile Types and site types

0 commit comments

Comments
 (0)