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

Broken VCC_WIRE entries in database #440

Closed
kgugala opened this issue Jan 4, 2019 · 3 comments
Closed

Broken VCC_WIRE entries in database #440

kgugala opened this issue Jan 4, 2019 · 3 comments

Comments

@kgugala
Copy link
Contributor

kgugala commented Jan 4, 2019

see f4pga/f4pga-arch-defs#314 (comment)

@mcmasterg
Copy link
Contributor

From quick discussion sounds like we never had a known good entry. Oddly there is a GND fuzzer and a VCC fuzzer. I'm guessing that these simply aren't used a lot and so hasn't been a problem until recently?

@litghost
Copy link
Contributor

litghost commented Jan 7, 2019

In the previous database, VCC entries were located in ppips as "default". See f4pga/prjxray-db@b327fb4#diff-5693698103ebe6ceff1d3b92b9a7fedb

Then in the Oct 21st update, these entries were removed: f4pga/prjxray-db@fd147ad#diff-5693698103ebe6ceff1d3b92b9a7fedb

@mcmasterg
Copy link
Contributor

I would believe that. I didn't have a good understand of these when I was refactoring things. Probably should get a code review on how these are implemented in the fuzzers. FWIW I think someone is consolidating pip fuzzer .py right now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants