Hi Rob,
ADC libraries generation is based in pic_ds_map.py file. This file has once been generated from your wiki page. I should use devicespecific.json file... but then would directly be exposed to changes. adc_pcfg.py file also uses datasheet references, based on pic_ds_map.py. Looks like some normalization and checking would be required... One day... Cheers, Seb 2009/10/23 Rob Hamerling <[email protected]> > > > Hi Seb, > > > Sebastien Lelong wrote: > > > Can a given PIC have its datasheet number changed ? This is important > > because, for some of PICs, I use the datasheet number to generate ADC > > libraries (see /tools/adc/adc_pcfg.py) > > By coincidence I just discovered a situation that Microchip may use > duplicate datasheet *numbers* for essentially the same information. > In this case it is 'Programming Specification' 41396A with almost > identical contents as 41284c and with as only difference the addition of > '12F617' on some places. Looks like somebody is paid for the number of > new datasheets he/she releases! > > Anyway, indeed the datasheet number of a PIC can change! > > When I notice such an occasion I'll update devicespecific.json, but I > may 'forget' to update CHANGELOG because the change is too insignificant > (in my opinion). > > Regards, Rob. > > > -- > Rob Hamerling, Vianen, NL (http://www.robh.nl/) > > > > -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
