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.8.0 04/21/2012 (debian 1:2.8.0~rc1-2) with nmh-1.5 X-Exmh-Isig-CompType: repl X-Exmh-Isig-Folder: inbox From: karl AT aspodata DOT se To: geda-user AT delorie DOT com Subject: Re: [geda-user] Datasheet PDF -> symbol+footprint+characteristics In-reply-to: <20151217082048.d5d04c13591f5a3b9ecd82a0@gmail.com> References: <1450268513 DOT 967952147 AT f8 DOT my DOT com> <20151216160918 DOT ED1FA8105D0D AT turkos DOT aspodata DOT se> <20151216192128 DOT 74cfb82ab124236c19abcc38 AT gmail DOT com> <20151217082048 DOT d5d04c13591f5a3b9ecd82a0 AT gmail DOT com> Comments: In-reply-to "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" message dated "Thu, 17 Dec 2015 08:20:48 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Message-Id: <20151217092452.3CC728038A57@turkos.aspodata.se> Date: Thu, 17 Dec 2015 10:24:51 +0100 (CET) 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 Niklas Karlsson: > It is useful for Microcontrollers with like one hundred pins. True, but you'll miss alt.func. names, and probably the power pins. > The ibis file I looked in have bin number, signal name and model > name. Pin number and signal name should be simple. That is simple for the pins *provided*, you have to add the rest somehow. And then, do you check the names against the pdf ? To extract pin names from pdf is not that much harder, consider the procedure in: http://wiki.geda-project.org/geda:tragesym_tutorial > Pin type from model I guess should be possible but require more work. That should be doable. The mcu probably don't have dedicated in's or out's, so the digital is simply io, then you have the digital ones that could be analog or clock, they are pas or possible clk, and lastly you have pwr. Or, you can simply set all pins to io, the pintype is perhaps only used when using drc2, and then it's mostly for digital io's anyhow and with digital pins reconfigurable, it's use more depends on your specific application than on what the mcu can do. I think so anyhow, I might be wrong on this. $ cd /gnetlist/scheme $ grep$ grep pwr * gnet-drc2.scm:;;; unknown in out io oc oe pas tp tri clk pwr unconnected gnet-drc2.scm:;;;pwr gnet-drc2.scm:(define pwr 10) gnet-drc2.scm:(define pintype-names (list "unknown" "in" "out" "io" "oc" "oe" "pas" "tp" "tri" "clk" "pwr" "unconnected")) gnet-drc2.scm:; unk in out io oc oe pas tp tri clk pwr undef gnet-drc2.scm:; unknown in out io oc oe pas tp tri clk pwr unconnected gnet-drc2.scm:;pwr grep: gnetlist: Is a directory $ So look through gnet-drc2.scm to see what pintype is used for. > I have not tried this command but think I used a spread sheet last time. > Intermediate format with list of pins together with attributes is > probably good but hopefully for most cases output should be piped to > djboxsym. > > I did not try djboxsym yet, used spread sheet last time. It would > however be useful with pins on two or four sides. ... If you can produce a file like: LQFP100 LQFP64 TFBGA64 LQFP48 1 - - - io PE2 TRACECLK 2 - - - io PE3 TRACED0 3 - - - io PE4 TRACED1 4 - - - io PE5 TRACED2 5 - - - io PE6 TRACED3 6 1 B2 1 pwr VBAT 7 2 A2 2 io PC13 TAMPER_RTC 8 3 A1 3 pas PC14 OSC32_IN ... I have a tool that take that and produce whatever symbol you wish (well every symbol I wish, but I'm willing to add more). The one above is for stm32f100 (see stm* in http://turkos.aspodata.se/git/openhw/share/gschem/include/, all stmf100*.sym are generated from the .pins and .pins.table files). A nice feature of this program is that same pins for all similar syms line up. Regards, /Karl Hammar ----------------------------------------------------------------------- Aspö Data Lilla Aspö 148 S-742 94 Östhammar Sweden +46 173 140 57