I have seen quite a lot of JTAG tools from TI falsely report that the fuse is blown. But I cannot remember the specifics. I suspect that they do not use JTAG bypass to test. I do not know if MSP430 JTAG programmer Version: 2.3 is any better. If you do not have the source code, one way to find out is to use a logic analyzer on the JTAG pins.
Using bypass to test the fuse seems a reliable way. Because it relies on something specific happens to conclude the fuse is blown. (As oppose to rely on something does not happen to conclude the fuse is blown.) However, I think using the bit pattern 0xAAAA to test bypass is not a very good choice. It is too easy to change it into 0x5555. I would use a few other bit patterns to positively identify bypass. [email protected] wrote: When issueing a reset with "msp430-jtag.exe -r" the following happens: ( Using MSP430 JTAG programmer Version: 2.3 ) ----8<----8<---- Use -h for help Cleaning up after error... Reset and release device... An error occoured: Could not reset target (no connection?): Could not access device - security fuse is blown ----8<----8<---- Is this reliable? i mean is it tested with bypass and so on like in "slaa149" on part 4.3 "testing for a successfully programmed fuse" - or could there be another possibility for this same error to happen with fuse okay? Ciao, Helmut------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users --------------------------------- Never miss a thing. Make Yahoo your homepage.
