Mail Archives: geda-user/2015/12/17/04:25:06
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 <git root of geda-gaf>/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
- Raw text -