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.

Sign up for GitHub

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

Jump to bottom

Power straps must also know about MAXWIDTH #553

Open
harrisonliew opened this issue Dec 13, 2019 · 2 comments
Open

Power straps must also know about MAXWIDTH #553

harrisonliew opened this issue Dec 13, 2019 · 2 comments
Assignees
@harrisonliew
Labels
advanced PR medium priority Hard workaround exists, costing time/effort, chip QoL/QoR issue

Comments

@harrisonliew
Copy link
Contributor

harrisonliew commented Dec 13, 2019 •
edited
Loading

Certain technologies have MAXWIDTH in addition to LEF58_WIDTHTABLE which is now checked after #521. This denotes that the last entry in the width table is exact, not greater than or equal to. The width table checks just need to take this into account.
@harrisonliew harrisonliew added high priority No workaround exists, many people blocked, chip-breaking issues CurrentTapeout This issue is needed for an ongoing tapeout at UCB labels Dec 13, 2019
@harrisonliew harrisonliew self-assigned this Dec 13, 2019
@harrisonliew harrisonliew added medium priority Hard workaround exists, costing time/effort, chip QoL/QoR issue and removed high priority No workaround exists, many people blocked, chip-breaking issues labels Dec 14, 2019
@colinschmidt colinschmidt added advanced PR and removed CurrentTapeout This issue is needed for an ongoing tapeout at UCB labels Oct 6, 2020
@colinschmidt
Copy link
Contributor

Resolution: Stackup representation in Hammer needs to support this maxwidth parameter, power strap code needs to cap the width of straps even if the user requests larger, tool plugins may need to update their stackup dumping.

@colinschmidt
Copy link
Contributor

I ran into this issue recently, it isn't too annoying because power straps don't get setup that frequently, but would be a pretty straightforward fix I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@harrisonliew harrisonliew

Labels
advanced PR medium priority Hard workaround exists, costing time/effort, chip QoL/QoR issue
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@colinschmidt @harrisonliew