X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.98.4 at av01.lsn.net
Subject: Re: [geda-user] ideas on slotting and mechanisms for
 grouping/associating heterogenous symbols.
To: geda-user AT delorie DOT com
References: <CAM2RGhS4L-ch6FEcLtdSt0vA0BdQZvq+AuFDP+9ea7Ftd=AALg AT mail DOT gmail DOT com>
 <8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com>
 <alpine DOT DEB DOT 2 DOT 00 DOT 1512300544550 DOT 9035 AT igor2priv>
 <87FC7D4C-157A-499E-8B93-97653D6A7C68 AT noqsi DOT com>
 <alpine DOT DEB DOT 2 DOT 11 DOT 1601012231450 DOT 1728 AT newt>
 <AE52C1DB-01A3-43FA-AE8E-68AD33F37180 AT noqsi DOT com>
 <624E6A69-62CE-4FCB-9D44-9FDF036254A3 AT sbcglobal DOT net>
 <56880043 DOT 7040003 AT ecosensory DOT com>
 <20160102182739 DOT 5d195829880cf75768ae0a82 AT gmail DOT com>
 <201601021755 DOT u02HtOWs020325 AT envy DOT delorie DOT com>
 <20160102191018 DOT 5e68c0c4ecc70a49bd9998f6 AT gmail DOT com>
 <201601021816 DOT u02IGHCC021127 AT envy DOT delorie DOT com>
From: John Griessen <john AT ecosensory DOT com>
Message-ID: <568817CC.7090207@ecosensory.com>
Date: Sat, 2 Jan 2016 12:32:44 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Icedove/38.4.0
MIME-Version: 1.0
In-Reply-To: <201601021816.u02IGHCC021127@envy.delorie.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 01/02/2016 12:16 PM, DJ Delorie wrote:
> Should this be something you can do in the layout program?
>
> If so, how do you specify "that gate" in the schematic when you want
> to make an as-built?

Yes.  As in my proposed idea that I will now call "pinswap by attribs and pinswap file"     :


I would use a separate script to process pin swaps that utilizes a pinswap number attribute that is
not part of symbols as they are in the library, but added when you need it.  There could be a pinswap file added with same symbol 
name and a .pinswap ending on it.  The pinswap file would come from FPGA tables of pin uses in datasheets that are 1000 pages 
long.  The pinswap file would not be embedded in a standard symbol, just kept as a file next to it.  Each pin that has pinswap 
attrib would have pinswap=2 or pinswap=771, but not  any lists of variants allowed -- that would be the job of a script or backend 
to assign from the .pinswap data file.

The meaning of the pinswap attrib on a pin would be: "Assign the internal function of this defined pin of this IC to the physical 
pin number of this pinswap attrib.  For example use U7.  If a pin has pinnumber=669 and pinswap=771, the generated netlist for the 
design net that connects would have U7-771 in the list for that net.

The function names for pinswaps will not always be the same, (like they were for old fashioned slotting of quad gates), so a way 
to suppress showing the functional name on a symbol would be a good idea, and instead use a name form an attrib associated with 
pinswap attrib.   I'd start using a new attrib pinfunction that is always created and added to a symbol by a pinswap script and 
never in a standard symbol.  When it is there, set visibility of pinname to off and visibility of pinfunction to on.


To add doing steps in layout:

output a .net.aslo netlist file to compare with.  Add a feature to use it to gschem.  Perhaps since the ratlist is shown in a 
color, the imported .net.aslo netlist connections could be shown in a different color as a visual check, the accepted as "the 
netlist"  to use to show yellow ratlines.