On 29-07-2013, at 16:02 , Rob Hamerling <[email protected]> wrote:
> In my opinion the new files are a here and there somewhat over-complete: > there are many more declarations (synonyms) which are not used by any of the > current libraries and may never be needed in new libraries. This is because > the MPLAB-X files contain all these and I have not found a convenient way to > remove them ... maybe later. I assume you mean this: > var volatile bit*2 T2CON_T2CKPS at T2CON : 0 > var volatile bit T2CON_TMR2ON at T2CON : 2 > var volatile bit*4 T2CON_TOUTPS at T2CON : 3 > var volatile bit T2CON_T2CKPS0 at T2CON : 0 > var volatile bit T2CON_T2CKPS1 at T2CON : 1 > var volatile bit T2CON_TOUTPS0 at T2CON : 3 > var volatile bit T2CON_TOUTPS1 at T2CON : 4 > var volatile bit T2CON_TOUTPS2 at T2CON : 5 > var volatile bit T2CON_TOUTPS3 at T2CON : 6 Leave them in. I recently had my only problem with a device file ever, and this was it: a library adressed individual bits which weren't declared. The device files look good. I don't have hardware here, but if you can generate device files for the PIC18F67K22, I can do hardware testing in a few days. I think it is best if we have two full sets of device files, if that isn't too much work. Then we can switch between them when compiling our projects and notice the differences, if any. Eur van Andel, [email protected] Via Telia 3G, somewhere in Sweden -- You received this message because you are subscribed to the Google Groups "jallib" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/jallib. For more options, visit https://groups.google.com/groups/opt_out.
