X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Message-ID: <1382902615.28349.5.camel@pcjc2lap> Subject: Re: [geda-user] Power to ICs with numslots > 1 From: Peter Clifton To: geda-user AT delorie DOT com Date: Sun, 27 Oct 2013 19:36:55 +0000 In-Reply-To: References: <201310261908 DOT r9QJ8Vv8025803 AT envy DOT delorie DOT com> <526C9628 DOT 7000201 AT sonic DOT net> <1382899880 DOT 21120 DOT 7 DOT camel AT pcjc2lap> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.4-0ubuntu1 Mime-Version: 1.0 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 Sun, 2013-10-27 at 23:36 +0430, James Jackson wrote: > Thank you for your reply. I have found a 'cludge' solution - if I give > all my subcircuits the same refdes, then all the merging happens > correctly. Seems a pretty dirty way of doing it, though... > > > The hierarchy really just allows me to have one master schematic from > which I can move around all others in the design easily. The circuit > is a stereo audio application, so each circuit (of which there are > six) will be used at most twice, and I don't have many signals moving > between subcircuits (five at most). I that case, try removing the sub-circuit names entirely. (Remove the "refdes=X?" attribute from your instances, it should give you the navigation you want without the X1/... prefix to everything. > I think my options are boiling down to: > > > 1. Keep the hierarchy, with the cludgy subcircuit naming described > above > 2. Keep the hierarchy, but route power signals explicitly to each > subcircuit > 3. Get rid of the hierarchy, and pass multiple schematic names to > gsch2pcb 1 is possible, but might bite you in the longer term. 2 is normal for hierarchy. 3 is normal for flat schematics. For 1, assuming you are not using hierarchy to multiply instantiate the same schematic - rather, using it to help navigating an otherwise flat schematic, try this: In your project folder, create a file called "gnetlistrc" (or perhaps "gafrc", depending on your exact version of gEDA?), in this place: ; Controls if net names are mangled to make them uniq when traversing ; down into the hierarchy. If this is disabled then the net names are not ; changed and it is the user's responsibility to make sure they are unique. ; If you disable this, you really are taking your netlist's life into your ; own hands. This basically has the effect of making all same named nets ; in the entire hierarchy be electrically connected. Hope you know what you ; are doing. ; (hierarchy-netname-mangle "disabled") There is also the option: ; hierarchy-uref-mangle string ; ; Controls if uref names are mangled to make them uniq when traversing ; down into the hierarchy. If this is disabled then urefs are not changed ; and it is the user's responsibility to make sure they are unique. ; If you disable this, you really are taking your netlist's life into your ; own hands. You *MUST* have unique urefs throughout the entire hierarchy ; or bad things might happen. Also you cannot reuse underlying schematics. ; (hierarchy-uref-mangle "enabled") ;(hierarchy-uref-mangle "disabled") But I'd recommend trying removing the refdes= from your sub-circuit instantiation first, as if that works, it saves breaking the hierarchy system completely. Peter -- Peter Clifton Clifton Electronics