Grant Edwards schrieb:
The mspgcc web page talks about pyJTAG and pyBSL. Those
_appear_ to have been replaced by the "python" directory. That
this is true
directory contains much more recent files and nobody seems to
be using the old utilities. Is that the case? Does the web
page need updating?
probably
I've checked out a copy of the "python" directory, and run
"python setup.py install" as described in the readme.txt file:
...
According to the readme.txt file "The msp430-bsl and
msp430-jtag tools are installed to the binary directory
/usr/local/msp430/bin [...]" .
Except they aren't.
There is no /usr/local/msp430.
i know, that isn't perfect yet.
setup.py install installs the "mspgcc" package into the system wide
python-site packages. this enables you to write your own programs using
its jtag and bsl drivers, or you can install/symlink the msp430-*.py
tools to a path in your $PATH.
for msp430-jtag, you have to make sure that the l.so files are found. in
case of problems try msp430-jtag -DDDDD which should print the search path.
see also below. there i use a wrapper script, so that the libs don't
need to be installed system wide.
Can somebody loan me a clue on how to install msp430-jtag?
you may have a look at the makefile in CVS/packaging, especially the
targets pytools-build and pytools-install.
here i just copy all the parts to the target "bin" directory. this
creates the mspgcc package subdirectory under bin. but that isn't clean
for un"x platforms. i usually install to /opt/mspgcc, which makes the
situation less worse as the "mess" is all in the separate tree ;-)
i installed the entire toolchain using this makefile. (it build+installs
on linux, on windows it's used to create the installer)
chris
