Mail Archives: geda-user/2012/07/10/09:45:07
Bdale Garbee:
> Karl Hammar <karl AT aspodata DOT se> writes:
> > I wanted to make some symbols for STM32F100C, a cortex-m3 from ST
> > in a 48pin lqfp package.
> I have symbols for the STM32L151 in 48, 64, and 100 pin variants, you
> can find them on git.gag.com in the hw/bdale repo.
Ok, looking through that repo...
In MAWD.sym and miniRRC2.sym it seems you got the pins with the active
end on the outline, is it any specific reason for that?
MWswitch.sym looks funny, what is that?
Yeah, I know, description and documentation attribs are for the weak:)
///
If you don't mind I'll take your PIC12F629.sym and see what I can do
about it.
Sym files are a little wordy, this little device is this big:
$ wc PIC12F629.sym
104 542 1920 PIC12F629.sym
Now, I can extract (with [1]) the attribs and pins from the file:
$ ~/git/openhw/pdftopin/symtopin.pl PIC12F629.sym
numslots=0
refdes=U?
footprint=DIP28
device=PIC18F242
description=Microchip PIC18F242 Microcontroller
slot=1
1 in Vdd
2 io GP5/T1CKI/OSC1/CLKIN
3 io GP4/T1G/OSC2/CLKOUT
4 io GP3/MCLR/Vpp
5 io GP2/T0CKI/INT/COUT
6 io GP1/CIN-/ICSPCLK
7 io GP0/CIN+/ICSPDAT
8 pwr Vss
$
Now, it is plain easy to see that pintype of Vdd should be pwr which
wasn't that easy to spot in the sym file.
And where are your attribs hidden, they doesn't show when
Edit->show inv text (EN), View->zoom extents (VE), I cannot find it in
the gschem canvas.
T 5400 -900 8 10 0 0 0 0 1
device=PIC18F242
Well, it was in Hade realm. I don't know if it is a bug or feature to
be able to hide things that way, it is in a non-scrollable region.
///
Change Vdd's pintype, "/" to " ", add:
!include def.pins
!> .dil.sym dil
!> .rect.sym rect 2 0 0.2 l:Vdd,GP[3-5] r:.*
anywhere in the file, and add the file:
$ cat def.pins
author=Bdale Garbee <bdale AT gag DOT com>
copyright=Bdale Garbee
$
I can get:
$ ~/git/openhw/pdftopin/pintosym.pl PIC12F629.pins
printing to PIC12F629.dil.sym dil()
printing to PIC12F629.rect.sym rect(2 0 0.2 l:Vdd,GP[3-5] r:.*)
$
two brand new sym's. I did take about an hour, but 30min was for this
mail, 20min for symtopin.pl; that means in just 10min from start to
stop I got a cleaned up sym.
I put them all at [2] so you can compare.
///
> I don't know enough about the F series to know if that might be at
> all useful to you or not.
There are some migration guides in:
AN3364 Migration and compatibility guidelines for STM32F1, STM32F2 and STM32L1 microcontroller applications
http://www.st.com/internet/com/TECHNICAL_RESOURCES/TECHNICAL_LITERATURE/APPLICATION_NOTE/DM00024853.pdf
AN3422 Migration of microcontroller applications from STM32F1 to STM32L1 series
http://www.st.com/internet/com/TECHNICAL_RESOURCES/TECHNICAL_LITERATURE/APPLICATION_NOTE/DM00032987.pdf
but no, I don't think I'll use them now that I already made my sym's.
...
> The "magic" in my set of STM32L151 symbols is that all the pins
> they have in common are in the same place on the symbol, so that I
> can change between the different physical package versions in the
> schematic quite easily.
Interesting idea, I'll think about that.
Another way to do that would be to do a 48pin sym, then a sym for the
diff between the 64 and 48 pin package, and then a diff-sym for
100-64, etc. Then you don't have to switch syms at all, just add
another sheet with the extra functionality.
Regards,
/Karl Hammar
[1] http://turkos.aspodata.se/git/openhw/pdftopin/symtopin.pl
[2] http://turkos.aspodata.se/tmp/geda/
-----------------------------------------------------------------------
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57
- Raw text -