Hi, I have started using pyjtag to program msp430 cards. I have no problem with erasing, programming and verifying, but I am having difficulty in getting the cards to start running at the end of the programming sequence. I had thought that the way to do this is with "jtag.py -eEpvr prog.hex". But I can't seem to get a reliable reset after programming. I've tried playing around with the _parjtag.reset() parameters from within the jtag.py program, and using idle to manually control the jtag functions (python is excellent for such interactive testing). My rough findings were that I could force a reset and restart of the card's program by manually sending a "reset(execute = 1, release = 1)" - this would start the card's program, but it also gave the "Could not reset target (no connection?)" error. But after that, a normal (0, 0) reset worked on that card - at least until I had reprogrammed the card.
Has anyone any hints as to what is going on, and what is the easiest way to get a reset-and-go at the end of the programming sequence? I am using W2K, the Kickstart FET, and our own msp430 cards, which have a Dallas reset device on the reset line for brown-out detect (with an internal 4k7 pull-up), and their own 3.3V supply on the card, in case that makes any difference. I'd like to get a nice reset at the end, because it would make it easier for the production folk for the program to start automatically after programming - on this card, it gives a short beep, which is a nice confirmation that the card is working properly. Of course, even without that, pyjtag is still *way* better that our old method - programming using C-Spy. mvh. David "I love deadlines. I love the whooshing noise they make as they go past." Douglas Adams
