On Fri, Apr 13, 2012 at 12:00 AM, Joerg Wunsch
<address@hidden> wrote:
Hayden Muhl <
address@hidden> wrote:
> avrdude: stk500v2_program_enable(): bad STK600 connection status: Target
> not detected (0x00)
I have no idea about that, nor did I run into that myself so far.
If AVR Studio is able to recover from this situation, it would be
interesting to trace its USB activities against the STK600 commands
AVRDUDE is issuing (which you can see using -vvvv).
I've been able to reproduce the problem, so my board is unusable again. Hooray?
I haven't analyzed the output at all yet, but I can possibly shed some light on what went wrong. I was in terminal mode fiddling with the clock speed, and I issued the command "sck 1". 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.
- Hayden