Hi,
just a question regarding the jtag interface. Chis wrote that the
pyjtag interface is connected to the PC's parallel port. Is there a
chance to connect a the msp via usb2parallel port interface? Would it
work? Would it be a big task to do the required adaptations om pyjtag?
This would allow for debugging on Macs too and on PC's if there is no
parallel port anymore in the next generation.
Peter
Am Mittwoch, 11.02.04 um 17:48 Uhr schrieb Ethan Gold:
Chris,
Thanks for the extremely helpful info.
I've got at least the little LED flashing during pyjtag activity on
my protogype board under linux now.
It's a shame we won't be able to dev on our Macs, but we're
a linux shop too, and my thinkpad was getting lonely.
Just for the record, I'm running the Fedora Core-1 Linux distro
w/ the gcc-3.2.2 rev and the msp430 additions dropped in.
In case anyone else is messing with OS-X, the tools build easily
under OS-10.3 if you _make sure you install the X-code tools_
instead of the 10.2.x compilers, which at first seem to work (but
won't fully build gcc). The X-code gui isn't required, just the rebuilt
native gcc toolchain for darwin.
Thanks again,
-E
On Feb 10, 2004, at 2:34 PM, Chris Liechti wrote:
Ethan Gold wrote:
I have both the TI serial and parallel jtag adapter units, and was
under
the impression that the pyserjtag and pyjtag tools would work with
them,
but the documentation is not very clear. Now I think that it will
only work
with this circuit diagram I finally found on the website. Does this
diagram
> implement a functionally equivelent serial jtag box to the TI
version?
yes, pyserjtag is for that box, for which you can find the schematic
on our website, somewhere... it's not compatible to other serial
programers.
pyjtag uses the usual jtag adapter desing that comes with all the FET
kits from TI. other vendors also sell adpaters with that cicuit or a
compatible one.
What I really need is for the serial jtag adapter to work, as there
are few
parallel ports implementations for modern MacOS machines, and the
API's will surely never be supported if there is a RS232 alternative
(which
is just fine with me).
mind you, the pyserjtag adapter does only support programming, NO
debugging.
if you just want do download thats fine then, but then you can also
have an other alternative: the BSL. the MSP has a built in ROM that
allows programming over the serial port.
So... what's the story with the jtag communications tools? Can I use
them
with the TI JTAG boxes?
TI-hw down-/upload debugg/GDB PCcon MSPcon wires(3)
pyjtag: yes yes yes parport JTAG >=5
pybsl: - yes no RS232 ser 5
pyserjtag: no yes no RS232 JTAG >=5
gdbstub(1): - - yes(2) RS232 ser 3
(1): not yet implemented, but a possible solution: a small software
on the MSP, that talks GDB protocol over the serial line. that would
allow some debugging even w/o JTAG, but breakpoints could not be set
everywhere and there are other limitations.
(2): as mentioned in (1), there are limitations due to the the nature
Flash. you cant set breakpoints everywhere, the downloaded program
would need to have calls at the appropriate places. it requires a
serial port, it uses space in RAM/Flash, ...
(3): connection from the programer to the target:
JTAG: minimum 4 data lines + GND, RST recomended and TEST needed on
some targets.
BSL: GND, RX, TX, TEST or TCK and RST to activate the BSL
gdbstub: gdb protocol over the serial: GND, RX, TX
in the future we may support other programer hardware/connections
too, but i cant promise anything.
chris
