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/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to; bh=TkZcg2WVxMe8MNFsw/3rqg6aZ02MRsB0hyIVs6oYbO4=; b=l3KvExJvsda9SrWl8c+ZkjlhQEbzKYFOXxKW0JLgG8U88pxQhXdfilfg3kAcLnYTPQ UNN4Lk+Ugk0txY05JLAgFBZZDzqraGI0OdUTh4RJRgYL6ugc0KFJlUSYIo6246mteBE6 2tAcvFANQPAxSM47GQ8hVH4UEHHXPgI6o4LS/hgEWtZ+l4UizHNdYJJhcoSkBepM0dWC ltLnCemGQTwJ8sGIb2b3ZqnMIVNIu7CwdRKIfT1txROa76SDJXdN+sh7SNbTqlYGzBLV kuNy/13f9UUjH4CYRxCNGSdHvGolTAlokWq0ZQLDMgSvirvAbEg7DpkqEJhE3l4JWsOs bC/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to; bh=TkZcg2WVxMe8MNFsw/3rqg6aZ02MRsB0hyIVs6oYbO4=; b=Bgz+3G1qldPU8NGFuaTbCwavKrsOpvFpqokd+LSKMV8XIYAxQ7+qVHDMm5cRdvTSiy OEjRNlEIVhLTKGaCuv0t/wsiyJpqSwHiely/dYadZxvDhJ2AhmwkD/acb75uppDeLXlM qWFmP6jHlkezaFhKuUqVSzDeQTwy24xEC0U37zm8jBqEXVrTQCPmxcFBUUxC0zOkhtU6 fggjZsexiL5m51oYz95ELFKP7zDBfhBh2gqAAr42iTRh0mmgNyJ/idoCRT7jqBOfHCAM rZFemt5RdC3zDeP5FDHlaggkUCwJGoGTQe9NfZOreY1yD+kk9hop3N4r6WtBWf+o82mn TlgQ== X-Gm-Message-State: AIVw110yvWkGV5hjIxs5f3oQymQKiMIY5a/6Ls3Ak7HntFnzhl81TNCe Y+KAiSheCQbyr+GXqKStBMWjp7dGUxjT X-Received: by 10.84.254.10 with SMTP id b10mr8535736plm.442.1501975825846; Sat, 05 Aug 2017 16:30:25 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: "Chris Fisichella (christopher DOT j DOT fisichella AT gmail DOT com) [via geda-help AT delorie DOT com]" Date: Sat, 5 Aug 2017 19:30:25 -0400 Message-ID: Subject: Re: [geda-help] help with 71 pin element To: geda-help AT delorie DOT com Content-Type: multipart/alternative; boundary="f403045fff568f9788055609ff73" 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 --f403045fff568f9788055609ff73 Content-Type: text/plain; charset="UTF-8" Hi DJ, Thank you very much for the prompt reply.I was reading the gschem documentation , and it says the pinseq needs to be a number. The pinnumber can be alphanumeric. That's what I did in my symbol fp file. I did find a mistake in the regulator symbol file . There should be no "L71" thanks for catching that. It's just an alphanumeric grid with letters for rows and numbers for columns. I fixed the pinnumber mistakes and can see pinname is "unknown-2" It seems to be looking for a pinsequence. I ran gschlas -e and got this file . I don't see why my schematic symbol is not working with this footprint. In 170804_RegulatorSchematic, I can see the pins have pinnumber assigned as "K7" and pinsequence assigned a positive integer. I ran through gsch2pcb and still, nothing gets attached to that regulator. I am noticing some of the library symbols do not use alphanumeric pinnumbers. Perhaps I should also do that? Best, Chris On Fri, Aug 4, 2017 at 8:43 PM, DJ Delorie wrote: > > Your schematic doesn't have the symbols embedded (gschlas -e foo.sch) so > we can't see what the schematic has for pin numbers. > > Note that the symbol must have the *numbers* (1..71) not the name > (A1..L71), unless you change the .fp file to have A1..L71 in the numbers > field. > > Importing the schematic into the pcb will replace the "name" field with > the pinnames from the schematic, so they end up with names like "ENABLE" > or "BUS4" or "PWRGOOD" depending on your design. > > --f403045fff568f9788055609ff73 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi DJ,

Thank you very much for the prom= pt reply.I was reading the gschem documentation, and it say= s the pinseq needs to be a number. The pinnumber can be alphanumeric. That&= #39;s what I did in my symbol =C2=A0fp file. I did find a mistake in the r= egulator symbol file. There should be no "L71" thanks for catching that. It's just= an=20 alphanumeric grid with letters for rows and numbers for columns. I fixed the pinnumber mistakes and can see pinname is "unknown-2" It see= ms to=20 be looking for a pinsequence.

I ran gschlas -e <= ;foo.sh> and got this file. I don't see why my schematic symbol= is not working with this footprint.

In 170804_RegulatorS= chematic, I can see the pins have pinnumber assigned as "K7" and = pinsequence assigned a positive integer.

I ran= through gsch2pcb and still, nothing gets attached to that regulator.

I am noticing some of the library symbols do not us= e alphanumeric pinnumbers. Perhaps I should also do that?
Best,
Chris
On Fri, Aug 4, 2017 at 8:43 PM, DJ Delorie <dj AT de= lorie.com> wrote:

Your schematic doesn't have the symbols embedded (gschlas -e foo.sch) s= o
we can't see what the schematic has for pin numbers.

Note that the symbol must have the *numbers* (1..71) not the name
(A1..L71), unless you change the .fp file to have A1..L71 in the numbers field.

Importing the schematic into the pcb will replace the "name" fiel= d with
the pinnames from the schematic, so they end up with names like "ENABL= E"
or "BUS4" or "PWRGOOD" depending on your design.


--f403045fff568f9788055609ff73--