On Wed, Apr 18, 2012 at 10:57 AM, Joerg Wunsch <[email protected]> wrote:
> No, sorry, that just tells me "Target not detected", but this is only > a translated message of the respective error code the STK600 responded > with (STATUS_TGT_NOT_DETECTED). > > What would be interesting is to see an USB sniffer trace from how AVR > Studio recovers from that situation. > > > While I was in terminal mode, the > > parms command showed an SCK period of 1 us, but now avrdude says SCK > period > > is 3.25 us. > > That's strange, but not fatal at all. It's just a bit slower than > intended. > > I was doing some reading, and found this. "Note that the ISP frequency (SCK) must be less than 1/4 of the target clock. The ISP frequency is set by the Atmel STK600 programming dialog in Atmel Studio." http://www.atmel.no/webdoc/stk600/stk600.programming_isp.html Since I first encountered this problem when fiddling around with SCK, I wonder if this could be the cause of my issues. It goes on to say that high-voltage programming may be necessary in this case. I will work on putting a USB logger on my Windows box so we can see how AVR Studio solves the problem. Let me know if there's one you recommend. - Hayden
_______________________________________________ AVR-chat mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/avr-chat
