> 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.
Would it be possible to write msp430 code for the pyserjtag adaptor that understood gdb serial protocol, and used it to drive the jtag lines - sort of like rproxy, but on the msp430? > 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 > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > >
