X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Sun, 21 Oct 2012 17:30:17 -0400
Message-Id: <201210212130.q9LLUHwt025462@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <20121021202359.GA24620@fi.muni.cz> (message from Jan Kasprzak on
	Sun, 21 Oct 2012 22:23:59 +0200)
Subject: Re: [geda-user] Pin labeling: best practices?
References: <20121021202359 DOT GA24620 AT fi DOT muni DOT cz>
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


What I do is split MCUs up into functional blocks - one block for all
the power/gnd pins, one for ISP, one for external memory bus, etc.
Then you can fiddle with block variants on a per-project basis.

As for design-specific pin functions, what I do is leave the symbol's
pin named according to what the mcu's documentation uses, so that I
can remember what pin it "is" according to the mcu.  Then I label the
net coming out of that pin right at the pin, with its design-specific
purpose.

So, a pin that's GPIO port 9 bit 4, that's TxD3, that I happen to be
using for the console, might be named P94/TxD3 with the net named
CONSOLE_TX.