X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=XLbGM+8e/NWMA49PefbxGi44EAx50oK0sNaWB2p8APA=; b=T0tgoiLYuu9WcGQE5sDdPTzDo6XRykV7HGULFC50nZX/T03Cgg82dy1K5q8+m9xJ4w aPorrIVVn71kukGTU8CzGy2Js3y5CVMSzpF8AHCL2HM8nv+7idPggB0aFCtUQnXMuhHt TVV0GvKgGgzUw40k+N0g227+JfhaV8QMdDLwpKYD/UGbu7Uid90pLkoyPxlJcv+XQ6oc 6b89sWdg3HtiAYYZxgUZdxAWcSst09P/sM4bX2M1VqekxzKP67GlcqH70yqkJP8V6qhi cqZWM5ytnQG2lyZmJ6s6g8+nq3PtI6g5W30t2aKOyHYY2ml+fFqp8gHV+NmNkzU0i3/b fOOQ== MIME-Version: 1.0 X-Received: by 10.52.66.237 with SMTP id i13mr16783739vdt.47.1433616109146; Sat, 06 Jun 2015 11:41:49 -0700 (PDT) In-Reply-To: <1433582411.3516.69.camel@akerlind.nu> References: <1433582411 DOT 3516 DOT 69 DOT camel AT akerlind DOT nu> Date: Sat, 6 Jun 2015 10:41:49 -0800 Message-ID: Subject: Re: [geda-user] how to avoid 'Cant find PINLABEL pin1 called for in netlist'? From: "Britton Kerin (britton DOT kerin AT gmail DOT com)" To: geda-user AT delorie DOT com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t56IftPT024767 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 Sorry bad description of the problem by me. First off I meant PINLABEL to stand for the name I give the pin (e.g. OUT_5V), and the error message is actually 'pin 1' and not pin1. The error crops up during optimize in the .pcb file I use for the subcircuit. Once the subcircuit layout is imported into PCB and the refdeses changed (via a script), the error goes away, presumably because the hierarchical design flow of between gschem and PCB understands the situation and knows not to worry about those pins. The only difference I notice between your approach and mine is that you dont set pinlabel for the interface pins in the subcircuit schematic, which I doubt would make a difference (the fact that you aren't trying to make a .pcb from the subcircuit alone seems more likely to be the cause). Britton On Sat, Jun 6, 2015 at 1:20 AM, Jonatan Ã…kerlind wrote: > On fre, 2015-06-05 at 15:52 -0800, Britton Kerin > (britton DOT kerin AT gmail DOT com) wrote: >> It all works but PCB ends up complaining: >> >> 'Cant find PINLABEL pin1 called for in netlist' >> > > Do you have a "pin1" either in the subschematic symbol used in the top > level schematic, or in an IO symbol on the subschematic, that is not > connected anywhere? Would be easier to spot the error with access to the > schematics and symbols. > > I use hierarchical schematics with netlist export to pcb without such > problems. Examples can be seen here: > > https://github.com/natanoj/heatcontrol > > One simple top level schematic is this one: > https://github.com/natanoj/heatcontrol/blob/master/schem/roomunit/roomunit-psu-daughter.sch > > with one child: > https://github.com/natanoj/heatcontrol/blob/master/schem/roomunit/roomunit-poe-dcdc.sch > > and corresponding subschematic symbol in top level schematic: > https://github.com/natanoj/heatcontrol/blob/master/schem/sym/poe-dcdc.sym > > A layed out pcb of this circuit: > https://github.com/natanoj/heatcontrol/blob/master/pcb/roomunit-psu.pcb > > /Jonatan >