El mié, 13-09-2006 a las 22:40 +0200, Bernd Jendrissek escribió: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > A while ago I realized with horror that the same device can have > different pinouts when all that changes is the package. The specific > example I have here is of a 16C2550; in 44-pin PLCC pin 1 is in the > middle of the "top" row and is ~TXRDYA (then D0, D1, D2, etc.). In > 48-pin TQFP the pattern of pins (by function) is the same except for NC > pins in the corners, but pin 1 is in a corner and is D5 (then D6, D7, > RXB, etc.) The 40-pin DIP loses another 4 pins on the way. > How do you cleaver peoplez deal with devices coming in multiple package > formats? I glean from Wikipedia that it's probably the same piece of > silicon inside, so it's tempting to want to decide on a specific package > quite late into the design.
I think the goal could be something similar to Dan's proposal: http://archives.seul.org/geda/dev/Sep-2006/msg00037.html > I gather that "heavy footprints" are uncool, but wouldn't it be cool if, > like someone else mentioned recently (**), PCB (*) could do both, with > "light" footprints that are device-agnostic, > > (*) Maybe it is easier to do the work in gnetlist, where there is > already some ChangePinName() activity. As someone pointed out, it is very interesting to see pinnumbers in the schematic. Maybe libgeda is the right place for this kind of code? Regards, Carlos _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
