[avrdude-dev] Windows status + RFC

[E. Weddington]

Ok, now I understand what's going on with the stk500.

Some of it was also my ignorance of avrdude's normal operation.

The unknown response of 0x11 is a failure to enter programming mode. 
Which is a normal response if your stk500 is not hooked up to 
anything. So I hooked it up and did a read of my m128 successfully!

Since I'm new at CVS I still just want to run the attached patch by 
everybody.

The 0x11 response should not be unknown, it's a common response. 
Atmel's AVR Studio gives an error message for the same thing. This 
patch just gives a descriptive error message for this. 

So it seems that stk500 support works under Windows. I'll work with 
Joerg on getting the ppi to work.

Eric

Index: avrdude/stk500.c
===================================================================
RCS file: /cvsroot/avrdude/avrdude/stk500.c,v
retrieving revision 1.17
diff -u -r1.17 stk500.c
--- avrdude/stk500.c    14 Feb 2003 04:09:50 -0000      1.17
+++ avrdude/stk500.c    14 Feb 2003 22:31:26 -0000
@@ -385,7 +385,16 @@
     return -1;
   }
 
-  fprintf(stderr, "%s: stk500_program_enable(): unkown response=0x%02x\n",
+  if(buf[0] == Resp_STK_FAILED)
+  {
+      fprintf(stderr, 
+             "%s: stk500_program_enable(): failed to enter programming 
mode\n", 
+                 progname);
+         return -1;
+  }
+
+
+  fprintf(stderr, "%s: stk500_program_enable(): unknown response=0x%02x\n",
           progname, buf[0]);
 
   return -1;