Various fixes for the magic tech file #608
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The `%d` will actually display the distance units on its own, so there is no need to have `%dum` because this will just print `0.3umum`. Signed-off-by: Sylvain Munaut <[email protected]>
There are no DRC rules against it. Signed-off-by: Sylvain Munaut <[email protected]>
Signed-off-by: Sylvain Munaut <[email protected]>
Fixes IHP-GmbH#400 Signed-off-by: Sylvain Munaut <[email protected]>
Without theses it's possible to put the guard ring too close to the poly extension and end up with pSD.i/pSD.j violations that are not reported by magic DRC. Credits to Tim Edwards for writing the rule live in fossi chat :) Signed-off-by: Sylvain Munaut <[email protected]>
It wouldn't consider 'via6' as forming connections between area of 'm6' Credits to Tim Edwards for writing the rule live in fossi chat :) Signed-off-by: Sylvain Munaut <[email protected]>
* The mimcc is defined as `squares-grid 360 420 420`, so the drawn area includes a 0.36u border all around already which corresponds to MIM.d * This means the current 'surround' rule is wrong because it forces an additional 0.26u around which is not needed. And there is in fact no need for a surround rule at all. * The minimum width becomes 1.14u which is the TopVia1 width given by TV1.a (0.42u) and twice the MIM.d border (0.36u). Also the layer was wrong * The spacing rule is also irrelevant since the minimum spacing is 0.42u but independent zone will include a 0.36u border so two independent zone will always be DRC valid. * The surround rule was referring to the wrong metal layer and also need to be adapted since TopMetal1 (m6) must surround by 0.42u (TV1.d) but 0.36u of that is already included. That surround rule is also non-directional, it must be all around. * Fix the m5/m6 typo in exact_overlap rule Signed-off-by: Sylvain Munaut <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes several fixes for the magic tech file.
Created as a draft until @RTimothyEdwards gets a chance to review / validate those.