Chris Liechti <[email protected]> wrote:... looks like you're using the TI backend. so it is their code for their chips.
if you run msp430-jtag with --backend=mspgcc -DDD it runs the code you can look at here http://mspgcc.cvs.sourceforge.net/mspgcc/jtag/msp430/JTAGfunc.c?revision=1.14&view=markup line 581 and following ... the fuse check needs some pulses on the JTAG interface. when these are not correct is the JTAG going into bypass mode. it is doing the same for blown fuses and correct pulses. but if you previously were able to use the JTAG successfully you have good chances that the check works reliably chris Excuse me for straying slightly out of the topic. Is there existing code (like what Chris pointed out above) that deals with 2-wire (SBW) JTAG? I tried the code in the SBW version of TI SLAA149d and found that I cannot reliably synchronize with the target FSM. (This has nothing to do with the JTAG Fuse.) Specifically, ResetTAP_sbw() and the first few lines of code in GetDevice() before it calls ResetTAP_sbw() do not seem to work consistently. These correspond to lines 48-84 and 121-146 of the code Chris references to, but I was testing the equivalent code in SBW version of SLAA149d. Thanks. --------------------------------- Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.
