avr
/
avrdude
mirror of https://github.com/mariusgreuel/avrdude.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

The avr109 programmer type no longer chokes on a wrong avr910 device 

ID, so remove that description.


git-svn-id: svn://svn.savannah.nongnu.org/avrdude/trunk/avrdude@648 81a1dc3b-b13d-400b-aceb-764788c761c2
This commit is contained in:
Joerg Wunsch 2006-09-07 19:34:17 +00:00
parent 8d207dbaf1
commit 27216a0cd6
3 changed files with 6 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ChangeLog
View File

@ -1,3 +1,9 @@
2006-09-07 Joerg Wunsch <j@uriah.heep.sax.de>
* avrdude.1: The avr109 programmer type no longer chokes on
a wrong avr910 device ID, so remove that description.
* doc/avrdude.texi: (Ditto.)
2006-09-07 Joerg Wunsch <j@uriah.heep.sax.de> 2006-09-07 Joerg Wunsch <j@uriah.heep.sax.de>
* jtagmkII.c: When failing to start in ISP mode, try * jtagmkII.c: When failing to start in ISP mode, try

7
avrdude.1
View File

@ -707,10 +707,3 @@ Page-mode programming the EEPROM through JTAG (i.e. through an
option) requires a prior chip erase. option) requires a prior chip erase.
This is an inherent feature of the way JTAG EEPROM programming works. This is an inherent feature of the way JTAG EEPROM programming works.
This also applies to the STK500 in parallel programming mode. This also applies to the STK500 in parallel programming mode.
.Pp
The device IDs used by AVR910 and AVR109 do not match, so the
avr109 (aka. butterfly) programmer might report
.Dl "selected device is not supported by programmer" .
Use the -F option to force
.Nm
to continue anyway.

12
doc/avrdude.texi
View File

@ -1919,18 +1919,6 @@ Problem: I'm not using linux and my AVR910 programmer is really slow.
Solutions: The reasons for this are the same as above. Solutions: The reasons for this are the same as above.
If you know how to work around this on your OS, please let us know. If you know how to work around this on your OS, please let us know.
@item
Problem: AVRDUDE says my device is not supported when using the AVR109 boot loader
Solution: Currently, AVRDUDE uses the AVR910 device codes given in the
@code{avrdude.conf} file, and matches them against the list of supported
devices reported by the programmer. Unfortunately, there are no device
codes at all for some of the newer AVR devices, and even worse, the
device codes listed in @code{preprocessor.xls} of appnote AVR109 do not
match those once specified in AVR910.
Use the -F option to force AVRDUDE to continue anyway.
@item @item
Problem: Updating the flash ROM from terminal mode does not work with the Problem: Updating the flash ROM from terminal mode does not work with the
JTAG ICEs. JTAG ICEs.