Hi Seb,
Sebastien Lelong wrote:
> What don't we put the pin suffix directly within pinmap file?
> I guess you just concatenate strings from it, so this should
> generate "qualified" aliases in device file, without modifying your script.
Indeed I just take the string to create a 'pin_'alias name.
I was thinking about something similar: changing my py -> rexx
conversion script to insert the qualification. But having it in
pinmap.py is even easier (at least for me!).
> For 16F88:
>
> '16F88': {'RA0': ['RA0', 'AN0'],
> 'RA1': ['RA1', 'AN1'],
> 'RA2': ['RA2', 'AN2', 'CVREF'],
> 'RA3': ['RA3', 'AN3', 'VREF+'],
> 'RA4': ['RA4', 'AN4', 'T0CKI'],
> 'RA5': ['RA5', 'MCLR', 'VPP'],
> 'RA6': ['RA6', 'OSC2', 'CLKO'],
> 'RA7': ['RA7', 'OSC1', 'CLKI'],
> 'RB0': ['RB0', 'INT', 'CCP1_B0'],
> 'RB1': ['RB1', 'SDI', 'SDA'],
> 'RB2': ['RB2', 'SDO', 'RX', 'DT'],
> 'RB3': ['RB3', 'PGM', 'CCP1_B3'],
> 'RB4': ['RB4', 'SCK', 'SCL'],
> 'RB5': ['RB5', 'SS', 'TX', 'CK'],
> 'RB6': ['RB6', 'AN5', 'PGC'],
> 'RB7': ['RB7', 'AN6', 'PGD']},
>
> (PICs with CCP1MUX: 16f818, 16f819, 16f87, 16f88. Few manual modifications)
>
> What do you think about this solution ?
Would be great!
But beware that apart from CCP1 there are many other duplicate aliases,
expecially in the 18F series. I could send you a list of the dup
warnings from my dev2jal script.
Regards, Rob.
--
Rob Hamerling, Vianen, NL (http://www.robh.nl/)
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---
