Mail Archives: geda-user/2021/04/25/16:58:00
| X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f
|
| X-Recipient: | geda-user AT delorie DOT com
|
| X-Original-DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed;
|
| d=gmail.com; s=20161025;
|
| h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
|
| bh=TO+Q1KtXpg1qBlDUEc1j69HiViAEM4UR7imdV5DKcuQ=;
|
| b=fBgwRHepr2+GUJWBs5ZSuoVfkjluwuG72L7U1uO/r3P3sGBooUsx01ECtcSoJSYaaK
|
| OfK5kmP10/ZV0pONcJVa7u8eORSj7ru2eGYZtyFpQq8p2qv8qrVb/2xvyLLObXEg0HmV
|
| UiCBDKzmxuVGA7LE07k4aq5wATafmh8k3VZaBqttYnJEmMxfHqEe1arSwl1gXtebueyz
|
| dkyfVMkvohdnAOmdEnRGodLbWRHOI+YSTA5h+cVLlKs3yEIfgWFrnU7Flfko/wS9q7xE
|
| hvQ25g5OzXiUK9lIg6oo2cTc2mL2wCJFNz0molUiRW11iQwX+nLXnZ1bPoWsugUVR015
|
| W+iA==
|
| X-Google-DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed;
|
| d=1e100.net; s=20161025;
|
| h=x-gm-message-state:mime-version:references:in-reply-to:from:date
|
| :message-id:subject:to;
|
| bh=TO+Q1KtXpg1qBlDUEc1j69HiViAEM4UR7imdV5DKcuQ=;
|
| b=FQD0UWOOYBUhAsavn3GMwx7FXqmwpdz+9+bMSN5D6fIGXdyC/f9+QnQL6b0iwrE/52
|
| j4SX8McSkDIqajmWnEje0aTf8C76oXvk7A0wGfvkoA3ZzfWCLtg5BCIFedCP9Z3SQpEa
|
| nUoOrWxBsz3myflvO7INQ83XDcDxpaL7Qy5Q4ApB+Zc0BT/yfSthwNbsmClBi8uqSllk
|
| Je54NduuPH2euwAwNWs+pB2TfqtIH74IBG9f1zgbVmdNqxYSGN4g/sGpPc850Z+Ax3fw
|
| T4oJWkFm40qUmrsQqNj8f3ka9oYkyiRerAq1DB7txfHhlGZIfdFSmzvDmeFTiU+t16aA
|
| r7Tw==
|
| X-Gm-Message-State: | AOAM533v+xG5BJWNj9xhYog3DpvWkc9ove2C38sMhq/8lqfDiu5fJ+ii
|
| +Tgnan8S7L9ofjxQm1wm15nK0sNvh5oCnmGncN+sB2b3
|
| X-Google-Smtp-Source: | ABdhPJylVIZKvqXSiHDFBO0eV+PV9VdtrV+stOfUZrlskXjZ302V1y9LyAyiM4HoZY8TZeAWSMSe4ceEdH+56/+v6y8=
|
| X-Received: | by 2002:a2e:99d1:: with SMTP id l17mr10450450ljj.501.1619384206844;
|
| Sun, 25 Apr 2021 13:56:46 -0700 (PDT)
|
| MIME-Version: | 1.0
|
| References: | <20210425114318 DOT A17E183D15C7 AT turkos DOT aspodata DOT se> <e032c3a5-2902-7d1c-ad71-f862bb239b07 AT nksb DOT online>
|
| In-Reply-To: | <e032c3a5-2902-7d1c-ad71-f862bb239b07@nksb.online>
|
| From: | "Erich Heinzle (a1039181 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
|
| Date: | Mon, 26 Apr 2021 06:26:34 +0930
|
| Message-ID: | <CAHUm0tPPa46uLD__nkdUrPVB=VwWNmnb94hPnj8O8G6YG-yQAw@mail.gmail.com>
|
| Subject: | Re: [geda-user] Symbols, pin function/name changes - BSDL
|
| To: | geda-user <geda-user AT delorie DOT com>
|
| Reply-To: | geda-user AT delorie DOT com
|
--0000000000006765dd05c0d2445f
Content-Type: text/plain; charset="UTF-8"
translate2geda handles bsdl files, but things get a bit crazy with large
fpga devices
https://github.com/erichVK5/translate2geda
Regards,
Erich
On Mon, 26 Apr 2021 03:47 Nicklas SB Karlsson (nk AT nksb DOT online) [via
geda-user AT delorie DOT com], <geda-user AT delorie DOT com> wrote:
> It's a good appreciated effort. As manufacturers make available BSDL
> files for components I however think it's a good idea to mention
> something about them.
>
> Syntax is different from yours but they are text files. Looking into one
> or a few: there is pin label similar to your last column, pin type
> similar to your second last column, there is a pin map string and there
> are also other information probably not usable in symbols.
>
>
> Nicklas Karlsson
>
>
> Den 2021-04-25 kl. 13:43, skrev karl AT aspodata DOT se [via
> geda-user AT delorie DOT com]:
> > In http://aspodata.se/git/openhw/pdftosym/pintosym.pl
> > I have a program that generates symbols.
> >
> > It takes lists of pinnumber vs pinlabels like:
> >
> > LQFP100 LQFP64 TFBGA64 LQFP48
> > ...
> > 6 1 B2 1 pwr VBAT
> > 7 2 A2 2 io PC13 TAMPER_RTC
> > 8 3 A1 3 pas PC14 OSC32_IN
> > 9 4 B1 4 pas PC15 OSC32_OUT
> > 10 - - - pwr VSS_5
> > 11 - - - pwr VDD_5
> > 12 5 C1 5 pas OSC_IN
> > 13 6 D1 6 pas OSC_OUT
> > ...
> >
> > where a function is on different pins for different packages.
> > I.e. VBAT is a pwr pin, which is pin 1 in the LQFP48 package,
> > and B2 in the bga package.
> >
> > That works quite nice, and for e.g. the power pins I can make them
> > line up as in:
> >
> http://aspodata.se/git/openhw/share/gschem/_mcu/stm32f100lm.power.LQFP100.sym
> >
> http://aspodata.se/git/openhw/share/gschem/_mcu/stm32f100lm.power.LQFP48.sym
> >
> http://aspodata.se/git/openhw/share/gschem/_mcu/stm32f100lm.power.LQFP64.sym
> >
> http://aspodata.se/git/openhw/share/gschem/_mcu/stm32f100lm.power.TFBGA64.sym
> > so for theese symbols Vdd_3 is in the same position regardless of
> > package type, so I can swap the symbol, and all things that were
> > connected to Vdd_3 will still be. Compare theese two for example:
> >
> http://aspodata.se/git/openhw/share/gschem/_sub_page/stm32f100lm.power.LQFP48_10u.sch
> >
> http://aspodata.se/git/openhw/share/gschem/_sub_page/stm32f100lm.power.LQFP100_10u.sch
> > they depends on symbols in directories:
> > http://aspodata.se/git/openhw/share/gschem/_graphical/
> > http://aspodata.se/git/openhw/share/gschem/_discrete/
> > and the above stm32f1xxx.sym's.
> >
> > So that works just nice if the pin label stays the same.
> >
> > ///
> >
> > But now I'm looking at the smarc standard:
> > https://sget.org/standards/smarc/
> >
> > There you have the same pin, but differnt names/functions depending on
> > which generation, also later generations might add alternate functions.
> >
> > A) same function but the name is changed
> > E.g. for pin P26, in Embedian T335X (smarc v1p0?) it is named EthRX-,
> > in sget standard for v1p0 and v1p1 it is named GBE_MDI1-, and lastly
> > in v2p0,v2p1,v2p1.1 it is named GBE0_MDI1-. I.e. Eth -> GBE -> GEB0
> > is the same thing under different names.
> >
> > B) alternate functions dropped or added
> > Se e.g.
> > http://aspodata.se/git/openhw/share/gschem/_module/smarc_pinout.txt
> > https://sget.org/wp-content/uploads/2020/05/SMARC_V211.pdf p.96..
> >
> > Take pin S32, between v1p1 - v2p0 there is a function change, and
> > between v2p0 - v2p1 an alt.func. was added.
> > $ head -1 smarc_pinout.txt ; grep 'S32' smarc_pinout.txt
> > pin | SMARC v1.0 | SMARC v1.1 | SMARC v2.0
> | SMARC v2.1 (and 2.1.1)
> > S32 | SDMMC_D6 | SDMMC_D6 | PCIE_D_RX+
> | PCIE_D_RX+ SERDES_0_RX+
> >
> > Pin P77 was dropped in v2p0, and oops, readded in v2p1.
> > $ head -1 smarc_pinout.txt ; grep 'P77' smarc_pinout.txt
> > pin | SMARC v1.0 | SMARC v1.1 | SMARC v2.0
> | SMARC v2.1 (and 2.1.1)
> > P77 | PCIE_B_CKREQ# | PCIE_B_CKREQ# | RSVD
> | PCIE_B_CKREQ#
> >
> > What is a good way to handle that ?
> >
> > Regards,
> > /Karl Hammar
> >
> >
>
--0000000000006765dd05c0d2445f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto">translate2geda handles bsdl files, but things get a bit c=
razy with large fpga devices<div dir=3D"auto"><br></div><div dir=3D"auto"><=
a href=3D"https://github.com/erichVK5/translate2geda">https://github.com/er=
ichVK5/translate2geda</a><br><div dir=3D"auto"><br></div><div dir=3D"auto">=
Regards,</div><div dir=3D"auto"><br></div><div dir=3D"auto">Erich</div></di=
v></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr=
">On Mon, 26 Apr 2021 03:47 Nicklas SB Karlsson (nk AT nksb DOT online) [via <a hr=
ef=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>], <<a href=
=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>> wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">It's a good appreciated effort. As =
manufacturers make available BSDL <br>
files for components I however think it's a good idea to mention <br>
something about them.<br>
<br>
Syntax is different from yours but they are text files. Looking into one <b=
r>
or a few: there is pin label similar to your last column, pin type <br>
similar to your second last column, there is a pin map string and there <br=
>
are also other information probably not usable in symbols.<br>
<br>
<br>
Nicklas Karlsson<br>
<br>
<br>
Den 2021-04-25 kl. 13:43, skrev <a href=3D"mailto:karl AT aspodata DOT se" target=
=3D"_blank" rel=3D"noreferrer">karl AT aspodata DOT se</a> [via <br>
<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank" rel=3D"noreferre=
r">geda-user AT delorie DOT com</a>]:<br>
>=C2=A0 =C2=A0In <a href=3D"http://aspodata.se/git/openhw/pdftosym/pinto=
sym.pl" rel=3D"noreferrer noreferrer" target=3D"_blank">http://aspodata.se/=
git/openhw/pdftosym/pintosym.pl</a><br>
>=C2=A0 =C2=A0I have a program that generates symbols.<br>
><br>
>=C2=A0 =C2=A0It takes lists of pinnumber vs pinlabels like:<br>
><br>
> LQFP100 LQFP64 TFBGA64 LQFP48<br>
> ...<br>
>=C2=A0 =C2=A0 6=C2=A0 =C2=A01=C2=A0 B2=C2=A0 =C2=A01 pwr VBAT<br>
>=C2=A0 =C2=A0 7=C2=A0 =C2=A02=C2=A0 A2=C2=A0 =C2=A02 io=C2=A0 PC13 TAMP=
ER_RTC<br>
>=C2=A0 =C2=A0 8=C2=A0 =C2=A03=C2=A0 A1=C2=A0 =C2=A03 pas PC14 OSC32_IN<=
br>
>=C2=A0 =C2=A0 9=C2=A0 =C2=A04=C2=A0 B1=C2=A0 =C2=A04 pas PC15 OSC32_OUT=
<br>
>=C2=A0 =C2=A010=C2=A0 =C2=A0-=C2=A0 =C2=A0-=C2=A0 =C2=A0- pwr VSS_5<br>
>=C2=A0 =C2=A011=C2=A0 =C2=A0-=C2=A0 =C2=A0-=C2=A0 =C2=A0- pwr VDD_5<br>
>=C2=A0 =C2=A012=C2=A0 =C2=A05=C2=A0 C1=C2=A0 =C2=A05 pas OSC_IN<br>
>=C2=A0 =C2=A013=C2=A0 =C2=A06=C2=A0 D1=C2=A0 =C2=A06 pas OSC_OUT<br>
> ...<br>
><br>
>=C2=A0 =C2=A0where a function is on different pins for different packag=
es.<br>
>=C2=A0 =C2=A0I.e. VBAT is a pwr pin, which is pin 1 in the LQFP48 packa=
ge,<br>
>=C2=A0 =C2=A0and B2 in the bga package.<br>
><br>
>=C2=A0 =C2=A0That works quite nice, and for e.g. the power pins I can m=
ake them<br>
>=C2=A0 =C2=A0line up as in:<br>
> <a href=3D"http://aspodata.se/git/openhw/share/gschem/_mcu/stm32f100lm=
.power.LQFP100.sym" rel=3D"noreferrer noreferrer" target=3D"_blank">http://=
aspodata.se/git/openhw/share/gschem/_mcu/stm32f100lm.power.LQFP100.sym</a><=
br>
> <a href=3D"http://aspodata.se/git/openhw/share/gschem/_mcu/stm32f100lm=
.power.LQFP48.sym" rel=3D"noreferrer noreferrer" target=3D"_blank">http://a=
spodata.se/git/openhw/share/gschem/_mcu/stm32f100lm.power.LQFP48.sym</a><br=
>
> <a href=3D"http://aspodata.se/git/openhw/share/gschem/_mcu/stm32f100lm=
.power.LQFP64.sym" rel=3D"noreferrer noreferrer" target=3D"_blank">http://a=
spodata.se/git/openhw/share/gschem/_mcu/stm32f100lm.power.LQFP64.sym</a><br=
>
> <a href=3D"http://aspodata.se/git/openhw/share/gschem/_mcu/stm32f100lm=
.power.TFBGA64.sym" rel=3D"noreferrer noreferrer" target=3D"_blank">http://=
aspodata.se/git/openhw/share/gschem/_mcu/stm32f100lm.power.TFBGA64.sym</a><=
br>
>=C2=A0 =C2=A0so for theese symbols Vdd_3 is in the same position regard=
less of<br>
>=C2=A0 =C2=A0package type, so I can swap the symbol, and all things tha=
t were<br>
>=C2=A0 =C2=A0connected to Vdd_3 will still be. Compare theese two for e=
xample:<br>
> <a href=3D"http://aspodata.se/git/openhw/share/gschem/_sub_page/stm32f=
100lm.power.LQFP48_10u.sch" rel=3D"noreferrer noreferrer" target=3D"_blank"=
>http://aspodata.se/git/openhw/share/gschem/_sub_page/stm32f100lm.power.LQF=
P48_10u.sch</a><br>
> <a href=3D"http://aspodata.se/git/openhw/share/gschem/_sub_page/stm32f=
100lm.power.LQFP100_10u.sch" rel=3D"noreferrer noreferrer" target=3D"_blank=
">http://aspodata.se/git/openhw/share/gschem/_sub_page/stm32f100lm.power.LQ=
FP100_10u.sch</a><br>
>=C2=A0 =C2=A0they depends on symbols in directories:<br>
> <a href=3D"http://aspodata.se/git/openhw/share/gschem/_graphical/" rel=
=3D"noreferrer noreferrer" target=3D"_blank">http://aspodata.se/git/openhw/=
share/gschem/_graphical/</a><br>
> <a href=3D"http://aspodata.se/git/openhw/share/gschem/_discrete/" rel=
=3D"noreferrer noreferrer" target=3D"_blank">http://aspodata.se/git/openhw/=
share/gschem/_discrete/</a><br>
>=C2=A0 =C2=A0and the above stm32f1xxx.sym's.<br>
><br>
>=C2=A0 =C2=A0So that works just nice if the pin label stays the same.<b=
r>
><br>
> ///<br>
><br>
>=C2=A0 =C2=A0But now I'm looking at the smarc standard:<br>
> <a href=3D"https://sget.org/standards/smarc/" rel=3D"noreferrer norefe=
rrer" target=3D"_blank">https://sget.org/standards/smarc/</a><br>
><br>
>=C2=A0 =C2=A0There you have the same pin, but differnt names/functions =
depending on<br>
>=C2=A0 =C2=A0which generation, also later generations might add alterna=
te functions.<br>
><br>
>=C2=A0 =C2=A0A) same function but the name is changed<br>
>=C2=A0 =C2=A0E.g. for pin P26, in Embedian T335X (smarc v1p0?) it is na=
med EthRX-,<br>
>=C2=A0 =C2=A0in sget standard for v1p0 and v1p1 it is named GBE_MDI1-, =
and lastly<br>
>=C2=A0 =C2=A0in v2p0,v2p1,v2p1.1 it is named GBE0_MDI1-. I.e. Eth ->=
GBE -> GEB0<br>
>=C2=A0 =C2=A0is the same thing under different names.<br>
><br>
>=C2=A0 =C2=A0B) alternate functions dropped or added<br>
>=C2=A0 =C2=A0Se e.g.<br>
>=C2=A0 =C2=A0<a href=3D"http://aspodata.se/git/openhw/share/gschem/_mod=
ule/smarc_pinout.txt" rel=3D"noreferrer noreferrer" target=3D"_blank">http:=
//aspodata.se/git/openhw/share/gschem/_module/smarc_pinout.txt</a><br>
>=C2=A0 =C2=A0<a href=3D"https://sget.org/wp-content/uploads/2020/05/SMA=
RC_V211.pdf" rel=3D"noreferrer noreferrer" target=3D"_blank">https://sget.o=
rg/wp-content/uploads/2020/05/SMARC_V211.pdf</a> p.96..<br>
><br>
>=C2=A0 =C2=A0Take pin S32, between v1p1 - v2p0 there is a function chan=
ge, and<br>
>=C2=A0 =C2=A0between v2p0 - v2p1 an alt.func. was added.<br>
> $ head -1=C2=A0 smarc_pinout.txt ; grep 'S32' smarc_pinout.txt=
<br>
> pin=C2=A0 | SMARC v1.0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| SMARC=
v1.1=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| SMARC v2.0=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =
SMARC v2.1 (and 2.1.1)<br>
> S32=C2=A0 | SDMMC_D6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =
SDMMC_D6=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| PCIE_D_RX+=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0| PCIE_D_RX+ SERDES_0_RX+<br>
><br>
>=C2=A0 =C2=A0Pin P77 was dropped in v2p0, and oops, readded in v2p1.<br=
>
> $ head -1=C2=A0 smarc_pinout.txt ; grep 'P77' smarc_pinout.txt=
<br>
> pin=C2=A0 | SMARC v1.0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| SMARC=
v1.1=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| SMARC v2.0=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =
SMARC v2.1 (and 2.1.1)<br>
> P77=C2=A0 | PCIE_B_CKREQ#=C2=A0 =C2=A0 =C2=A0 =C2=A0 | PCIE_B_CKREQ#=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 | RSVD=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| PCI=
E_B_CKREQ#<br>
><br>
>=C2=A0 =C2=A0What is a good way to handle that ?<br>
><br>
> Regards,<br>
> /Karl Hammar<br>
><br>
><br>
</blockquote></div>
--0000000000006765dd05c0d2445f--
- Raw text -