Skip to content

Commit

Permalink
Merge pull request #51 from gatecat/clarify-site-pip-usage
Browse files Browse the repository at this point in the history
docs: Clarify correct usage of site PIPs
  • Loading branch information
mithro committed May 9, 2021
2 parents b3ab097 + 404fbec commit d2d7ad1
Showing 1 changed file with 13 additions and 0 deletions.
13 changes: 13 additions & 0 deletions docs/device_resources.md
Original file line number Diff line number Diff line change
Expand Up @@ -242,6 +242,19 @@ entered via the site port corresponding to the site pin. The first site wire
in the site will be the site wire attached to the output BEL pin of the site
port. From there site routing continues per above.

It is important to note that site PIPs can only be used to access placed cells
inside that site. Site PIPs cannot be used as general route-thrus, to route
from site input to output. General route-thrus across entire sites should use
tile pseudo PIPs as described below - even if a site pin is being validly used
for one sink pin of a net that is located inside the site; site PIPs cannot
also be used to leave the site again to reach other sinks.

LUT route-thrus, for example, might require both site PIPs and tile pseudo
PIPs. The site PIP would be used to route through the LUT in order to access
an associated flipflop input inside the site. The tile PIP would be used to
route across the entire site as part of the general, inter-tile, routing
problem.

![Wire and nodes](https://symbiflow.readthedocs.io/projects/arch-defs/en/latest/_images/rrgraph-wire.svg)

### Tile Types and site types
Expand Down

0 comments on commit d2d7ad1

Please sign in to comment.