You are correct, it's the Makefile that needs to be edited. BTW,
convention says that the name should be Makefile, rather than makefile, if
you want to follow tradition.
A couple of other notes. I had to install python2-devel to be able to
generate the _parjtag.so file. Otherwise, it was throwing up on my shoes
with the errors below. This needs to be in the top level README.
The Makefile in the /python directory does the following: 'cp
build/lib.linux-i686-2.1/$@ .' This does not work so well if you have a
python2.2 distribution installed.
The _parjtag.so file that comes in the /pyjtag directory does not work.
It
had to be rebuilt. I presume that the object is to copy the _parjtag.so
file from the /jtag/python directory to the /pyjtag directory.
It would also be nice if the programming process had an option for more
verbosity. When -e -p -v -r is done, it would be good to know what step
it's on, particularly for large programs. I don't think spinning wheels or
progress bars with byphens is necessary just 'erase...\n', 'program...\n',
'verify...\n'.
I also get errors on the -r, even though it appears to actually have
done
the reset. The error is 'Could not reset target (no connection?)'
The last option in the jtag.py -h has -w which says "Wait for <ENTER>
before closing serial port.". I don't know if this option is applicable to
the parallel port, but obviously serial should be parallel.
BTW, I hope my comments and whinging are not interpeted as complaints.
You
guys have done a great job, and I really do appreciate everything you've
done. I'm really hoping that I can get away from the C-Spy garbage, and
start doing programming off the Linux box. While I'm a veteran programmer
of 20+ years in a number of languages, I also represent a typical end-user
at some points. The perspective is that I'm a person using Linux based
MSP430 tools, and these are the difficulties/errors I'm running into.
Not all embedded folks are going to be Linux savvy. While I used to do
a
fair amount of Perl programming, I am not a Python person. I would love to
have time to help in the development of the tool chain, but at this point in
my project life cycle, I can only be a user. So when a python script (a
language I don't know) acts up, I'm often at a loss. Especially when it's
dependent on a particular version of Python, or some Windows oddities.
So please, while I realize that a tone of frusteration has crept in here
and there, don't take it as dissatisfaction with what you folks have done.
I just want to program my F147's reliably, and get this monkey^wproject off
my back.
--John
----------------------
make[1]: Entering directory `/home/msp430/jtag/python'
python2 setup.py build
running build
running build_ext
Traceback (most recent call last):
File "setup.py", line 16, in ?
include_dirs = ["..", "../msp430"],
File
"/usr/src/build/87651-i386/install/usr/lib/python2.2/distutils/core.py",
line 138, in setup
File
"/usr/src/build/87651-i386/install/usr/lib/python2.2/distutils/dist.py",
line 893, in run_commands
File
"/usr/src/build/87651-i386/install/usr/lib/python2.2/distutils/dist.py",
line 913, in run_command
File
"/usr/src/build/87651-i386/install/usr/lib/python2.2/distutils/command/build
.py", line 107, in run
File "/usr/lib/python2.2/cmd.py", line 330, in run_command
print "\n"
File
"/usr/src/build/87651-i386/install/usr/lib/python2.2/distutils/dist.py",
line 913, in run_command
File
"/usr/src/build/87651-i386/install/usr/lib/python2.2/distutils/command/build
_ext.py", line 231, in run
File
"/usr/src/build/87651-i386/install/usr/lib/python2.2/distutils/sysconfig.py"
, line 126, in customize_compiler
File
"/usr/src/build/87651-i386/install/usr/lib/python2.2/distutils/sysconfig.py"
, line 408, in get_config_vars
File
"/usr/src/build/87651-i386/install/usr/lib/python2.2/distutils/sysconfig.py"
, line 313, in _init_posix
distutils.errors.DistutilsPlatformError: invalid Python installation: unable
to open /usr/lib/python2.2/config/Makefile (No such file or directory)
make[1]: *** [_parjtag.so] Error 1
make[1]: Leaving directory `/home/msp430/jtag/python'
make: *** [python] Error 2
[r...@linux jtag]#
-----Original Message-----
From: [email protected]
[mailto:[email protected]]on Behalf Of Chris
Liechti
Sent: Friday, October 25, 2002 22:23
To: [email protected]
Subject: Re: RE: RE: [Mspgcc-users] JTAG MSP-FETP430IF status
Am 26.10.2002 00:34:03, schrieb "J.C. Wren" <[email protected]>:
>I made sure it's using python2 also, although it's
>calling out python2.1 in the /usr/bin/env bang line.
no it's not. i forgot to mention that it's called from make where
just "python" is used, which defaults to python 1.5.2 on some
systems. so you'll probably need to chage it in the makefile:
>python ihex2c.py eraseFlash.a43 eraseFlash
chris
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
