AVR Freaks

I don't like being beaten by technology though.

If I simply connect to it in bootloader mode and type "S" (which is the AVR911 command to get signature) it responds "AVRBOOT" as expected. If I then let avrdude have a talk to it I see:

Connecting to programmer: .avrdude.exe: Send: . [1b]
avrdude.exe: Send: S [53]
avrdude.exe: Recv: A [41]

avrdude.exe: Recv: V [56] R [52] B [42] O [4f] O [4f] T [54]
avrdude.exe: Send: V [56]
avrdude.exe: Recv: 1 [31] 5 [35]
avrdude.exe: Send: v [76]
avrdude.exe: Recv: ? [3f]
avrdude.exe: Send: p [70]
avrdude.exe: Recv: S [53]
Found programmer: Id = "AVRBOOT"; type = S
    Software Version = 1.5; No Hardware Version given.
avrdude.exe: Send: a [61]
avrdude.exe: Recv: Y [59]
Programmer supports auto addr increment.
avrdude.exe: Send: b [62]
avrdude.exe: Recv: Y [59]
avrdude.exe: Recv: . [01]
avrdude.exe: Recv: . [00]
Programmer supports buffered memory access with buffersize=256 bytes.
avrdude.exe: Send: t [74]

Programmer supports the following devices:
avrdude.exe: Recv: . [00]

avrdude.exe: Send: T [54] . [00]
avrdude.exe: Recv: . [00]
avrdude.exe: error: programmer did not respond to command: select device
avrdude.exe: initialization failed, rc=-1
             Double check connections and try again, or use -F to override
             this check.

avrdude.exe: Send: L [4c]
avrdude.exe: Recv: . [0d]
avrdude.exe: Send: E [45]
avrdude.exe: Recv: . [0d]

avrdude.exe done.  Thank you.

which also shows avrdude sending the 'S' command and getting "AVRBOOT" back. It then sends 'V' for version and gets "15" which is interpreted as V1.5. Looking at AVR109:

then it seems the command sequence sent is:

S> (return software identifier)

<AVRBOOT

V> (return software version)

<15

v> 

<? (possibly not surprising as 'v' does not appear in the list??)

p> (return programmer type)

<S (which apparently means "Serial")

a> (auto increment address)

<Y (Yes, it does autoincrement)

b> (check block support)

<Y[01][00] (yes, 0x100 block size)

t> (return supported device codes)

<[00] (we don't list partcodes)

T[00]> Select device type [00]

<[00]

And this is where it all seems to break down. I'm guessing the problem starts when the 't' command just returned [00]

Some AVR109 source I found has:

            // Return supported device codes.
            else if(val=='t')
            {
#if PARTCODE+0 > 0
                sendchar( PARTCODE ); // Supports only this device, of course.
#endif /* PARTCODE */
                sendchar( 0 ); // Send list terminator.
            }
            
            
            // Set LED, clear LED and set device type.
            else if((val=='x')||(val=='y')||(val=='T'))
            {
                recchar(); // Ignore the command and it's parameter.
                sendchar('\r'); // Send OK back.
            }

and also:

/* definitions for device recognition */					
#define	PARTCODE	0			
#define	SIGNATURE_BYTE_1	0x1E			
#define	SIGNATURE_BYTE_2	0x95			
#define	SIGNATURE_BYTE_3	0x16			

so it seems like having PARTCODE 0 is a valid thing to do yet avrdude does not seem to want to accept this.

Oh well, I probably will give in and simply blast it.