www.atmel.no/beta_ware has a new device support pack available for users of AVR Studio 4.12 SP3.
It adds support for some new Pico Power devices (ATmega329P, ATmega3290P, ATmega325P, ATmega3250P) in the assembler, simulator, JTAGICE mkII, STK500, AVRISP, AVRISP mkII, and AVR Dragon.
It also expands AVR Dragon support to the ATmega16 and ATmega169.
- Luke
It also expands AVR Dragon support to the ATmega16 and ATmega169.
That's what I wanted to hear! Cheers!
- Dean :twisted:
Quote:It also expands AVR Dragon support to the ATmega16 and ATmega169.That's what I wanted to hear! Cheers!
- Dean :twisted:
So Dean, I take it you have been convinced by the Dragon?
r/S
Hey Dean you can be the guinea pig with the new version of Studio this time :) let us know if it fixes the Dragon bugs and especially the ISP frequency problem. Will wait for your report before D/L...don't want to waste all of those electrons if it is still buggy :lol:
It also expands AVR Dragon support to the ATmega16
Yesss!!!
Yes, I am a Dragon convert. It doesn't steal the STK500's thunder, and it makes JTAG/dW more accessable to hobbyists. I still prefer my JTAG MKII and STK500 combination for serious AVR work (well, as serious as I can get with my abilities). Having said that, a second JTAG will come in handy (I neither own nor need AVRs larger than the Dragon's limits) and one can NEVER have too many ISP programmers ;).
I wish the MEGA169 had dW debugging; programming and debugging with only an ISP connector and no loss of IO ports! School finishes in half and hour so I'll be able to post my report in about an hour and a half. Stay tuned!
- Dean :twisted:
PS: I'm really riding the technology wave here; Dragon, prerelease GCC compiler, beta AVRStudio version....
And the results are in.
Installation was easy and fast. My Studio build still reads B490, but I'm unsure of whether the package updated the Dragon DLLs in addition to adding in new Dragon part XMLs (I assume this is how the programmer support is added, by modifying the device XML files). Once installed I tried to connect to my Dragon, and couldn't; my Dragon status LED changed to a solid red colour without the green link LED. A restart cured the problem - much to my relief - although I am unsure of whether than was a Windows problem unrelated to the new update.
I tested the new device support by programming my MEGA169 (Butterfly) via JTAG - all worked well. However, I am now completely unable to communicate with devices via ISP; the programming speed setting will not retain its value at all, and returns constant read errors.
If you need the support and only use JTAG (not sure about dW), test this out. If not, retain your existing setup.
- Dean :twisted:
Just my 2 cents to compensate my own inattention :(
After AtmegaProductPack0806 was apllied I was unable to enter ISP mode of AVRDragon (connected to target STK500 with ATmega16), too.
"Programming mode" dropdown list was of only one item - JTAG mode.
My workaround:
Now I was able to select ISP mode connecting to AVRDragon.
"ISP frequency not saved" issue still present,
but ISP programming, reading and verifying of Atmega16 was Ok in my case.
As for changes made by AtmegaProductPack0806 - one can look at the attached file.
The main difference is AvrMasterTimer.dll, version 1.0.053 -> 1.0.0.54.
m16def.inc - timestamp changed, version 2.21 -> 2.23, the rest is identical, IMHO.
m169def.inc - timestamp changed, nothing more.
New 32xx(P)def.inc added.
Changes in help files.
Part description files:
ATmega16.xml - build 203 -> 217, AVRDragon tag added in module_list. (Speed again is 8MHz, and I like my Atmega16 16PI :))
ATmega169.xml - build 265 -> 266, AVRDragon tag added in module_list.
ATmega32xx(P).xml.added
