"Steve Franks" <[EMAIL PROTECTED]> wrote: > Ok, now I feel like a dufus. The problem appears to be a function > of the jtagiceII, the one variable I never changed while pulling out > my hair last night/this morning. (At least my pcb's are proven good > now) - WIth it (jtagice) removed, toggling the reset pin causes > normal execution.
Curious, most recent version/update of AVR Studio (and thus the JTAG ICE firmware) is in use? > Note this behavior happens with the reset pin on the jtagice > disconnected as well, so it's not like the jtagice is holding the > device in reset continuously, which it is known to do. JTAG doesn't require an external reset pin to hold the device in reset, it can also do this via the JTAG engine. If JTAG communication then gets lost, there's nothing that would restart the target. Normally, upon disconnecting from the ICE, the debugger is saying the ICE to have the target continue operating, and then it says "good-bye" to the ICE (which is the point when the comms LED turns red again). > The only major annoyance is now ripping the jtagice off this tiny > board every time we program and touching the reset pin with a > resistor (no mean feat on an MLF/QFN package <whine>). If you only want to download your firmware, you could do that with AVRDUDE. However, the last WinAVR's AVRDUDE version was not compiled against libusb, so you can only talk via RS-232 to the ICE, but it should be doable. (It's probably getting up to 50 % of the speed you could achieve over USB.) -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) _______________________________________________ AVR-chat mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/avr-chat
