X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 12912 DOT 74196 DOT bm AT omp1017 DOT mail DOT ne1 DOT yahoo DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1343165449; bh=P9BFEG+8y4v7MF2NfC9+MyDeVkz7hzV612ACEn+f/7s=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=C123F4LzavOvDoDA9OSOgFo0wHSnCH6nwgOJquq6M9DgMbyzBEBemuPyEtKMY3HeqWZrtsH20dRU6tWIyRpPxBjbrD3RPq440XvLKIBUicu7wIGM3rwrLRmtzqpmE7IIDXB5K5lZPCgZlrim1p9Dn3/nvmCGtxE9DHiTiSgNoFE= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=pIvaK6KTgXQHAZ2feyQN649/QZp+R8lPmYTHJvoApeDhVJBXE66HxPCYnFjYsH/PH0FkumViiokK7TQhFgCOOda2UBqa4Fj79+9ujEwbrZGYzpieJtmysxEMM15fEo9yXa5hfGVurX5KNis1Ng6hsfC02ogIS1YyR4QnPdIvud4=; X-YMail-OSG: 8Cz_suMVM1mor5Qzl8fzIvuYa_xAwlh81aZgbXrSoY_o6dD IY2h6Ku3GeBQikDWURhHK2Gt_u0OC36bWTKk7U_gecEtENobfisHehHMTcL0 CM4s08pQsyKJ9lKRl6_EvW7HVe7rBqVkoejIcgkMg3ehkZwsQipydouuwu9r gorQC8.7x5oeh._shWytEwLLHpwFsAKyABtuR.FnDIQm8wtijua0KCspc1oF tFr.cZnVEVIW0DzypXLYaW6PyU11ZMgQkduLjDg_oDdJllpCyb6kx_AOgHGZ t8BU2Bq9vmKMjS7NTOaq5h7W1UFKGTGtXJABB5e.sPIIGeBvmhn1jvgLY5LM YqthVEtdvWBNihjXJ448aHJckYyiyP_r_JWOExAiZTsnsum4hLkSP9uCrb.B 1GvW.OA0jEwIkkOiIAr98dBmAzoW7gNY1q.1_CTlpclE2k4.8xVkpvD5mrxR G_p7ZELMFwLTvSExGB.wSKY5m2UKBJXo9vlG4zI01AgR1jMZtNPehxxIf89C ojb3pxEGOzRF8iTB32A-- X-Mailer: YahooMailWebService/0.8.120.356233 References: <20120709210244 DOT 60387819FB92 AT turkos DOT aspodata DOT se> <20120724143816 DOT E52AD81A00CD AT turkos DOT aspodata DOT se> <1343145903 DOT 52830 DOT YahooMailNeo AT web120701 DOT mail DOT ne1 DOT yahoo DOT com> <20120724182748 DOT AA97C8279F6D AT turkos DOT aspodata DOT se> Message-ID: <1343165449.9752.YahooMailNeo@web120704.mail.ne1.yahoo.com> Date: Tue, 24 Jul 2012 14:30:49 -0700 (PDT) From: Edward Comer Subject: Re: [geda-user] Yet another sym file generator To: "geda-user AT delorie DOT com" In-Reply-To: <20120724182748.AA97C8279F6D@turkos.aspodata.se> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="1167350687-811905639-1343165449=:9752" 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 --1167350687-811905639-1343165449=:9752 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Karl,=0A=0AMy md5sum for=A0stm32f100lm.pins failed, so I re-downloaded it a= nd then md5sum passed. When I ran it, this was my output:=0A=0Aecomer AT penny= royal:~/pcb_projects/diy-symbol/pintosym$ ./pintosym.pl stm32f100lm.cmd=0Ap= rinting to stm32f100lm.adc.LQFP100.sym (adc_pins cutout r:DAC l:ADC:s w:8)= =0AUse of uninitialized value in concatenation (.) or string at ./pintosym.= pl line 886.=0AUse of uninitialized value in concatenation (.) or string at= ./pintosym.pl line 886.=0Aprinting to stm32f100lm.adc.LQFP48.sym (adc_pins= cutout r:DAC l:ADC:s w:8)=0AUse of uninitialized value in concatenation (.= ) or string at ./pintosym.pl line 886.=0AUse of uninitialized value in conc= atenation (.) or string at ./pintosym.pl line 886.=0Aecomer AT pennyroyal:~/pc= b_projects/diy-symbol/pintosym$=A0=0A=0AIn that directory I now see some ve= ry attractive sym files with simulated tear marks at the top and bottom, na= med=A0stm32f100lm.adc.LQFP100.symand =A0 stm32f100lm.adc.LQFP48.sym, which = I assume are two parts of the same chip. I have only been=A0peripherally=A0= following the conversation about breaking up a complex chip in this way so = as to make the schematic more readable. Will gschem and gsch2pcb correctly = handle these two symbols as a single chip in PCB??=0A --1167350687-811905639-1343165449=:9752 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable
Karl,
=
My md5sum for stm32f100lm.pins failed, so I re= -downloaded it and then md5sum passed. When I ran it, this was my output:

ecomer AT pennyroyal:~/pcb_= projects/diy-symbol/pintosym$ ./pintosym.pl stm32f100lm.cmd
print= ing to stm32f100lm.adc.LQFP100.sym (adc_pins cutout r:DAC l:ADC:s w:8)
Use of uninitialized value in concatenation (.) or string at ./pintos= ym.pl line 886.
Use of uninitialized value in concatenation (.) o= r string at ./pintosym.pl line 886.
printing to stm32f100lm.adc.LQ= FP48.sym (adc_pins cutout r:DAC l:ADC:s w:8)
Use of uninitialized= value in concatenation (.) or string at ./pintosym.pl line 886.
= Use of uninitialized value in concatenation (.) or string at ./pintosym.pl = line 886.
ecomer AT pennyroyal:~/pcb_projects/diy-symbol/pintosym$&n= bsp;

In that director= y I now see some very attractive sym files with simulated tear marks at the= top and bottom, named stm32f100lm.adc.LQ= FP100.sym and   stm32f100lm.adc.LQFP48.sym, which I assume are two parts of the same chip. I have only been&nbs= p;peripherally following the c= onversation about breaking up a complex chip in this way so as to make the = schematic more readable. Will gschem and gsch2pcb correctly handle these tw= o symbols as a single chip in PCB??

<= /div> --1167350687-811905639-1343165449=:9752--