X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f X-Recipient: geda-help AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1607428240; bh=nxHo/2+5wsCGiYy6DWCax9QuY0zAjg81sBEiKrFb5O8=; h=X-UI-Sender-Class:Subject:To:References:From:Date:In-Reply-To; b=Y3NLrZf099D6kBTmbaXYtXFP+75os+0b/bwXw/og54dMCOSLt9Hu040kdTI/W/i0r vHMTxChfnQ1IJc/qefC61z6BpuYNQcY5v+YffjE2hRr/iolCdwOKHLDVXRrME2C7Mr is+BIXKqnCgNZGG+wsWsrhg1MPUpvC+Yo67L03U8= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Subject: Re: [geda-help] using net names on multiple sub schematics used by single symbol To: geda-help AT delorie DOT com References: From: "Klaus Rudolph (lts-rudolph AT gmx DOT de) [via geda-help AT delorie DOT com]" Message-ID: <3e21c34b-571c-8762-7e68-f096bcf10a37@gmx.de> Date: Tue, 8 Dec 2020 12:50:37 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US X-Provags-ID: V03:K1:cslNiX22e4hkZQdkE4/LNMVuG1TbVleQEjISapPhe6RHtOOywzR sUE0tGLW2MxuzOdBR9vjHBd1kK3paF2k6k39KwBjQgFUhz9iVi9S9hSEvqCX0r7n9hehXIy ECImbvSlguTYs9JvcfWEg4w74vZtX95cW8bb9350NLsXD+ufjsXIk5ZbkXIdyOeDCjyOwz/ y+po6CZmg5tuk1Gm6yG3Q== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:TdCvzB9SWPU=:d8PEJsRiISn5usp7KhPNqe szTEXMcQcilRXGZ/OS5CIfpmsHY7z4g8JENHxBsOUHJF+yg3bj7XnhMbiGKyz/qWddqTq/Z5B LnpFds56BENmWAsRaxkVNTr8+5GCf5XtLrfzdHCwMnjqREgKvO5BJAmqK+tX9IWdHgaSKMpgf MxYm6ZPx4ygrkN/zesS4RFnlmSu3pdyS0olbmQ2T4g2An1RPPV+BHrTPwMQEbjjFmKZl4qGcZ JIGpGpQbqlvi143bLyRhYLfEQGtc7WH6AH7g09xilqcbCEKwHxi9QpjEk5iLgQUP8S/fgmfnu mR6tMH3CPBHePhcboq8WjqZtIKCSMymNsY08tcBFaKQ3HDFNXs0s7aYI+n2eeu8OFO1xTstyA RiU2eVDnJyZhmuchNceKto1GUrgO2eyx/mCV0fHd7h49iCuk/bCs91GB5RJyeqWMjXSk9dhij p1fmLxQcyCGVIrsr/x/HTmLwvTuIcvuau71+mvZNg1R663kCicTKoRpkcMdYqDAoIlvM10TQ+ 6rb5SVQ5uLl2WsDMqUNaJfsepaph6hc0XSa1yKTjjP3KALGR8glNM1BdF2gAJiw93D76QjpB9 PudO35/qVGnafMiT/ld2EaINyLsWNfUJOK1hSahH9zN0subo5nVN2J7ZzZUBLpogtW/BSUXsG Yh3Z6qAlnlTXIokFvmC2R4Q8DhTMrfMSSBdT9/vgBg/CDwPHeyWFdV5CyHWsJE05ENZtkjEhM lXJ2aHiueWeyPLY0oYhfwVoQLtH6N0WK6wZ/s5u0Tyx1NGWnVKZrnO6qIQF6uIZYlv25XTIBG WxHacdfvrbcYCzIyRRS8C8ZpybKui5IsFlXtYP7kKh96Z+q/HUVzsxzCkgOY3Uol+gsTAV6Dc QgtQVanrtQRkPr1KWIWg== Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id 0B8BpUTN008939 Reply-To: geda-help AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-help AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk Hi Lutz, Am 06.12.20 um 22:21 schrieb Roland Lutz: > Hi Klaus, > > On Fri, 4 Dec 2020, Klaus Rudolph (lts-rudolph AT gmx DOT de) [via > geda-help AT delorie DOT com] wrote: >> gschem supports multiple sub schematics in a single symbol, simply by >> inserting multiple "source=xxx.sch" attributes. >> >> From gschem this works fine. Pressing "S" to go into the hierarchy >> opens the first sub schematic and navigate with "page up" "page down" >> works as expected. > > yes.  This is a little-known feature which I didn't know about myself > until I found it in the sources.  I'm happy someone is actually using > it. :-) It was in the docs in the past. But I only find a old pdf http://www-mdp.eng.cam.ac.uk/web/CD/engapps/geda/geda-doc/gschem/gschem.pdf. Is there somewhere an actual one available? > >> error: net name conflict across hierarchy: net name `A2/SIG1' is used by >> net `SIG1' on page `A2/' and by net `SIG1' on page `A2/' >> error: net name conflict across hierarchy: net name `A1/SIG1' is used by >> net `SIG1' on page `A1/' and by net `SIG1' on page `A1/' > > There was an error in the way gnetlist handles package and refdes > namespaces in components with multiple subschematics.  I fixed it in the > branch `stable-1.10' on GitHub (geda-project.org appears to be down at > the moment).  You can clone it from: > >     https://github.com/rlutz/geda-gaf Great! Currently the git.geda-project.org/geda-gaf is online again. It seems that also delorie.com was removed from nameservers at the weekend. OK, no problem, add your repo as secondary remote and was able to fetch your changes. Thanks a lot!!!!! > > > BTW, port symbols aren't designed to be used with net= attributes. > There are two distinct kinds of connections between schematics: > >   (a) one net spanning multiple same-level schematics Yepp! That is quite easy, simply use the same net= attribute in the same hierarchy of the sub schematics. I checked it and it works as expected. > >   (b) the pin of a component being connected to a port in a subsheet > > Port symbols are used for case (b) while power symbols (or simply named > nets) are used for case (a). > > I'd recommend using "new-style" power and port symbols: instead of a > refdes= attribute, you can specify a single netname= or portname= > attribute which indicates the net (or port) to which the component is > connected. If I replace older refdes= to the "newer" portname= it works fine. But in which case I can/should use netname= attribute? I was not able to get an example working with using netname= It may be a good idea to share a minimal example with sub schematics which uses all of these features, even with shared / slotted devices. I did a little example this morning and run with your last changes and it works fine. Thank you very much! Klaus P.S. If you like a can share my little example and we can add the netname= attribute to this example and make that public?