Hello all,

I order to keep the maintenance of - the scripts  of - device files 
generation low I want to implement 2 changes. I also propose it as not to 
carry any legacy that is no longer needed:

1) For each device file aliases are added for mapping of analog pins to a 
logic sequence of numbers, so called 'JANSEL_xx'. I heard that the analog 
library for this is no longer maintained. Next to that there are no sample 
files that use these JANSEL aliases. In the scripts a lot of exceptions are 
handled  - due to inconsistencies from Microchip - to create these JANSEL 
alias. I propose to remove the JANSEL aliases from the device files and 
simplify the script.

2) Currently the device files are only generated when there is a data 
sheet. I fully agree with this. However, the generation uses the number of 
the datasheets which is frequently changed by Microchip. We already removed 
the datasheets from GitHub since we could no longer automatically download 
them. The number of the datasheet is also mentioned in the device file. 
Datasheets can easily be found by just Google the PIC number. As to lower 
the maintenance of the scripts I propose to remove the datasheet number 
from the device file and from the script that generates them. Also the 
'datasheet.lst' file could be removed since in 'devicespecific.json' it is 
mentioned if a datasheet is available or not. I am OK to keep the 
datasheet.lst up to date but then by removing the number of the datasheet. 
I also would like to remove the programming specification from this list 
since they are not used in the generation of device files.

Let me know your thought on these proposals.

Thanks

Kind regards,

Rob


-- 
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 https://groups.google.com/group/jallib.
For more options, visit https://groups.google.com/d/optout.

Reply via email to