Hi Wayne, Thanks for pointing this out and no, you should not have known all of the above.
The thing is that this list started off as a developers list. At some point, there was a need to document parts of the development process. The JSG and SVN -pages were the first iirc and later test, board and sample files were added and documented (by others, I have documented way too little...). Some of these documents may be outdated and most of them assume you are a developer and have a working copy of the svn to work on. I can imagine this is confusing if you are not aware of this. But how to proceed? Maybe I shouldn't have mailed the link without a notice that it is a development-related procedure, using tools intended for developers. Maybe we should put a message on each developer page. Or we could suffice by stating that the jallib wiki is all for developers and if you use a package, you should focus on justanotherlanguage.org (which is still under construction afaik) I don;t know... What I do know is that testfiles, boardfiles are intended for developers to easly apply pic-independent test-files to their specific board configuration. The sample generation is developers tool to re-use the test-investment. So most of the knowledge of the test-files should be available in samples. I'm afraid I can't help you on the python issue. I'm glad I got it running here on my windows computer... Joep 2009/11/8 Wayne <[email protected]> > > Joep Suijs wrote: > > Hi Vasile, > > > > 2009/11/8 vasile surducan <[email protected]> > > > >> Hi Joep & all > >> > >> I'm not searching for something special, just try to understand things > that > >> I've missed (and find a few :) including the wedge procedures usage in > the > >> ISR, which does not work properly for me on my last project) > >> > > Wedge... sounds like something I added into a library and did not > document > > (yet). Not for the faint of heart and I am happy to work with you on > this. > > > > > >> However I'm starting a new design involving a graphical display > probably > >> with touchscreen / isolated USB conectivity/ IR temperature measurement, > >> some specific high voltage supply for a microwave generator and a > peltier > >> based thermostat, all together in a medical device. The chalenge is huge > at > >> this point, but the project will be slowly solved, step by step. I think > I > >> will split the main functionality on two microcontrollers, since I do > not > >> want to use any ARM or DSP core. > >> > > > > Impressive... Why don't you want an ARM or DSP core? > > > > I'm sure you took care of liability issue's? > > > > > >> We use board and test files to support development and testing. > >>> And Seb made a nice script that generates all possible (compilable) > >>> samples from each test/board combination. > >>> > >> How do you use those scripts? I guess is something phyton related which > run > >> on your own computer together with jal. > >> > > See the wiki: > > http://code.google.com/p/jallib/wiki/jallib_testing > > Joep > > Thanks for that link! I had not seen that before. I have a few > questions though. > > I as a user, and not a developer, was very confused when I first read > that page. At first I thought that I should be in the jalpack directory > to run the tests. Then realized that I had to be in the svn > directory as there is no board or test dirs in the jalpack. Duh :-( > I missed that because I was really confused by the paragraph about > Testfiles and boardfiles and I still don't understand it! > > I then tried to do the "jallib" command which didn't work. I had to look > at the jallib file to realize that I had to edit it to work on my > system. That makes sense, now, but I think it should be pointed out to > a new user in that page. > > I fixed the jallib file, finally, and ran the script which did put a > bunch of files in outdir as well as throwing a bunch of errors while > doing the writes. > > -------------------------------------------------------- > Invalid board/test combination: [Errno 13] Permission denied > Traceback (most recent call last): > File > "/Programming/PIC/JALv2/jallib/jallib-read-only/tools/jallib.py", line > 587, in generate_samples_for_board > generate_one_sample(board,test,fullsamplepath) > File > "/Programming/PIC/JALv2/jallib/jallib-read-only/tools/jallib.py", line > 541, in generate_one_sample > status = do_compile([outfile],exitonerror=False,clean=True) > File > "/Programming/PIC/JALv2/jallib/jallib-read-only/tools/jallib.py", line > 209, in do_compile > status = > subprocess.check_call(cmd,shell=False,stdout=stdout,stderr=stderr) > File "/usr/lib/python2.5/subprocess.py", line 457, in check_call > retcode = call(*popenargs, **kwargs) > File "/usr/lib/python2.5/subprocess.py", line 444, in call > return Popen(*popenargs, **kwargs).wait() > File "/usr/lib/python2.5/subprocess.py", line 594, in __init__ > errread, errwrite) > File "/usr/lib/python2.5/subprocess.py", line 1153, in _execute_child > raise child_exception > OSError: [Errno 13] Permission denied > ---------------------------------------------------------- > > I believe it may be due to the paths being different but I have not gone > through the jallib.py file yet to confirm that, yet. It may also be > that I don't have some python files that you fellows have. > > In the 16f648a files generated I noticed the the MCLR pragma is not > defined. Is that not needed in that pic? > > That's it for now... I have to get back to re-reading the > testfile/bordfile paragrph again. :-( > > Sorry if I should have known all of the above. I have tried to keep up > with the list but we have had some problems over here that took > precidence over my 'fun' work. > > Wayne > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
