Hi there,
I did a quick search about this issue in the mailing- and bug-list but
did not find an answer (which might imply that may search was too
superficial). However:
When I use a jtag3 and the current head of the svn trunk and try to
program or read the fuse with a jtag3 in PDI mode, then I always end up
reading and writing fuse0. A quick search through the source code (and
the /etc/avrdude.conf file) reveals that, e.g., in jtag3.c in
jtag3_read_byte() every memory type starting with the word "fuse" ends
up to address fuse0. The offset specification in the config file is
ignored. I'm trying to address the fuses like this:
avrdude -p atxmega128a1 -c jtag3pdi -U fuse2:r:/tmp/blah:h
Also, running above command with four "-v" flags reveals that the data
sent to the jtag3 does not change at all if varying the memory type
among fuse{0,1,2,4,5}
I'm very well aware of the fact that the trunk of a vc-repo always
reflects work in progress. If this is indeed a bug, I would open an
issue in the bug tracker and suggest a fix in form of a patch against
the head of the trunk. However, as this is such an obvious issue, I
rather suspect that it is already fixed in some working copy of the core
developer(s).
Otherwise JTAG3 works quite well, I'm also able to debug with avarice.
I'm using this for some xmega128a1 module. Many thanks to Joerg Wunsch.
Best,
Claus
--
Claus-Justus Heine hims...@claus-justus-heine.de
http://http://www.claus-justus-heine.de/
_______________________________________________
avrdude-dev mailing list
avrdude-dev@nongnu.org
https://lists.nongnu.org/mailman/listinfo/avrdude-dev
