Hi, I now use pyjtag and gdb regularly. Mostly I call pyjtag directly as part of my "make", since it burns the chip far faster than downloading via gdb (any ideas as to why that might be the case?). It works well together, and I can happily leave rproxy running even while using pyjtag.
However, sometimes the code will not verify - I get verify errors from pyjtag, and if I try to use gdb to download, I get "Remote failure reply: E00". I don't know how much of the code has actually been burnt properly - the reset vector certainly isn't. I can, however, download the same hex file using C-Spy (I'm on W2K here). If I make any sort of change in the code, and recompile, then I generally have no problem burning the new version. I can find no patern as to what works and what fails - my guess is that there is a bug that hits for some particular checksum value, since it is apparently random whether my code has the problem or not, but is entirely consistant for a given hex file. I can email over a couple of hex files - one that works, and one that fails - if it helps. I am using the TI FET, with an MSP430F149. Thanks for any ideas, David Brown Norway.
