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

Get info about packages/pins from the IDE files. #57

Merged
merged 6 commits into from
Nov 6, 2021

Conversation

yrabbit
Copy link
Collaborator

@yrabbit yrabbit commented Nov 4, 2021

Signed-off-by: YRabbit rabbit@yrabbit.cyou

Signed-off-by: YRabbit <rabbit@yrabbit.cyou>
@yrabbit
Copy link
Collaborator Author

yrabbit commented Nov 4, 2021

Well, we'll see how the CI goes. Should break on examples because nextpnr is old, but it will create bases.

"device": "GW1N-4-PBGA256-6",
"partnumber": "GW1N-LV4PG256C6/I5",
},
"GW1N-1": {
"package": "LQ144",
"package": "LQFP144",
"header": 1, # stupid note in excel
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this header can go

return (pkgs, res, res_bank_pins)

# returns ({partnumber: (package, device)}, {pins}, {bank_pins})
def xls_pinout(device):
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe this shouldn't be called xls when it's not excel based ;)

@pepijndevos
Copy link
Member

Exactly as predicted! So what's up with the nextpnr side? I mean, isn't the chipdb format the same?

@@ -147,6 +147,17 @@ def write_timing(b, timing):
b.u32(len(timing))
b.ref(blk)

def write_partnumber_packages(b, db):
import ipdb; ipdb.set_trace()
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

uh breakpoints should go I think haha

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exactly as predicted! So what's up with the nextpnr side? I mean, isn't the chipdb format the same?

The structure has changed: a table with packages has been added.
You can put the next patch on nexpnr

yrabbit/nextpnr@0e8a299

Signed-off-by: YRabbit <rabbit@yrabbit.cyou>
Signed-off-by: YRabbit <rabbit@yrabbit.cyou>
Signed-off-by: YRabbit <rabbit@yrabbit.cyou>
@yrabbit
Copy link
Collaborator Author

yrabbit commented Nov 5, 2021

The speed is determined from the partnumber, the match is stored in the database so the input regular expression is simplified and allows more models:)

Of course this is only friendly with the last commit for nextpnr: yrabbit/nextpnr@74b4f69

@pepijndevos
Copy link
Member

Looks good to me!

@pepijndevos
Copy link
Member

Wait actually if this is an incompatible bba change it should bump the DB version

@pepijndevos
Copy link
Member

b.u32(0) # version

Signed-off-by: YRabbit <rabbit@yrabbit.cyou>
examples/Makefile Outdated Show resolved Hide resolved
Signed-off-by: YRabbit <rabbit@yrabbit.cyou>
@pepijndevos pepijndevos merged commit f3c22dd into YosysHQ:master Nov 6, 2021
@yrabbit yrabbit deleted the json branch November 6, 2021 15:55
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