[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[avrdude-dev] [bug #37997] AVR109 not working
From: |
Joerg Wunsch |
Subject: |
[avrdude-dev] [bug #37997] AVR109 not working |
Date: |
Sun, 08 Sep 2013 21:07:35 +0000 |
User-agent: |
Mozilla/5.0 (X11; FreeBSD i386) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/27.0.1453.110 Safari/537.36 |
Follow-up Comment #8, bug #37997 (project avrdude):
One discrepancy immediately catches attention:
The "OK" log says:
Programmer Type : avr910
The "Failed" log says:
Programmer Type : butterfly
Given the large number of device codes that are supported by
the programming hardware, I really doubt this is actually a
bootloader. (Bootloaders usually support exactly one device,
the device they are operating on.)
Did you try with both, -c butterfly (aka. -c avr109), as well
as -c avr910? While both implementations share the same
roots, their behaviour is not exactly the same.
One of the consequences of this might be that in the working
log, we can see:
avrdude_5_2: Send: T [54] ^ [5e]
i.e. the device code 0x5e is chose, which is the correct one
for an ATtiny2313. In the "failed" log, we see:
avrdude: Send: T [54] . [13]
avrdude: Recv: . [0d]
avrdude: devcode selected: 0x13
i.e. it picks device code 0x13 which belongs to an AT90S1200.
This is done since the bootloader implementation just picks
the very first device code it can see, since many bootloaders
simply don't spend much attention on the device codes they
are claiming to support, so picking the first one is usually
the best choice.
However, for a standalone programmer, there are subtle
differences in the programming algorithm between AVR's
grandfather AT90S1200, and the ATtiny2313, which might explain
the failure.
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?37997>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/