Re: MSP430 JTAG over USB for Linux?

On Sep 28, 2:29 pm, "Michael N. Moran" <mnmo...@xxxxxxxxxxxxx> wrote:

I've looked at the gdbproxy, but I'm having a hard time
understanding exactly what it uses to talk to the USB
JTAG device.

It uses closed proprietary code. That's the only way TI will allow
their JTAG to be used. But it is free.

Sorry ... I'm old and confused

join the club

don't the .dll libraries only run under Windows? Or is there some WINE stuff going
on here?

No WINE, but if the low-level interface of the JTAG devices is close
enough to the real TI JTAG devices, then the closed code I mentioned
should work fine.

The best related thread that I found here was yours,
Grant. :-)

Grant walks on water. He's one of the few truly smart people who
doesn't mind stooping down to answer questions from all kinds of
people. I don't know why this is getting more rare on the Internet but
it's distressing.

Sorry about being *thick*, but I just like to understand
how these things work before I fork out the cash.

The cash outlay can be very small. You can try out the software using
a EZ430 USB dongle and the total outlay is around $20. They come with
a built-in JTAG device that uses the smaller pin count Spy-bi-wire
JTAG protocol.

At least one guy on the net is selling little adapters to allow that
JTAG device to be used with other msp430 devices that also support Spy-
bi-wire. You only really need to buy a more expensive JTAG device if
you want to use a member of the family that doesn't support Spy-bi-
wire, or if you can leverage a corporate budget :-)

Eric

.

Relevant Pages

  • Re: MSP430 anyone?
    ... I followed all installation instructions. ... When I plug it in USB, it's recognized as a MSP-FET430UIF JTAG device, ... Are you sure you're not looking for the USB driver for Windows ...
    (comp.arch.embedded)
  • Re: MSP430 anyone?
    ... I followed all installation instructions. ... When I plug it in USB, it's recognized as a MSP-FET430UIF JTAG device, ... Are you sure you're not looking for the USB driver for Windows ...
    (comp.arch.embedded)