Mail Archives: geda-user/2015/10/23/10:43:24
--Apple-Mail=_C38896D1-CEB0-4C40-B24A-1AA570C164D3
Content-Type: multipart/alternative;
boundary="Apple-Mail=_8F156CD8-2DA2-4CD5-AA65-A6CE23E106A6"
--Apple-Mail=_8F156CD8-2DA2-4CD5-AA65-A6CE23E106A6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
On Oct 23, 2015, at 2:29 AM, Carlos Nieves (cnieves DOT mail AT gmail DOT com) [via =
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>=20
> I=92m thinking about a bottom-up approach to detecting missing slot =
assignments and missing parts of split symbols. The standard gEDA =
footprint names are pretty good for this purpose, as they encode the pin =
count in a regular way. Some of the symbols in the gEDA library also =
have pins=3D attributes. Since I export to Allegro, and it expects the =
netlister to tell it how many pins the footprint is expected to have, I =
have to deal with this anyway. So, count pins and verify that the right =
number are present.
>=20
> The main problem with that is that it's only valid for PCB workflow, =
and depends on the footprint names... ;)
It doesn=92t depend on footprint names: the approach I=92m using for =
Allegro looks for a pins=3D attribute, and only tries to deduce pin =
count from the footprint if that=92s absent. Of course, a DRC version =
might want to check that the footprint matches, if present.
A peripheral, optional tool like a specialized DRC script doesn=92t have =
to cover every possibility. It need only be applicable to the flows for =
which it makes sense.
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_8F156CD8-2DA2-4CD5-AA65-A6CE23E106A6
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=windows-1252
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Oct 23, 2015, at 2:29 AM, Carlos =
Nieves (<a =
href=3D"mailto:cnieves DOT mail AT gmail DOT com">cnieves DOT mail AT gmail DOT com</a>) [via =
<a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] =
<<a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>>=
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><blockquote class=3D"gmail_quote" style=3D"font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: auto; text-align: start; text-indent: 0px; text-transform: =
none; white-space: normal; widows: auto; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-style: solid; border-left-color: =
rgb(204, 204, 204); padding-left: 1ex;"><div style=3D"word-wrap: =
break-word;"><br class=3D"Apple-interchange-newline">I=92m thinking =
about a bottom-up approach to detecting missing slot assignments and =
missing parts of split symbols. The standard gEDA footprint names are =
pretty good for this purpose, as they encode the pin count in a regular =
way. Some of the symbols in the gEDA library also have pins=3D =
attributes. Since I export to Allegro, and it expects the netlister to =
tell it how many pins the footprint is expected to have, I have to deal =
with this anyway. So, count pins and verify that the right number are =
present.</div></blockquote><div style=3D"font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;"><br></div><div style=3D"font-family: Helvetica; font-size: 12px; =
font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: auto; text-align: =
start; text-indent: 0px; text-transform: none; white-space: normal; =
widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">The =
main problem with that is that it's only valid for PCB workflow, and =
depends on the footprint names... =
;)<br></div></blockquote><br></div><div>It doesn=92t depend on footprint =
names: the approach I=92m using for Allegro looks for a pins=3D =
attribute, and only tries to deduce pin count from the footprint if =
that=92s absent. Of course, a DRC version might want to check that the =
footprint matches, if present.</div><div><br></div><div>A peripheral, =
optional tool like a specialized DRC script doesn=92t have to cover =
every possibility. It need only be applicable to the flows for which it =
makes sense.</div><br><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><p style=3D"margin: =
0.0px 0.0px 0.0px 0.0px"><font face=3D"Helvetica" size=3D"3" =
style=3D"font: 12.0px Helvetica">John Doty<span =
class=3D"Apple-converted-space"> <span =
class=3D"Apple-converted-space"> </span><span =
class=3D"Apple-converted-tab"> <span =
class=3D"Apple-converted-space"> </span></span></span>Noqsi =
Aerospace, Ltd.</font></p><p style=3D"margin: 0.0px 0.0px 0.0px =
0.0px"><a href=3D"http://www.noqsi.com/">http://www.noqsi.com/</a></p><p =
style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><font face=3D"Helvetica" =
size=3D"3" style=3D"font: 12.0px Helvetica"><a =
href=3D"mailto:jpd AT noqsi DOT com">jpd AT noqsi DOT com</a></font></p><br =
class=3D"Apple-interchange-newline"></span>
</div>
<br></body></html>=
--Apple-Mail=_8F156CD8-2DA2-4CD5-AA65-A6CE23E106A6--
--Apple-Mail=_C38896D1-CEB0-4C40-B24A-1AA570C164D3
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJWKkdbAAoJEF1Aj/0UKykRrL0P/jMEHElFBnGEgj432jOrG72O
X945m2Y0oKdGnjs1SUwcSQHr7slqDdlNjMUcPhj5S85CTHKbqI4GhxfDBTnDlLs7
vwup+AT5OyyL9mVYv/j+jAj/wJOhtIpRX7l21/QnCfYHt+WUBccI1T9G2RjH7eLP
k2vFRYpgyg6qWSqEHyR2q6RZSBZp/xKfRHKHsO35ybUP+8fdfQMnhB3LRY5uuYiR
cRSOxNrDjyT1Z/Qu9ppnLNJBfSSSMfS6kU4NJhGey2ILD+KG35SMXXaKksoMmZWa
+qXIL0S/rmhlNgWOsgxAT9lyPg3suW1guL0f+AWeBso1+P1qaEvoDwoJ9PQeZeev
UJieFZ79nfJbBL8xZ47b2u7DyB/wOo59RKo+rQ4EtMf6mG4GetWSXjouICUSSPh4
ZXQXoAV8dpVM3OR3fNTtRghtyUh/p49S6KYySsMKQUpDfUsTJHgAb2jeBhNUQO+s
uHPxudn22kewCbwbJObQzc1PUpaI9RRDkJ3eHBtU3d46SIEfoXGMINzjrY1M7sPI
qN7nZaWKBXDEX0KJlOJ5YmNinC+bY0vcCIHzXF/8J2ct6hCVRQkG6aYtKQQ+mBk5
y7Ys8UiE90TOEJBgB2Jv6wRTXTzdk04PNYiLG72x9Zeoc0JTo5+iIRXQhqUv8ifg
CxCvc1HNP+X0o77YqEd9
=e5wK
-----END PGP SIGNATURE-----
--Apple-Mail=_C38896D1-CEB0-4C40-B24A-1AA570C164D3--
- Raw text -