Hi Albert, It occurs I've just deleted it by error. While this file is being highly precious because it's been manually created. It stores the big table you sometime can see on datasheets, showing PCFG bits configuration and the results (#channels, #Vref...)
So it's now back into SVN. You should be able to run "adc_channels_generator.py". Or better, bash script "adc_generate_all.sh", or even "make adclib" in /tools. This will probably change in the near future: some python files will have to be generated from JSON format, while pinmap.py and adc_pcfg.py will also be converted to JSON format (very closed to python though). You can have a look at this wiki page, it can give you some guidelines (or not): http://code.google.com/p/jallib/wiki/ParsingDatasheets Let me know if you have any problems. Cheers, Seb 2009/7/28 a.faber <[email protected]> > > Hi Seb, > when I try to run the adc_channels_generator.py I get the following error: > ImportError: No module named adc_pcfg > Albert > > ----- Original Message ----- > From: "a.faber" <[email protected]> > To: <[email protected]> > Sent: Tuesday, July 28, 2009 8:33 PM > Subject: [jallib] Re: Issue 80 in jallib: pin_AN0_direction not defined > error for PIC16f722 > > > > > > Hi Seb, > > No problem to update them by hand from now on, do you have some > > instruction > > which scripts to run in order to update the ADC files? Also, do you want > > to > > maintain/update the pinmap.cvs file by hand? > > Albert > > > > ----- Original Message ----- > > From: <[email protected]> > > To: <[email protected]> > > Sent: Tuesday, July 28, 2009 7:57 PM > > Subject: [jallib] Issue 80 in jallib: pin_AN0_direction not defined error > > for PIC16f722 > > > > > >> > >> > >> Comment #2 on issue 80 by sebastien.lelong: pin_AN0_direction not > defined > >> error for PIC16f722 > >> http://code.google.com/p/jallib/issues/detail?id=80 > >> > >> I have troubles generating a new pinmap_pinsuffix.json file. I'm not > even > >> able to > >> re-generate current pinmap.py, with the same script ! I have to dig this > >> (or not), > >> but I guess this is because I've updated pdftotxt script, and the output > >> isn't the > >> same as before (while the parsing rules was very, very, very fragile). > >> I'd > >> need to > >> prepare/preprocess txt version of datasheet, to ease the parsing, but > >> it's > >> a lot of > >> work, too much issues. And too much time spend on this... > >> > >> My first attempts in producing pinmap.py was a one-shot approach. > >> pinmap.py > >> should > >> now be maintained by hand IMHO. > >> > >> As for 16f722, pins should be manually be put in pinmap.py, in order to > >> generate new > >> device files. I'll try to have a look soon. > >> > >> Seb > >> > >> -- > >> You received this message because you are listed in the owner > >> or CC fields of this issue, or because you starred this issue. > >> You may adjust your issue notification preferences at: > >> http://code.google.com/hosting/settings > >> > >> > > > > > > > > > > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
