You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Why do the enclosures have to be square ?
In #5 I now computed the enclosures so that the width of the metal generated by the via is the same as the routing gauge wire width in the routing direction. The other enclosure I still keep to the minimum one provided by the design rules. Is this enough ?
Problem with direct patches to these files is that these are auto-generated out of the design rules so such a patch will be overwritten the next time I generate the Coriolis files.
The enclosure of the VIA in the non-perpandicular direction should be so that the whole metal width is equal to the wire width in said metal in the non-preferred direction.
It is the VIA non-prefered extension size which is used to compute the space occupied by the segment at it's end.
So if it is smaller than the non-perpandicular wire half-size, either the router cannot complete or you get DRC
violation.
And my psycho-rigid self likes squares shapes, easier to visually debug.
I understand about non patching generated file, but I wanted to provide you with an example of what I did
patch. What would be your preferred way of communication for the next time?
Reason I use minimal enclosure is to allow two contact next to each other. If I am remember correctly I compute the pitch of the perpendicular wire and the enclosure in such a way that you can have two via on different nets next to each other.
I understand about non patching generated file, but I wanted to provide you with an example of what I did
patch. What would be your preferred way of communication for the next time?
It's fine, just wanted to explain why I did not apply the full patch as is.
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
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
2 participants
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.
The
decap_w1still have DRC issues undermagic, so I wasn't able to confirm the DRC.Otherwise, with the latest Coriolis commits it should complete.