I have to head out of state Friday to program some boards we're 
developing
that use a 'F123.  I decided to take the opportunity to install 'pyjtag' and
not drag along the Windows laptop.

        I'm wondering if there can be some unification in the python stuff.  I
don't know much about Python, but it was a bitch to build this stuff.  It's
not overly clear that first the _parjtag.so needs to be built from the
'jtag' directory.  And when I did, I got several errors.  There are explicit
calls to Python versions.  The jtag/python/build makefile has a specific
reference to the lib.linux-i686-2.1 directory, yet mine wanted to be 2.2.

        I think I had to change a total of 4 files to get it to use python2 and 
get
it all built and working.  Is there any way this can be unified?  There's
one file that uses "/usr/bin/env python" as an invocation line.  Is this the
safest way to get it to use the latest version?  And should the makefile use
'python' or 'python2'?

        It does finally work.  Part of the problem was that I had an old
_parjtag.so file that was causing a "Can't open device" message.  Should
there be a version check in the _parjatg.so file?  Is that even possible?

        --John



Reply via email to