Array
(
[content] =>
[params] => Array
(
[0] => /forum/threads/should-run-1st-fill-then-edrc-waivers.6942/
)
[addOns] => Array
(
[DL6/MLTP] => 13
[Hampel/TimeZoneDebug] => 1000070
[SV/ChangePostDate] => 2010200
[SemiWiki/Newsletter] => 1000010
[SemiWiki/WPMenu] => 1000010
[SemiWiki/XPressExtend] => 1000010
[ThemeHouse/XLink] => 1000970
[ThemeHouse/XPress] => 1010570
[XF] => 2021770
[XFI] => 1050270
)
[wordpress] => /var/www/html
)
Guests have limited access.
Join our community today!
Join our community today!
You are currently viewing SemiWiki as a guest which gives you limited access to the site. To view blog comments and experience other SemiWiki features you must be a registered member. Registration is fast, simple, and absolutely free so please, join our community today!
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Should run 1st Fill then EDRC Waivers?
- Thread starter Aousafur
- Start date
gaetan_arrive
New member
I guess both should work as Fill isn't expected to create new violations. That said, running Waivers first is a good way to check it.
Actually, I'd consider Waivers as an alternative to close a layout from a DRC standpoint. You typically run Fill once your layout is DRC clean (but density rules), then typically check it's still clean after Fill (now including density rules). Following the same approach suggests running Waivers first (and ignoring density violations). Basically, the same rationale could apply to the whole hierarchical bottom-up design flow: close a cell with fixing/waiving, instanciate it, and so on... Ultimately Fill appears as the last step of the design flow; it may also require further waiving to pass final DRC... but waiving of density rules only, anything else would be questionable.
My 2c.
Actually, I'd consider Waivers as an alternative to close a layout from a DRC standpoint. You typically run Fill once your layout is DRC clean (but density rules), then typically check it's still clean after Fill (now including density rules). Following the same approach suggests running Waivers first (and ignoring density violations). Basically, the same rationale could apply to the whole hierarchical bottom-up design flow: close a cell with fixing/waiving, instanciate it, and so on... Ultimately Fill appears as the last step of the design flow; it may also require further waiving to pass final DRC... but waiving of density rules only, anything else would be questionable.
My 2c.