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=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-transfer-encoding; bh=+HGP1QPw3ro6mTYlxzv969RQQl1lZOJ8nKuOZOzyZp4=; b=iR9G3Bm1Sn10yuLB6vIZZ8XjfAriJRVjrRy0uRHEKg9PxTqMMzaO9BiEGsrhz/ZZCP TJzu2r3yTllVDK7uPa6f2OJ0bF6Qyc5HnmKUhkM7Q8cCPEjP49B2QCG0BuqTugGNROlW LTgHSWwZaVFlZ6Arghjyo7+X39WsfFdrGtd6pRPtuXOazfNV3I6/nC/lDiEZzHT1sR4c uU1h+w/JUoVhVdlkV5SXW0QfuyNkTSQLrwKixBEyu2pirlm2GiqHt3OufWyB0nMeS/dr 03Di52SYnIyoJioQUJp39Z+nxAH5poAiBIpWmanLXuBsDwt2d/9aPWHB7xkaoUyZx0P1 VvUg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=+HGP1QPw3ro6mTYlxzv969RQQl1lZOJ8nKuOZOzyZp4=; b=nghPmfIKO5kqEQO7kOOIcX9vDdUIOPtf/q0LB8FWBf/PqSZGJot1MEXS680yfBqt7a E3yps1lxivAmzshkKraWyiOI52HN1C7IzpAmYgo4t/VoBwHfGA9S7pyDY6CLwbZNATdC JGIel0/NU5hLrIv4TPSmLbjN0qBSbdFuN77phbkRtSYEv8bahYWx23mcDaTYDR+wYaZo UUqO1tcb5kRb0ZYQvd8K6+77tTX/7qMp74cAv0qoEM25xDEVFvXB+JTGbYnSGOYLNif9 bS61AAI1BwvWz9yhh20hK2+jX9PrdwLrvwXu6NckKZbompXXGVjFVZvdBCuZyswGtHKc yOzg== X-Gm-Message-State: AFeK/H10GgW+TrOx9+N7ZXRi1+rOnlUKkpih/D5bi/iH8vMe3h3XXbJpctcTZhs9he85cA== X-Received: by 10.25.102.2 with SMTP id a2mr2592994lfc.3.1490121231188; Tue, 21 Mar 2017 11:33:51 -0700 (PDT) Date: Tue, 21 Mar 2017 19:33:46 +0100 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] pdf -> sym generator Message-Id: <20170321193346.64142d687ac87208253cc722@gmail.com> In-Reply-To: <20170321103609.DCEC68106DCC@turkos.aspodata.se> References: <20170320161202 DOT 965CD8106DC1 AT turkos DOT aspodata DOT se> <20170321103609 DOT DCEC68106DCC AT turkos DOT aspodata DOT se> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 > John: > > On 03/20/2017 10:12 AM, karl AT aspodata DOT se wrote: > > > That together with [4] and pintosym.pl [5] creates the symbol files > > > in [6]: > > > > > > I like your long names in smaller text for each pin. > > Were those auto extracted, or did you edit a file to guide that? > > Yes, they are auto generated from the alternate function columns. > > Pintosym lets you search for text in the pin names and alt.func. names > and when found, it puts that in normal size instead of the normal pin > name. E.g. stm32f107.can.LQFP64.sym is generated by searching for pin > names with "CAN" in it, the normal pin names like PD12 is then demoted > the small font line and the searched for text like CAN2_RX is made to > stand out. Seems that I'm also dropping the "_" in names on the small > font line. > > I am also contenplating the idea of adding a "r" to the remap > alternatives. E.g. pin PC7 has alt.function I2S3_MCK and > remap alternative TIM3_CH2, so I think that maybe using the name > TIM3_CH2r or rTIM3_CH2 for the remap alternative could be helpful. > That would also give you the opportunity to no to show remap functions > in the symbol file. > > ST also have a column for identifing 5V tolerant pins, how do I convey > that in a symbol ? Just add a suitable attribute to the pin, "U.max" or maybe "Umax" if "." in an attribute name is a problem? Or is there already a standard attribute name? "description", "documentation" and "comment" are available in the list of more or less standard attributes in gschem.