Mail Archives: geda-user/2013/09/20/16:49:18
On Sep 20, 2013, at 7:42 AM, Karl Hammar wrote:
> Dave Curtis, 16 Jul:
>> Modern microcontrollers typically have several functions that can be
>> brought out to each pin, under control of some pin routing registers.
>> Typically, I've used a pinlabel such as:
>>
>> pinlabel=PD5 (PCINT21/OC0B/T1)
>>
>> which shows the canonical GPIO name, plus other possible functions in
>> parens afterwards.
>>
>> A few days ago I was showing a friend (a KiCAD user) the output from the
>> symbol generator that I am working on, and he asked if there was a way
>> to make the pinlabel reflect the actual pin function as deployed in the
>> application, and lose all the other stuff.
> ...
>
> If you are writing a symbol generator, wouldn't the simplest solution
> be to make a new symbol.
If you go with per-project symbol libraries, perhaps. But also, remember that pin functions can change through the life of a project as you move the pin assignments around to ease routing or software.
In the end, I think a reasonable symbol generator needs to support all three methodologies. Tools should support the user's choice in methodology, not impose a methodology.
-dave
>
> I'm doing something similar with my pintosym.pl script.
> See
>
> http://turkos.aspodata.se/git/openhw/pdftosym/examples.pintosym/
>
> for examples.
>
> Regards,
> /Karl Hammar
>
> -----------------------------------------------------------------------
> Aspö Data
> Lilla Aspö 148
> S-742 94 Östhammar
> Sweden
> +46 173 140 57
>
>
- Raw text -