X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Mailer: exmh version 2.7.2 01/07/2005 (debian 1:2.7.2-18) with nmh-1.3 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: inbox To: geda-user AT delorie DOT com Subject: Re: [geda-user] Make multiple pins auto-numbered in gschem In-reply-to: References: <20111217222833 DOT 1F99881FD929 AT turkos DOT aspodata DOT se> <20111218194622 DOT 5FFDB81FD937 AT turkos DOT aspodata DOT se> <4EEE6884 DOT 20408 AT ecosensory DOT com> <20120425213315 DOT 7366B814784A AT turkos DOT aspodata DOT se> Comments: In-reply-to Russell Dill message dated "Wed, 25 Apr 2012 20:32:09 -0700." Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Message-Id: <20120426130554.2B4B1814784B@turkos.aspodata.se> Date: Thu, 26 Apr 2012 15:05:52 +0200 (CEST) From: karl AT aspodata DOT se (Karl Hammar) X-Virus-Scanned: ClamAV using ClamSMTP 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 Russel Dill: > On Wed, Apr 25, 2012 at 2:33 PM, Karl Hammar wrote: ... > > $ ~/git/openhw/share/ibis.pl stm32f2_lqfp100.ibs | head > > Component: STM32F2_LQFP100 > > 1 PE2 > > 2 PE3 ... > > So I'm wondering how to make that to a .sym file. ... > djboxsym is the probably the easiest way from that data, however... > > $ git clone git://github.com/russdill/pybis.git Wery, nice. ... > $ PYTHONPATH=. examples/ibs2symdef.py stm32f2_lqfp100.ibs ... > $ djboxsym < STM32F2_LQFP100.symdef > STM32F2_LQFP100.sym ... > The model doesn't contain any ground or power pins, so they do not > appear in the symbol. Also, the first model option for all the other > pins, so they all show up on the left side of the symbol. Its easy > enough to edit the symdef file to move them around though. Well, the pins are there, but commented and without a model to reference: $ egrep '^\|[0-9]+ [A-Z]' stm32f2_lqfp100.ibs |6 VBAT VDD33IOSWCO_MOSSWI_FT |10 VSS_5 VSSIOCO |11 VDD_5 VDD33IOCO |14 NRST RESET |19 VDD_12 VDD33IOCO_VSSIOCO_MOSSWI_FT |20 VSSA VSSCO |21 VREF+ VDD33CO |22 VDDA VDD33CO |27 VSS_4 VSSIOCO |28 VDD_4 VDD33IOCO |49 VCAP1_0 |50 VDD_1 |53 PA11 IO8USB_LSFS_OTG_FT_USB |54 PA12 IO8USB_LSFS_OTG_FT_USB |70 PA11 IO8USB_LSFS_OTG_FT_NON_USB_DNV33 |71 PA12 IO8USB_LSFS_OTG_FT_NON_USB_DPV33 |73 VCAP2 |74 VSS_2 |75 VDD_2 |99 NC |100 VDD_3 VDD33CO $ Should one expect ibis files to contain such incomplete pin definitions and somehow add some ad hoc rules for them (I havn't seen many ibis files so I can't say)? I cannot easily understand your code and provide a test patch. My guess is that you parse comments starting with "class Comment(Bracket):" on line 426 in pybis.py, and that it treats comments the same regardless of the current keyword. Regards, /Karl Hammar ----------------------------------------------------------------------- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57