AVR-OCD-Document is verrrrrry old, it doesn't support some new devices. As I know, Atmel will never open the debugging protocol of their JTAG spec. You can hack current AVRs for the protocol, but if Atmel releases new chips which is different from the hacked protocol, it will be an endless work to follow.
For AVR8 support, there are other problems: 1. chips library Different AVR chips have different parameters, including Flash Page Size, EEPROM Page Size, Fuse Size and bit map, Lock bit map, Calibration Bytes Size. In my programmer VSProg, I use a .xml configuration file for all these settings. If use .cfg for a AVR8 chip, there will be many such configure files. 2. Fuse setting check Some fuse value will kill the chip(make it unusable). So it's better to use GUI to set the Fuse value, instead of passing hex value directly in the .cfg file. 2010/1/14 David Brownell <davi...@pacbell.net> > On Thursday 14 January 2010, Paul Fertser wrote: > > > The On-chip Debug support is considered being private > > > JTAG instructions, and distributed within ATMEL and to > > > selected third party vendors only. > > > > > > Clearly, someone needs to throw a JTAG/SPI sniffer at some of the > > > transactions issued by AVR studio, and so some "reverse engineering > > > for interoperability". :) > > > > Luckily someone already did that, see [1] (they used Free AVR ICE to > > sniff). > > > > [1] http://mirrors.igsobe.com/nongnu/freeice/AVR-OCD-Documentation.html > > Interesting ... not all that current, and if you look at > for example the ATmega32 docs it gives a different picture > of things (e.g. roughly what the four debug registers do). > But, clearly a decent start. :) > > > _______________________________________________ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > -- Best Regards, SimonQian http://www.SimonQian.com <http://www.simonqian.com/>
_______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
