X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1350937554; bh=o9hZW1RBQqMmmz0s4q1tuLQxcZpvXw0osZYeFY0LaUs=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=hQmeQ1vXc9+rzvd/6m740Q8gqZPhaK2v3ql22Vg6KyND6TSH3slsLyPMTev+8biwAISIxZNU6NHOGicKPfj0/9RLSFrasd+NW9TgqAv+oXwXavC2HxjqDci+YgoeHIvIKZ9LvQABxeIRQUqDonpkLYln2Mj31I6PS042f+Avnr8= X-Yahoo-Newman-Id: 340469 DOT 53582 DOT bm AT smtp109 DOT sbc DOT mail DOT mud DOT yahoo DOT com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: dMQq9rIVM1kgWoAYnE30oY0IZQR0dXHYdKnwI2tUkN63Wal umYTeH6gPlt7qQY961B6SFXN9990356L42FE8xL_J1bfcFyM7kpZAQfxoaJN tilmiDBo3gXZgh7.nGPiy3zD1RRWoM64mRlNPANTlITviNsF9hhFKNOp_OGJ 0clvBSXbOUhk4JLmqSzkNR4pfmXv9nKhD0FhTfpzGYI.OT.1PtL3o1wKn1YM ZNE8euSbh9_OvoNVI0V2fEFfqaV1A2XwptQApsGCTq2s1eW.zWe4eGkJPPjZ WN.mOnaMSiJc17oTAO7aMAHtPFCyi6LnoAIHaWqOvM81fgL6ihx4a_HLgJAf MC._dETHKskpwOiafYosuQqopW5x9WgY6zwEr.oh.D9X0DO0JTaEcOD8EAIG o4f5k561Y3BY7d9pjaCKl.hfTTchvJ.PanGs46WuucWom1hojWOM3VgL7DG5 TXL.K_RKI47CPgVenUf6k32JHw8V_xflPsX6nsgl8o1ftCscl5451vCsTydA YtyKMPlCVDfk_oOwuBKjPmEpojeQr9mB7uGw8emnb1ZXprOZr9MgJVmACOaY KlQYY2YpOf1MVTfZqR3bA6XI- X-Yahoo-SMTP: f_DTt3mswBBgAkQlHvfWr7fedPivEj8lM_i1QPTGLa1z0f7XFiw- Message-ID: <5085AB12.6030104@sbcglobal.net> Date: Mon, 22 Oct 2012 13:22:42 -0700 From: "Girvin R. Herr" User-Agent: Thunderbird 2.0.0.24 (X11/20100228) MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] Pin labeling: best practices? References: <20121021202359 DOT GA24620 AT fi DOT muni DOT cz> <201210212130 DOT q9LLUHwt025462 AT envy DOT delorie DOT com> <20121021215442 DOT GB24620 AT fi DOT muni DOT cz> In-Reply-To: <20121021215442.GB24620@fi.muni.cz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com Jan Kasprzak wrote: > DJ Delorie wrote: > : > : 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. > > Naming nets instead of pins seems reasonable, thanks! There is > a problem wrt. my design with this approach, though: some pins of the MCU > are used for programming as well as for other purposes. For example, > one pin is used as clock input when downloading the firmware, and as > a PWM output in normal operation. So I want the programming connector > pin to be labeled "clock", but the whole net (maybe including > the MCU pin) should be labeled "PWM 1" or something like that. > > IOW, I want the "clock" label to be visible somewhere near the > connector pin (both in the schematics and in the PCB silk layer), > and the label "PWM 1" visible near the CPU pin. How do you suggest to > handle multi-purpose nets/pins? > > -Yenya > Yenya, I sometimes use the "Comment" attribute to add notes or other non-intelligent attributes to symbols, such as a panel name in quotes for a control. Attach the attribute to a symbol and it will move with the symbol. You can always edit its location and text attributes. You can add as many "Comment" attributes as you want to a symbol. I don't know if comment attributes are imported to PCB, but they are on the schematic if set to visible. Girvin Herr