Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Importing cell timings from prjxray-db #147

Open
wants to merge 18 commits into
base: master
Choose a base branch
from

Conversation

mkurc-ant
Copy link
Collaborator

@mkurc-ant mkurc-ant commented Mar 10, 2022

This PR continues the work towards timing driven routing by importing cell timings from prjxray-db to device resources database of a 7-series device.

Cell timings are stored in SDF format in prjxray-db. The patching script reads them using the python-sdf-timing library and populates the data to the device resources structures. Since cell names and instances in those SDF files do not correspond one-to-one with the architecture a manual mapping is needed. For this purpose a JSON file is used which contains the mapping.

The mapping in this PR considers only most common cell types like those inside SLICE. Timings for others are either not mapped or not present in prjxray-db.

The timing importer does not consider routing BEL timings yet.

gatecat and others added 18 commits February 17, 2022 17:48
…ks for "regular" cell-bel pin maps, not yet for parameter pins.

Signed-off-by: Maciej Kurc <[email protected]>
…ly for BEL pins mentioned in a map.

Signed-off-by: Maciej Kurc <[email protected]>
…t to the cell instance spec

Signed-off-by: Maciej Kurc <[email protected]>
…y everything for SLICEL and SLICEM

Signed-off-by: Maciej Kurc <[email protected]>
…ys to 0 (for now it seems that nextpnr won't handle eg. negative hold)

Signed-off-by: Maciej Kurc <[email protected]>
Signed-off-by: Maciej Kurc <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants