Enter The Dragon

Go To Last Post
386 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ok this may be a good point to start posting Dragon related stuff. A new forum would also be nice!

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

careful Bruce Lee dosent sue you for copyright on the name of your post... oh hang on he is dead. lol

sorry couldnt help my self

:arrow: Dan :!:

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

omi

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well, The big question is when (and where) can us normal folks buy one? Can Atmel give us a status update on when Digikey etc will be recieving stock, and if there will be enough volume for the initial 'christmas rush'?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What we know about the Dragon:

Cost US49.00

Availability end of July (2006 we think :-) )

Pictures: https://www.avrfreaks.net/index.p...

Atmel's link: www.atmel.com/avrdragon

It needs SP3 for studio available here: http://www.atmel.no/beta_ware/as...

Help file for SP3 if you don't have it yet and want to have a fuller preview of the Dragon:
https://www.avrfreaks.net/index.p...

What it can do:

The following devices are currently supported by AVR Dragon.
Programming Emulation
Device ISP HVSP PP JTAG JTAG dW Remarks

ATmega48/88/168 x x x
ATmega8 x x ATmega8 does not have on-chip debug function
ATmega32 x x x x
ATmega128 x x x No emulation support for devices > 32K Flash

ATtiny13 x x x
ATtiny25/45/85 x x x
ATtiny2313 x x x

The table doesn't come up right. See attached doc file.

Attachment(s): 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Downloaded the latest beta SP3 build as of today on a spare machine.
Well I am happy as a pig in slop! :mrgreen:
Have been debugging an ATmega32 (using about 50% code space) project for the last couple of hours using the Jtag on the Dragon connected to the target pcb and no hickups yet. Actually this could not have happened at a better time as one of my Atmel JtagI died yesterday (that damn flat ribbon cable thingie) and I was using my spare JtagI to connect to a Atmega128 project which the Dragon does not support for Jtag. So I am back in business thanks to Atmel.....Thanks so much Dag!
Tommorrow the ATTiny2313 DW tests for me.
If you wanted to know where the Atmega2560 chips are this critter uses them (along with an Atmega128) and since I am sure the Dragon is going to be a hit it may be tough getting some for a while.

Last Edited: Sat. Jul 1, 2006 - 04:39 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

also if you read the help file you will notice this little tidbit

" If the USB driver is correctly installed and AVR Dragon is connect to the PC, the green LED inside the encasing next to the USB connector will be lit."

Maybe they planned to have a case "encasing" for this critter at one time.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ok stretching the Dragon's legs...

The first suggestion I have is that Atmel should supply the USB cable and at least the 6 way and 10 way cables for ISP/DW and jtag. Even though I knew no cables were forthcoming and I have a supply of the 6 and 10 way connectors and ribbon cable I still had to go to the local Coles to get a USB cable as I forgot to get one before :( At AU$8.00 for the USB cable it would add about 10% to the cost of the Dragon (in AU$), I know I could get a cheaper one but by the time I go to an electronics/IT shop the cost in time and petrol woudl add up. The 6 way connectors are not easily available as much as the 10 way and if a was a beginner and just put togethet my pride and joy with say a tiny2313 on a bit of veroboard on a Friday afternoon having all the necessary cables would make life easier and having to purchase the cables/connectors anyway the extra cost to the Dragon would be a lot less if they were supplied. This would need a larger packing box of course. Just my 2c worth :-)

I startet by trying out ISP with a Mega8. For some reason it locked up and all leds went off and lost comms with Studio, the only way to restore things was to unplug the USB lead. There seems to be a bug with the ISP programming frequency retention with the Dragon/SP3 (latest downloaded today). It seems to revert back to 8MHz which causes an error. I can put it down to 250KHz but it seems to want to revert to 1MHz by just going to different pages in the programming screen which is of course no good to program new chips with the internal 1MHz clock enabled. I have managed to program a M8 by resetting the frequency down to 250KHz but by exiting the program and restarting again the programming freqeuncy goes up to 8MHz (yes I write the 250KHz value to the Dragon). Can someone else please verify what I'm experiencing before we put an official bug report?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JS
Not sure about the Mega 8 as I do not have one....but I worked with a Mega 32 yesterday and today..using jtag..all worked fine and Dragon is humming along...I did not have any 6 pin cables (did not get any with my STK500) so I ordered them and they will be here Wednesday so I can go a bit further with the testing on DBW and the Tiny2313....could "southern engineer" something for the cable but ...

Dragon needs something else I am working on..... :?: :D

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

If you have the room around the ISP connector in the target board you should be able to use a 10 w ribbon (CAREFULLY) and try out the normal ISP feature to see if you get what I'm getting.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I assume you updated the firmware on the Dragon?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

those really cheap 6to10 pin adapters at ere.co.th are really handy :)

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Actually I have two 10 pin squid cables that came with my JTAGI..using them on each end of a 10 pin to 10 pin female I should be able to make a half decent Cable till the real ones arrive

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I assume you updated the firmware on the Dragon?

Yep, first thing.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yep Gwen ...I just orered several of those including a box load of those single wire jumper cables they have that are such a good deal..maybe they will come later next week

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JS
Since its way past midnight I best wait till my head is clear tommorrow with the squid "thingie".....I will try ISP with the mega32 and see if it works okay and report back....you will be asleep by then

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You totally would not believe how many of the ere jumpers we have here...
They are usefull for wiring up stuff to PC boards like speakers, volume controls..etc

Then when you need to take out the board to work on it you just pull the connectors off the pins on the
board and it is just so easy :)

Way better than unsoldering stuff.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

the short ere jumpers will come in handy when wiring up the 40 pin header to the hv programming header on a Dragon color coded just like the Dragon Guide shows it

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I bought a ERE ISP programmer and haven't regretted for a second. But on advice from this forum I threw in a bunch of those jumper cables.... fantastic. my newest technique is making custom cables using hot-glue... the best combo is the home made ISP squid + the DIP "Claw" which works great saving me putting an ISP connector on my PCB's or breadboard.

looking forward to getting a Dragon and being able to use debugwire..

Whats the avrdude/avarice situation like? will this be a minor update to some config files or are major changes needed?

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I best wait till my head is clear tommorrow with the squid "thingie

Good idea, don't want to do the "St George" thingy and slain the Dragon! (would it turn into black goo? ) This new tool is causing PUNdemonium :lol:

Well can't get JTAG programming to work at all, the ISP frequency reverts to 1 MHz (even though I change it to 250KHz) which should work on a 16MHz Mega128, now it has gone back to 8MHz which would not be much good. I'll try tomorrow with a Tiny2313 and see if I can get DW running.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hey JS,

I upgraged AVRStudio and SP3 eariler in the week, in anticipation of the arrival of my new Dragon.

After the upgrade and while continuing on with the current project, I had a really strange issue. Even though I selected the path to the object file that I wanted to put into the target device, Studio would always download an object file of it's own choosing. With the original installation of SP3, I did not upgrade AVRStudio, itself. Also, during the initial installation of SP3, I told the installation wizard to preserve all of the project settings during the installation. After many hours of beating my head on the bench, I finally opted to un-install AVRStudio and re-install it and SP3. During the re-installation of AVRStudio and SP3, I told the installation wizard to ignore all of the project settings.

Also, when running the simulator, I always got a target stack overflow of some kind and the project code would crash with the execution of the first simulated instruction. Re-installing AVRStudio and SP3 fixed this two.

After re-installing AVRStudio and SP3, I had no further problems with downloading the selected object files to my target project and the stack issue went away.

One other thing, the copy of the original SP3 file that I used to perform the original installation of SP3 had a revision date that was several several days old. The AVRStudio and SP3 program file dates that I downloaded from Atmel's web-site to do the re-installation were only hours old.

I can't say the above is related to your problem but, it rings of similiaraties.

Hope this helps.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

Last Edited: Mon. Jul 3, 2006 - 12:42 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Carl,

There have been two issues of SP3 so far - one was build 485 and the most recent is build 488. In the AVR Studio 4 forum here Torleif has admitted that there was a spurious stack warning message in 485 - maybe this is what you saw?

Cliff

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

clawson wrote:
Carl,

There have been two issues of SP3 so far - one was build 485 and the most recent is build 488. In the AVR Studio 4 forum here Torleif has admitted that there was a spurious stack warning message in 485 - maybe this is what you saw?

Cliff

Maybe! It's all good now, though.

But, the problem JS is having and the issue that I had with AVRStudio with the object file path selection sounds suspeciously similiar.

It might be better that JS simply un-install AVRStudio and SP3 and re-install both using the most current versions available, and without preserving any AVRStudio settings.

Anyway, I thought I would make my experience with the AVRStudio and SP3 upgrade available in case others were having similiar issues.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
my newest technique is making custom cables using hot-glue...

That custom cable is really nice. What type of glue is that and how do you apply it?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well, my Dragon arrived today.

It took me about ten minutes to get the JTAG working - at least so I could read the microcontroller ID.

I'm in sort of a predicament in that, the only microcontroller that I have that the Dragon supports is the Mega128. No problem though, because I simply removed the Mega64 from my STK501 and inserted the Mega128. I also had to change iom64v.h to iom128v.h. As their big brother, little brother, it's all good.

The Mega128 programmed just fine, and boy, is it fast compared to ISP!

The first thing that I notice is that I have to remove the JTAG cable before the Mega128 is released to run the application program. Not ever having used JTAG before I ask, is this normal? I didn't have to remove the programming cable with ISP. It was just program and play, program and play, etc..

As an experiment, I put the Mega64 back into the STK501 and erased it. The Dragon must have erased the Mega64 because, I could not varify the application in the Mega64 and, I also could not run the application, once erased. So, trying another experiment, I tried programming the Mega64 with the Dragon using the Mega128 selection. Wha-La! The Mega64 programmed right up and ran the original application properly.

Now, obviously the JTAG fuse is selected and I had to enable that with ISP but, I also assume that the On Chip Debug Enable (OCDEN) fuse will need to be checked to use the live debug feature in AVRStudio. Is this correct.

Finally, When attempting to go live with JTAG and the Mega128 in AVRStudio, it so happens that, the Mega128 is not currently supported in AVRStudio using the Dragon and JTAG with live simulation. I wonder how long it will be as, I have no other AVR's that are supported by the Dragon at this time.

Gee, I've got:
5 ATtiny2313's SOIP
2 Mega8515's PDIP
2 Mega16's PDIP
3 Mega16's TQFP
30 Mega32's TQFP
20 Mega64's TQFP
5 Mega128's TQFP
And:
10 AT902313's PDIP

I've got plenty of controllers but nothing supported with both, AVRStudio and the Dragon.

I'll have to assume that with all of the shortages lately, Digi-Key will be a long time in servicing my needs.

So, the two questions are:
1. I have to remove the JTAG cable before the Mega128 is released to run the application program, is this normal?
2. Does the On Chip Debug Enable (OCDEN) fuse will need to be checked to use the live debug feature in AVRStudio?

Thanks!

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

Last Edited: Mon. Jul 3, 2006 - 08:46 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Finally, When attempting to go live with JTAG and the Mega128 in AVRStudio, it so happens that, the Mega128 is not currently supported in AVRStudio using the Dragon and JTAG. I wonder how long it will be as, I have no other AVR's that are supported by the Dragon at this time.

Docs say no Jtag emulation for devices above 32k if that is what your are trying to do and previous info indicates no plan for support later...but it does support ISP for Mega128...see the chip support matrix in the help file?

Quote:
I have to remove the JTAG cable before the Mega128 is released to run the application program, is this normal.

When I use Jtag with Mega32 and AVRSTUDIO I do not remove cable

Quote:
Does the On Chip Debug Enable (OCDEN) fuse will need to be checked to use the live debug feature in AVRStudio.

I enable it

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

bluegoo wrote:

Quote:
When I use Jtag with Mega32 and AVRSTUDIO I do not remove cable

But are you using the Dragon? I really ment this to be a Dragon specific question to find out if the other Dragon recipiants have the same circumstances. Is so, I'm good with it. If not, I would like to discover what theyt have done differently.

Thanks for your answers, though...

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I guess I do have one more question for Atmel...

Am I to assume (ASS-U-ME) that, as I can in fact program the Mega64 and Mega128 with the Dragon that, 32K will be the limit for their FLASH programming with the Dragon?

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Their is no limit on FLASH programming. The 32K limit is just for JTAG OCD.


My AVR Site

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
But are you using the Dragon? I really ment this to be a Dragon specific question to find out if the other Dragon recipiants have the same circumstances. Is so, I'm good with it. If not, I would like to discover what theyt have done differently.

Yes...just trying to offer some hep although it may not be much :)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

bluegoo wrote:
Quote:
But are you using the Dragon? I really ment this to be a Dragon specific question to find out if the other Dragon recipiants have the same circumstances. Is so, I'm good with it. If not, I would like to discover what theyt have done differently.

Yes...just trying to offer some hep although it may not be much :)

So, bluegoo,

Are you are saying all of the below!!!:

1. you do have a Dragon.
2. Yyou are programming the target with the Dtagon.
3. You do not have to pull the JTAG cable off of the target once programming is complete to get the program to automatically run the target application.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I can in fact program the Mega64 and Mega128 with the Dragon

The M64 in NOT supported (in theory) for programming YET, just the M128, but as they should be very similar you have got away with it, infact there is no device selection for the M64 in the dropdown menu.

I'm still having problems with keeping the ISP frequency at 250KHz, it will revert to 8MHz. It will work for the session but once I leave the programmer interface and restart it it will go back to 8MHz. This is my version of Studio

AVR Studio		4.12.488  Service Pack 3
GUI Version		4, 12, 0, 488



Operating System
Major			5
Minor			1
PlatformID		2
Build			2600
Service Pack 2

Plugins:

AvrPluginAvrAsmObject	1, 0, 0, 43
AvrPluginavrgccplugin	1, 0, 0, 6
Stk500Dll			1, 0, 0, 60

The M128 programs ok in ISP mode otherwise.
From my previous post:

Quote:
can't get JTAG programming to work at all
That's becuse I didn't select jtag programming mode!! :oops: jtag programming works and yes it is F A S T, I can confirm that the processor does NOT get released after programming Carl.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

Last Edited: Mon. Jul 3, 2006 - 10:54 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

js wrote:
Quote:
I can in fact program the Mega64 and Mega128 with the Dragon

The M64 in NOT supported (in theory) for programming YET, just the M128, but as they should be very similar you have got away with it, infact there is no device selection for the M64 in the dropdown menu.

I'm still having problems with keeping the ISP frequency at 250KHz, it will revert to 8MHz. It will work for the session but once I leave the programmer interface and restart it it will go back to 8MHz. This is my version of Studio

AVR Studio		4.12.488  Service Pack 3
GUI Version		4, 12, 0, 488



Operating System
Major			5
Minor			1
PlatformID		2
Build			2600
Service Pack 2

Plugins:

AvrPluginAvrAsmObject	1, 0, 0, 43
AvrPluginavrgccplugin	1, 0, 0, 6
Stk500Dll			1, 0, 0, 60

The M128 programs ok in ISP mode otherwise.

Funny, I can get the Dragon to program the Mega128 with JTAG, but not with ISP.

Here's my vitals on AVRStudio...

AVR Studio		4.12.485  Service Pack 3
GUI Version		4, 12, 0, 484

ATmega32		227

Operating System
Major			5
Minor			1
PlatformID		2
Build			2600
Service Pack 2

Plugins:

AvrPluginAvrAsmObject	1, 0, 0, 43
AvrPluginavrgccplugin	1, 0, 0, 6
Stk500Dll			1, 0, 0, 60

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Build 488 is the one I have.

Quote:
Mega128 with JTAG, but not with ISP.

Check the ISP frequency it is probably 8MHz, see above posts.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

Last Edited: Mon. Jul 3, 2006 - 10:57 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John,
I'll download the new version and see if I can duplicate your problem...

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
So, bluegoo,

Are you are saying all of the below!!!:

1. you do have a Dragon.
2. Yyou are programming the target with the Dtagon.
3. You do not have to pull the JTAG cable off of the target once programming is complete to get the program to automatically run the target application.

Yes......

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John,

Here is the updated AVRStudio and SP3 stats...

AVR Studio		4.12.488  Service Pack 3
GUI Version		4, 12, 0, 488



Operating System
Major			5
Minor			1
PlatformID		2
Build			2600
Service Pack 2

Plugins:

AvrPluginAvrAsmObject	1, 0, 0, 43
AvrPluginavrgccplugin	1, 0, 0, 6
Stk500Dll			1, 0, 0, 60

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well,

Item #1. The Dragon won't release the target to run after it's done programming in TJAG.
Item #2. No matter what I do, I can't get the Dragon to read the chip ID.
Item #3. My ATAVRISP is now usless as, I can't even communicate with it at all now. It worked perfectly imediately befor I started mess ing with the Dragon. I know this because I have been programming with it all day.

So, I've got my work cut out for me, I can see that!

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

#2 I don't have any problems once I get the ISP frequency down but it tends to got up to 8 MHz, perhaps this is messing up the AVRISP too?

No such thing as a free lunch?? :-)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Microcarl ..is your target a STK500 with a STK501 on it and a mega128 or mega64? may not matter but all my testing for the last couple of days has been using one of my projects target hardware and my AVRISP continues to work fine with the Dragon etc. Have not tried it using an STK500 as that is set up just as a HV programmer when avr's go south.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Item #3. My ATAVRISP is now usless as, I can't even communicate with it at all now. It worked perfectly imediately befor I started mess ing with the Dragon. I know this because I have been programming with it all day

Does AVRStudio find it at all or is the problem somthing with programming the AVR?


My AVR Site

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

LCD*AVR4me wrote:
Quote:
Item #3. My ATAVRISP is now usless as, I can't even communicate with it at all now. It worked perfectly imediately befor I started mess ing with the Dragon. I know this because I have been programming with it all day

Does AVRStudio find it at all or is the problem somthing with programming the AVR?

I see the STK500. I can set Vtarget and the ISP frequency. I can't get the chip ID or anything esle. The only thing I can do is program the STK500 with JTAG. The application is running just fine, as long as I don't have the Dragon connected to JTAG.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

js wrote:
#2 I don't have any problems once I get the ISP frequency down but it tends to got up to 8 MHz, perhaps this is messing up the AVRISP too?

No such thing as a free lunch?? :-)

Actually John, I run fine at 8.000MHz.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

bluegoo wrote:
Microcarl ..is your target a STK500 with a STK501 on it and a mega128 or mega64? may not matter but all my testing for the last couple of days has been using one of my projects target hardware and my AVRISP continues to work fine with the Dragon etc. Have not tried it using an STK500 as that is set up just as a HV programmer when avr's go south.

I had a Mega128 in it for the initial firing but, I put the Mega64 back in.

I'll humor us all, and put the Mega128 back in.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Nop! I put the Mega128 back in to the STK500. It runs the application fine. I can write and read Vtarget and Vref. But I can not check the chip ID or any fuses. All I get is the window, telling me to check the ISP frequency. I've got them as low as they go.

One thing I did do... I re-connected the Dragon and disabled the JTAG enabled fuse. Now I can re-start my application by hitting RESET on the STK500 with the Dragon connected, where as, RESET did not work with the Dragon connected and the JTAG fuse enabled.

But I still don't have the ISP function on the STK500 - no matter what I do.

As I was asked it I wanted to upgrade the STK500 when I put the same version of AVRStdio that JS has, I'm thinking I'm probably going to have to back-draft the STK500 firmware.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

Last Edited: Tue. Jul 4, 2006 - 12:59 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

microcarl wrote:
LCD*AVR4me wrote:
Quote:
Item #3. My ATAVRISP is now usless as, I can't even communicate with it at all now. It worked perfectly imediately befor I started mess ing with the Dragon. I know this because I have been programming with it all day

Does AVRStudio find it at all or is the problem somthing with programming the AVR?

I see the STK500. I can set Vtarget and the ISP frequency. I can't get the chip ID or anything esle. The only thing I can do is program the STK500 with JTAG. The application is running just fine, as long as I don't have the Dragon connected to JTAG.

Try to make sure it (STK500) is not set for high voltage programming on the front tab. I had once set the STK for HV and forgot to change it and I was trying to read the Chip ID(using ISP on the STK).....wondering why it wouldn't work.

If you continue to have problems try to re-flash the STK500 using the Upgrade program in the STK500 folder.


My AVR Site

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I run fine at 8.000MHz......All I get is the window, telling me to check the ISP frequency

It can only be 1/4 pf the clock frequency for ISP, so you must be running the M128 at 32 MHz if it works :) ?
So there seems to be a problem with keeping the ISP frequency either by Studio or the Dragon as I have experienced. Carl do you WRITE the ISP frequency to the Dragon once you select it? 250KHz should work for most chips.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

LCD*AVR4me wrote:
microcarl wrote:
LCD*AVR4me wrote:
Quote:
Item #3. My ATAVRISP is now usless as, I can't even communicate with it at all now. It worked perfectly imediately befor I started mess ing with the Dragon. I know this because I have been programming with it all day

Does AVRStudio find it at all or is the problem somthing with programming the AVR?

I see the STK500. I can set Vtarget and the ISP frequency. I can't get the chip ID or anything esle. The only thing I can do is program the STK500 with JTAG. The application is running just fine, as long as I don't have the Dragon connected to JTAG.

Try to make sure it (STK500) is not set for high voltage programming on the front tab. I had once set the STK for HV and forgot to change it and I was trying to read the Chip ID(using ISP on the STK).....wondering why it wouldn't work.

If you continue to have problems try to re-flash the STK500 using the Upgrade program in the STK500 folder.

LCD,

Yeo! Been there, done that!

I'm just dead as a door nail.

I suppose I could get out the other STK500 and see if it works but, then I'd really be dead if it screwed up too.

I think I'm going to pull the STK501 off of the STK500 and stick a Mega 16 in the thing and see if I can get it to work stand-alone.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Mabe you accidently disabled ISP when you were JTAG programming? The only two ways that can happen is HV or JTAG programming.


My AVR Site

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ok JS,

I realised that I received a couple of Mega88's a couple of months ago, so I removed the STK501 and plugged it into socked SCKT3200A2. That would be the Green IC socked.

Now i get the revirsion back to 8.00MHz after I set the ISP frequency to 1.000MHz.

Also, I seem to have totally lost the ISP capability on my STK500 as, I can't get it to work either. The only thing I've gotten to work is the JTAG programming for the Mega64 & Mega128.

So it looks like the Dragon breath has spued the eval fire and devoured my STK500.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

LCD*AVR4me wrote:
Mabe you accidently disabled ISP when you were JTAG programming? The only two ways that can happen is HV or JTAG programming.

LCD,

I can't even get to where I recognize a microcontroller so, at this point fuses don't come into play because, I'm using new devices that are running on the internal oscilator.

I've scrapped at least two chips now and possibly three - not to mention destroying an otherwise perfectly running STK500.

And the joy turns to sadness!!!

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I know this will sound stupid but.... are you selecting "connect" or "auto connect" from the program avr tab? If you use auto connect it will go back to the Dragon rather than let you select the programming tool (STK500)...I know I know...but just in case :-)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You guys are scaring me here..
Now I'm afraid to upgrade and hook up the dragon.
(bites nails)

If my STK500 goes braindead I'm doomed!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Can you even ISP the AVR using the Dragon? I don't see how its possible to screw up an STK500 just by using another ISP programmer. Look over all the jumper selections. Look at the current AVRStudio (STK500) settings. Basicly re-look everything. I also had a very similar problem a day after I used my stk500 the first time....but re-flashing fixed it up.


My AVR Site

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Just tried my STK500. Looks OK I can read the signature on a 90s8515.

Quote:
the Dragon breath has spued the eval fire

Ealry 4th July fireworks ?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

correct me if I am wrong..bit did not Johan test a Dragon to ISP a Mega88 in the STK500 with no issues? If that was the case and MicroCarl is running the same setup but experiencing a different result would it not be good for them to compare notes and see where the issue might be? :)
I ordered some other megas today and they will get here Friday so I will expand my testing then if it helps.
I think as the others who received these gifts will come online soon as they get their Dragons, that hopefully between all of us we can cover most if not all the chips that are supported.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

microcarl wrote:
Item #1. The Dragon won't release the target to run after it's done programming in TJAG.

This is normal, assuming you are not programming via the "Program AVR..." option (instead programming by opening the .ELF file). AVRStudio will keep the AVR in reset in anticipation of you starting it (via Debug->Start Program) but you can release the programmer by yanking the cable. If you program via the "Program AVR..." interface (not sure about the Dragon yet but you can open the programming window on a JTAG unit and program an AVR via the JTAG interface) then the programmer will automatically release the /RESET line.

Microcarl, so this is the situation so far (please correct where appropriate):

1) You can program AVRs via the JTAG interface on the Dragon.
2) You cannot program AVRs via the ISP interface on the Dragon, the Dragon is resetting it's SPI speed parameter on startup.
3) You can no longer program AVRs on your STK500 after attaching the Dragon.

I had a serious problem with my old STK500. It literally died mid-programming of a Butterfly, and would then act perfectly normal until I tried any ISP program/verify operations where it would hang. When you try to ISP program on the STK500, does the status light stay on yellow? In my case repairing or downgrading the firmware didn't help, but miraculously shipping it to Germany so another user could have (and perhaps fix) it apparently repaired it :S.

The Dragon doesn't supply a target voltage on the VTARGET pin, does it? We need schematics!

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Dragon doesn't supply a target voltage on the VTARGET pin, does it?

No it doesn't. Are you chasing DHL before they ship your Dragon back to Norway? Ring them perhaps.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

js wrote:
No it doesn't.

Good, because it shouldn't. Just covering possibilities.

js wrote:
Are you chasing DHL before they ship your Dragon back to Norway? Ring them perhaps.

No need, it' re-sheduled for delivery. This happened last time; DHL seems to think my street is located elsewhere, and sends the package to the wrong distribution centre. They then send it back to the main one and get it right the second time.

Can't say I hold much love for DHL.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hey, Nick!

Where did you get those connectors (at the "single ends" of the squid)?

I've seen those with as few as 2 lines, but those look like single connectors.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Being doing a bit more Dragonning with a Tiny2313 and DW. Don't know if the following is a bug or not. I can't seem to program the DWEN bit by using the Dragon in ISP mode, it gives the warning about setting the bit but it doesn't stick. By going into debug mode it ask to set the DWEN bit in ISP mode which works and the DW operation is successful. Disabling DWEN from within debugWIRE works too.
Well I think I have had enough for the day, my 12 hours are up :( Microcarl seems to have gone into sleep mode and even though it is about time to wake up I suspect he'll be executing a lot of NOPs due to the holiday.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JohanEkdahl wrote:
Hey, Nick!

Where did you get those connectors (at the "single ends" of the squid)?

I've seen those with as few as 2 lines, but those look like single connectors.


I often will just use a single crimp pin and then put heatshrink over that. I actually prefer that over using 1x1 crimp housings. But, if you insist, you can get them here:

http://hansenhobbies.com/product...

I'm sure they're available many other places, but I know the owner of the above store and I have used many of his connectors, so I can reccomend both the store and the part.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ok! The good news is, I'm up and rinning!!!

First, be aware that I am using an STK500/501 combination when dealing with the Mega64 and Mega128, and the Dragon or STK500 and ISP when dealing with the Mega88's.

When I first connected the Dragon, I was able to connect and program a Mega64 using JTAG, but not Dragon ISP but, I think I had the enable serial downloads fuse disabled.

In an attempt to duplicate the problem JS was having, I downloaded the current AVRStudio and SP3 off of the Atmel web-site.

After removal of the existing AVRStudio, build 485 and, the installation of the AVRStudio and SP3, build 488, upon connection I was asked to upgrade the firmware in the Dragon - and I did. Connecting to the Dragon was never an issue but, I was unable to read the chip ID - any chip ID, using JTAG or ISP.

I then decided to move over to the STK500 ISP. I was then asked to upgrade the firmware in the STK500, and I did. But I was not able to read any chip ID's with it either. Whereas: the STK500 has been working flawlessly for months. Yet, I was unable to read any chip ID. I had been usint the STK500 all day so, I knew it was working.

After many hours of beating my head on the bench and, 1 Mega64, 1 Maga128 and 2 Mega88's killed in action, I decided to go back to build 485.

I un-installed AVRStudio build 488 and installed the version of AVRStdio and SP3 build 485 which I was using before attempting to help JS.

After the re-installation of AVRStudio and PS3, build 485, upon connectiong to the Dragon I was asked if I wanted to down-rev the Dragon firmware - and I did. At that point I was able to read the chip ID and program a new Mega64 using ISP. I then enabled the JTAG fuse and I was able to program the new Mega64 using JTAG.

I then moved over to the STK500 ISP and, I was again asked to down-re the STK500 firmware - and I did. I was then able to read the chip ID and program the new Mega64 using the STK500 ISP.

The version of AVRStudio and SP3 that I used to help JS were direct downloads from Atmel's web-site. The version that I was originally using, I downloaded from Atmel's web-sire on 06/30/2006.

The versions of AVRStudio and SP3 that I downloaded on 06/30/2006 were:
aStudio4b460.exe version 10.1.0.238
AVRStudio412SP3_beta_b485.exe version 10.1.0.238

Now some notes...

As I have stated, this is my first experience with JTAG of any kind so, my ignorance has much to play in my loss of control with the operation of the Dragon.

One big mistake that I think that I made is that I inadvertently turned off the JTAG fuse simultainious to turning off the serial download fuse.

Duh! I guess it would make sense that if you turn off all of the available methods of communications with the chip, you can't communicate with the chip. The thing is, I can't say whether I was in that situation before of after I started helping JS. I suspect the latter because, I was programming my target while attempting to help JS.

While I apear to have everything in good working order, I do not like the fact that I have to physically remove the JTAG cable friom the target device before the target application can run. I can't see this as being normal. So, I probably won't be too inclined to use the Dragon until I purchase a few Mega's that fall under it's support as, there is no additional support gained by it's use until then. I'll just keep using the STK500 ISP. Now, my next project will more then likely ba a Mega32 and I will incorporate the JTAG interface for use be the Mighty Dragon.

This learning opportunity was at the expense of 1 Mega64, 1 Mega128, 2 Mega88's

Interestingly, one Mega88 was DOA out of the box. The other Mega88 will allow the Dragon and STK500 ISP to read the chip ID and read and change the fuses. But none of the three programming channels will complete the programming cycle without a data corruption error message.

So, I hope this puts to rest some fears and provides a bit of insite to a few issues that can trap a new-be to JTAG.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

microcarl wrote:
...I do not like the fact that I have to physically remove the JTAG cable from the target device before the target application can run.

You might have missed my post earlier in the thread (posted yesterday).

If you program the target using the JTAG interface from the Program AVR... dialogue, then it should start the program automatically. If the JTAG interface loads the program in preparation for debugging inside AVRStudio it will pause the program until you either remove the cable (ending debugging) or chose "Start Program" from the appropriate AVRStudio menu.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

abcminiuser wrote:

Quote:
If the JTAG interface loads the program in preparation for debugging inside AVRStudio it will pause the program until you either remove the cable (ending debugging) or chose "Start Program" from the appropriate AVRStudio menu.

Dean,

I am not trying to load the AVR during a debug session. I have no AVR's on hand that the Dragon will support. I am trying to program the AVR from an object file, just as I would using ISP.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

I am not trying to load the AVR during a debug session.

Enter another noob when it comes to dW/JTAG:

I suspect that while the dW/JTAG connection to the AVR it is "by design" that the AVR will only run controlled by the debugging session in Studio. In a way that makes sense - If you only wanted to program the thing and then let it run free from the debugging system you would not need dW/JTAG but could go straight for "standard ISP".

Also: If the AVR sees a dW/JTAG debugging system connected to it there would have to be some sort of control that could tell it if to run free or be under control of the dbugging system. IT might be that Studio in reality does this descicion - ie. always under control of the debugging system.

For me the big drawback (if I have understood things correctly) is that I cannot disable debugWire through ISP programming. So when I want to switch from dW to ISP I must first set up HV programming to disable dW (and check that ISP is enabled), and then rewire again for ISP. Going the other way (enabling the dW through ISP) does not display this akwardness.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I want to switch from dW to ISP I must first set up HV programming to disable dW

Not necessary, it can be done from inside debugWIRE when you have finished your debugging. Just go to debug>Dragon options (I think) and then click on disable debugWire. Of course you will need all 6 wires connected as if it were ISP programming. The disable DW option is only visible whilst you are in DW debug mode otherwise it doesn't come up.

By the way my target is an older board for the 90s2313 and it has an external BOD chip and a 4K7 pullup on the reset pin (I have removed the cap) and it still works well.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JohanEkdahl wrote:

Quote:
If you only wanted to program the thing and then let it run free from the debugging system you would not need dW/JTAG but could go straight for "standard ISP".

Ah! But the JTAG interface programs so much faster compared to ISP. I guess it's all some sort of trade-off, isn't it.

But I'm still a bit unsettled as to why I couldn't run anything, Dragon or STK500, with the most current SP3, build 488...

Obviously, I'm not totally incompetent as, I was eventually able to recover but, I made several attempts, going back and forth between AVRStudion versions. Each time I updated to the most current version of SP3, I ended up with the same reaults, a non-functional Dragon and STK500. I just decided that I will wait until the folks at Atmel get all of the bugs out before upgrading again.

Also, I'm trying to con the little woman out of some money so I can but a few of each Mega in the current Dragon support list. I need to have a better variety of devices anyway.

I am looking forward to my next project so I can use JTAG for debugging. Maybe I won't have to spend days figuring out the obvious mistake of something like using && instead of just &. Of course, I could always get new glasses!

Thanks for your input Dean and Johan.

And JS, I'm sorry that I was unable to help with your problem, but the whole thing here, just fell apart.

And I wonder why the other Dragon recipients are so quiet! What have your experiences been with the Dragon? Don't let me and Johan be the only one who reveals their lack of knowledge about JTAG.

Good or bad, tell us so we don't have to make the same mistakes...

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

Last Edited: Tue. Jul 4, 2006 - 11:01 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

Ah! But the JTAG interface programs so much faster compared to ISP.

Carl, Carl, Carl... Impatience is for the young and restless. Ya'know, Dean, Gwen... We, who think one of our advantages is experience should use the time it takes to download the firmware to do take a quick look over the system, think ahead and be in control. Go for another cup of coffe. Or just take a nap...

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JohanEkdahl wrote:
Quote:

Ah! But the JTAG interface programs so much faster compared to ISP.

Carl, Carl, Carl... Impatience is for the young and restless. Ya'know, Dean, Gwen... We, who think one of our advantages is experience should use the time it takes to download the firmware to do take a quick look over the system, think ahead and be in control. Go for another cup of coffe. Or just take a nap...

Johan, I'll buy into the coffe and nap!

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I do not like the fact that I have to physically remove the JTAG cable friom the target device before the target application can run.

I have just upgraded my JTAGICE and programmed a M128 with it. In JTAG program mode the chip IS RELEASED as soon as it finishes programming it, so it looks like another small bug in the Dragon not releasing the chip as both of us have confirmed.

I guess we should find out from Atmel if our rambling on this thread or others are good enough for problem reporting or we should submit a proper bug report. What saith the DEV team? (I hope it's the DEVelopers team and not the DEVil's team :lol: )

So all in all the Dragon seems fairly usable and one should not be afraid of using it or upgrading Studio, even though Carl seems to be having a few "issues". I must admit I click on "upgrade" with trepidation since my AVRISP got crippled (and still is) following a S4.12 upgrade that went wrong and Atmel doesn't want to give me the code for the 1200 which I accidendatly erased during an attempted manual update :( ...but that's another thread...

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

is wrote:

Quote:
So all in all the Dragon seems fairly usable and one should not be afraid of using it or upgrading Studio, even though Carl seems to be having a few "issues".

Actually JS, my troubles seem to be behind me, for now. As my Dragon seems to be perfectly functional, plus or minus a few minor bugs, I plan on keeping the version of SP3 that works for me in a safe place on the network. When the folks at Atmel make the bug corrections, I'll give it a try, knowing that I can always go back to a working state at any time.

Thanks for the confirmation on the program release issue.

Has anyone given any thoughts as to a suitable case? I would like to eventually buy say, three Dragons. The idea is that each Dragon has it's own dedicated case. One would strictly be dedicated to JTAG, one to ISP and Debug-Wire and, the third would be dedicated to High-Voltage programming.

As I have stated several times, I rarely ever proto-type using proto-bouards. In fact, I rarely even used the STK500 in design work. The STK500 is dedicated mostly to those times when I'm helping other AVRFreaks work out code issues. So, as I don't plan on actually using the Draagon breadboard area, dedicating a case to the Dragon and sealing off the proto-type area isn. really of concern to me.

I have thought a bit about making a series of adapters such that, I would plug the adapter into the Dragon proto area. The adapter would house the target AVR and, a cable would be attached to the adapter that could be used as an imbillical cord to the target proto-type board. I'm not sure yet as, I haven't seen the Dragon schematics but, wouldn't that qualify as a full blown enulator?

It's just a though!

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Reading through the setup prociedure for the Dragon:

1. Follow these simple steps to get started using the AVR Dragon:
2. Download AVR Studio 4.12 SP3 or later from http://www.atmel.com/avrdragon
3. Install AVR Studio and the USB driver 
4. Connect AVR Dragon to the computer, and auto-install new hardware (AVR Dragon) on the computer
5. Start AVR Studio and the AVR Dragon Programming Dialog 
6. Connect AVR Dragon to the target

I assume that live connects/disconnects of the Dragon to the target board is acceptible, which, was my concern about the program release issue.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Has anyone given any thoughts as to a suitable case? I would like to eventually buy say, three Dragons. The idea is that each Dragon has it's own dedicated case. One would strictly be dedicated to JTAG, one to ISP and Debug-Wire and, the third would be dedicated to High-Voltage programming.

Where There Be Dragons There Be Dragon Caves............ :wink:

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

bluegoo wrote:
Quote:
Has anyone given any thoughts as to a suitable case? I would like to eventually buy say, three Dragons. The idea is that each Dragon has it's own dedicated case. One would strictly be dedicated to JTAG, one to ISP and Debug-Wire and, the third would be dedicated to High-Voltage programming.

Where There Be Dragons There Be Dragon Caves............ :wink:

Dark, damp and, dingy!!!

I wonder if one of svofski's Dark Boxes will work?

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Dark, damp and, dingy!!!

My Dragon is thinking Clear Blue or Red Anodized....Bluegoo Dragon Skin! 8)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Carl..

Put it into one of those transparent project cases.

That way you can still admire it...and also still see the LED :)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Gwen wrote:
Carl..

Put it into one of those transparent project cases.

That way you can still admire it...and also still see the LED :)


I might. There is something nostalgic about seeing all of the circuitry and LED's flickering.

The more I think about it, the more I'm thinking I can turn the Dragon into an emulator. I think that will ultimately dictate the case size.

We'll see how big the adapter board turns out to be.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

microcarl wrote:
And I wonder why the other Dragon recipients are so quiet! What have your experiences been with the Dragon? Don't let me and Johan be the only one who reveals their lack of knowledge about JTAG.

Good or bad, tell us so we don't have to make the same mistakes...

Simple reason; I'm still waiting. My Dragon's been "scheduled for delivery" three or so times, each time being sent back to the main distribution center without any explanation. DHL is now officially on my s**t list!

JTAG comments seems to make sense. I can't remember if the Program AVR window usually freezes my AVRs after programming - when programming with my JTAG I usually yank the cable anyway since if I needed it to remain connected I would be using it as a debug platform.

Bluegoo's had me intrigued by his "Dragon Cave" hints via PM for a few days, hence my tempoary signature change. I'm eagerly awaiting the photos and explanation he's promised :).

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I might. There is something nostalgic about seeing all of the circuitry and LED's flickering.

My old PC..the one in the garage, has a clear case..it's really cool!

I saw some small clear project cases for sale....I will try and remember where.
I think they were just about right for the dragon and were 4$

Quote:
I wonder why the other Dragon recipients are so quiet!

After all your troubles I'm too scared to hook it up!
I need that Dragons For Dummies book!!!!!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Gwen wrote:
Quote:
I might. There is something nostalgic about seeing all of the circuitry and LED's flickering.

My old PC..the one in the garage, has a clear case..it's really cool!

I saw some small clear project cases for sale....I will try and remember where.
I think they were just about right for the dragon and were 4$

Thanks Gwen.

Quote:
I wonder why the other Dragon recipients are so quiet!

After all your troubles I'm too scared to hook it up!
I need that Dragons For Dummies book!!!!!

Don't be! I think there are enough folks around here that can help you get it going. Besides, I think the major part of my problem was because of my own ignorance about JTAG and FUSE setting.

But you know all that now because of my silly mistake and then telling you about it, right?

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have noticed that on the back side of the Dragon PCB there are some holeless pads. It ocurs to me that Atmel has made a fixture to hold the board and do the programming and testing without ever attaching a cable to it.

This presents some ideas for programing future project boards of my own.

I have these little Gold plated spring loaded pins that I ordered from Digi-Key by mistake. These little pins would work perfectly for this purpose.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

IT'S HERE!!!!!! IT'S HERE!!!!!!

I got home to find it on my bed. Seems DHL decided to send it via a courier from the main distribution centre rather than via the normal process.

Just plugged it in, it's awesome!

- Dean :twisted:

EDIT: Damnit, I don't have any of the supported AVRs. And before I get any more AVRs I need a project idea to go along with it :?.

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

Last Edited: Wed. Jul 5, 2006 - 05:42 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Carl, glad you fixed everything. :D

Quote:

Just plugged it in, it's awesome!

It's Atmel, isn't it ;)

Still trying to decide weather I should buy a AT90USBKey or a Dragon (when its available) or both 8)


My AVR Site

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
my AVRISP got crippled

WELL whaddyaknow SP3 fixed my crippled AVRISP!!! I noticed what seemed a new STK500 upgrader file so just for fun I tried to upgrade my AVRISP and it WORKED! even though it did not verify which could be understandable seeing that my 1200 code is a hack of a hack seeing that no one seems to be able to supply me with a good 1200 code for the AVRISP with a Mega8535 in it. I'm happy with V2.07 code in the AVRISP :)
Better post this on the original thread also in case someone else has this problem.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I have noticed that on the back side of the Dragon PCB there are some holeless pads

I just looked and I see them too :)

I think that headers seem easier to work with though....
Little springs would be flakey I think....

If you mount this in a case you could just snip the end off a usb cable
and then pass it through a hole in the case and solder onto the 4 pins on the dragon
where they come out the back of its USB connector thingie...they look big enough
to solder to.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Damnit, I don't have any of the supported AVRs

Get atmega168's they are my favorite :)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
don't have any of the supported AVRs.

You can get ATMEGA32-16PI on line from Dontronics in Tullamarine. They are usually quite good and could be there next day. DON'T ORDER from Futurelec they delivery is useless, I have been waiting for a USB module from them for over a month, they took the money but no cigar, don't even answer my emails. :(

ps just checked Farnell's website and they have Tiny2313 in stock and the M32 also so you have a choice.

pps ...and the Meag168 too. They will deliver tomorrow if you place an order now....unless they send them by DHL that is :lol:

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Getting a Dragon compatible AVR isn't an issue (I need to stop by Altronics soon anyway for a new iPod battery), it's choosing the one(s) I want. Dan and I have been trying to think of a new and interesting open source project I could work on, but I haven't found one I like yet. I want it to be unique, not require ordering specialist parts from Tajikistan or $100 parts. I want it to be useful to the community and be of a reasonable complexity (not too simple, not impossible). I'm a hard man to please initially but when I get going with a project I usually don't stop :).

While I'm waiting I upgraded my Dragon's firmware, which went very smoothly. I consider being able to see the new M2560 a bonus! It's a real pity there's no schematics for the entire Dragon.

I wonder why it needs external SRAM (Samsung chip)? It must be for shared information between the M2560 and the M128, as I can't think of any other reason to need it...

- Dean :twisted:

PS: I think PMs with project ideas if any would be best, I don't want to be responsible for derailing yet another thread :roll:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
wonder why it needs external SRAM (Samsung chip)? It must be for shared information between the M2560 and the M128, as I can't think of any other reason to need it...

my guess...user hex program download memory buffer and/or emulation memory...I do not have one but if you have a JTAGII break it open and see if there is a big sram in it especiallly for Debug Wire.....I wonder how close the chip comparison between a Dragon and a JTAGII is?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

bluegoo wrote:
Quote:
wonder why it needs external SRAM (Samsung chip)? It must be for shared information between the M2560 and the M128, as I can't think of any other reason to need it...

my guess...user hex program download memory buffer and/or emulation memory...I do not have one but if you have a JTAGII break it open and see if there is a big sram in it especiallly for Debug Wire.....I wonder how close the chip comparison between a Dragon and a JTAGII is?

I'd say you're spot on the money, Blue. I grabbed a screwdriver and gave the AVR gods yet another reason to hate me :).

My poor little digital doesn't lend itself to closeups, so I'm afraid I can't provide high-res shorts of the JTAG internals. If anyone really wants to see what's in it, I can borrow my mum's super-mega-ultra-fantastic Sony and give it my best shot.

Inside the MKII is (suprisingly) two M128s, different to the Dragon's single M128 and M2560. This is possibly due to the JTAG-MKII being designed before the latter chip was in production.

Also in the MKII is a Samsung SRAM chip, with a different part number to the Dragon (K6R4008CIO-3C10). I'd suspect this is a larger SRAM chip which might suggest why the Dragon's limited in JTAGing abilities.

- Dean :twisted:

Attachment(s): 

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks for the posting the pictures Dean...with your info it appears the Samsung Sram in the JtagII is a 4 MBIT device and the Samsung Sram in the Dragon is a 1 MBIT device...so considering they both have similar micros (except the Dragon has the newer 2560) my guess is that with the exception of available sram and firmware , inside the Dragon beats the heart of a JTAGICE 3 !!!!!! :twisted:

Are you still looking for a good project for your new Dragon ?
......hardware provided/ firmware is the challenge ! :roll:

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Interesting that once you eliminate the RS232 interface components, the case, the flat ribbon cable, and the switch in the JtagIceII....the component cost is probably very close to the Dragon..especially considering the two most expensive chips in the design Atmel makes!!!!
....last time I checked I believe a 4mbit sram drops in a 1 mbit pinout (32 pin landing but I could be wrong) if the additional address lines are wired up! Since the AVR only supports 64k external sram they have to page address the additional memory anyway.
I am still thinking Dragon is really a JtagIce 3 in disguise/waiting to happen!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

looking very closely at your pictures it looks like possibly they brought the jtag header 2x5 and ISP header 2x3 for each mega128 over to the side of the pcb! Maybe Production pcb design was previously a prototype design too!
pcb has something similar on the Dragon...I am guessing they can jtag/test/isp (2x5 pads) both the micros from the underside of the pcb on a "bed of nails".

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

microcarl wrote:
After removal of the existing AVRStudio, build 485 and, the installation of the AVRStudio and SP3, build 488...
...I then decided to move over to the STK500 ISP. I was then asked to upgrade the firmware in the STK500, and I did. But I was not able to read any chip ID's with it either. Whereas: the STK500 has been working flawlessly for months. Yet, I was unable to read any chip ID. I had been usint the STK500 all day so, I knew it was working.

When I upgraded AVR Studio to build 488, I have not seen any suggestions to upgrade STK500 firmware.
Build 488 simply connected to STK500 as before:

Detecting on 'COM1'...
STK500 with V2 firmware found on COM1
Getting revisions.. HW: 0x02, SW Major: 0x02, SW Minor: 0x07 .. OK

All basic operations with Atmega32 Ok, too:

Setting mode and device parameters.. OK!
Entering programming mode.. OK!
Reading lockbits .. 0xFF .. OK!
Leaving programming mode.. OK!

Entering programming mode.. OK!
Reading fuses .. 0x9F, 0x3F .. OK!
Leaving programming mode.. OK!

Entering programming mode.. OK!
Reading signature .. 0x1E, 0x94, 0x03 .. OK!
Leaving programming mode.. OK!

Microcarl, sorry, but... haven't You forgotten this:

Quote:
Firmware Upgrade
In order to achieve successful firmware upgrade, make sure that all cables and devices are removed from the target area of the STK500.

?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Microcarl, sorry, but... haven't You forgotten this:
Quote:
Firmware Upgrade
In order to achieve successful firmware upgrade, make sure that all cables and devices are removed from the target area of the STK500.

?


No, I didn't forget that.

And I know that build 488 upgraded my STK500 because, when I went back to build 485, and connected the STK500, AVRStudio said that there was version x.07 and that AVRStudio, build 485 build required The STK500 to have build x.04. So how esle would I have gotten a higher version of the firmware in the STK500, except that AVRStudio upgrade my STK500. And I specifically remember AVRStudio, build 488 asking me to upgrade the STK500 because I always shutter when I have to do an firmware upgrade on anything.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I am still thinking Dragon is really a JtagIce 3 in disguise/waiting to happen!

OR a STK600 ?? Just remove the 8535 bits of the STK500 and replace it with the Dragon bits??

On another matter the fact that the DWEN bit is left on at the end of the session is a little disconcerting given that I spent about half an hour last night trying to ISP the tiny2313 which was used by the Dragon with my newly revived AVRISP. I thought it had died again untill the light came on and remebered to turn off DWEN :(

:idea: DEV team suggestion: have a check box in the Dragon options to bring up a "disable DWEN" yes/no box whenever either the project is closed or stop debugging. This may also apply to the JTAGICEMK2 I suppose.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Just checked my STK500's firmware and it is 2.07 so it must have been upgraded by SP3 I guess even though I don't remember doing so, perhaps I went into mental paralysis and a short coma when I was asked to upgrade and clicled ok :?
BUT I do remember the disaster with SP2 upgrade of my AVRISP :(

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JS, thanks for the confirmation that SP3 did at least change the STK500 firmware.

I bet that if you go back to SP2, it'll sure ask.

I have ocasionally upgraded the BOIS in a few of my notebooks. Each time I do, I am fearful that I will end up with nothing more then a pile of highly refined petroleum by-product and processed beach sand. I feel that way about all firmware upgrades.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
if you go back to SP2

Definetely NOT!! :lol: But I'm not having any of the problems you describe everything seems well. I hardly use the STK500, still waiting for the fatefull day I'll need HV programming, but I can read the the chip. One thing I have noticed though is that the VTG goes back to zero on upgrade and therefore nothing will work, did you check the VTG and the VREF with SP3? May be that's what happened to you.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

js wrote:

Quote:
One thing I have noticed though is that the VTG goes back to zero on upgrade and therefore nothing will work, did you check the VTG and the VREF with SP3? May be that's what happened to you.

No, I checked that and I haf 5.1 at Vtg and 5.0 at Vref.

I think it was more that when I was messing with the fuses, I in-advertently turned off the JTAG and serial programming fuses.

It's all good now, except for the RESET hang after programming using JTAG. In ISP programming, RESET is released and the target program runs.

Maybe Johan is right! I should just program using ISP and, enjoy the coffee. Or, maybe I'll just take a nap as, I usually only run on 4 to 5 hours of sleep each day.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm in business! A kind member here, Adam, has sent me a MEGA168 (Gwen's favourite ;)) sample and an awesome little TINY13 mounted on an adaptor board which are both Dragon compatible. I'm going to take them for a spin now.

Has anyone got a project idea to keep me occupied for a while?

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

abcminiuser wrote:

Has anyone got a project idea to keep me occupied for a while?

I wanted to build a SPI/ i2c trigger device but I've been too busy lately.. simply waits for certain data on the bus and then sets a trigger output to trigger a scope or logger or toaster. don't have any use for it but thought it'd be useful for debugging when you don't have a mixed signal scope/ logic analyzer/ spi triggered toaster.
be a nice tiny13 project. software uart to talk to PC, SPI or I2c implementations and a trigger output.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

NickLott wrote:
abcminiuser wrote:

Has anyone got a project idea to keep me occupied for a while?

I wanted to build a SPI/ i2c trigger device but I've been too busy lately.. simply waits for certain data on the bus and then sets a trigger output to trigger a scope or logger or toaster. don't have any use for it but thought it'd be useful for debugging when you don't have a mixed signal scope/ logic analyzer/ spi triggered toaster.
be a nice tiny13 project. software uart to talk to PC, SPI or I2c implementations and a trigger output.

That's brilliant, and seeing as my new TINY13 board has a LED on one of the pins, it's even more suitable. I don't have a scope however; could you describe the trigger mechanism? Is it low until trigger tripped, then high for a specific duration?

I could even write in a nano-sized interpreter so you could send it rules for triggering (eg, trigger on 0x02 sent if preceeded by a 0x21 for example)...

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

well you could just have a +ve or negative pulse, hell make it user definable. I left my scope 8000kms away but most scopes will trigger on either a rising or falling edge so a starting point might be vcc output normally and then a falling edge to gnd on trigger condidtion for 10 ms. or until cleared, etc.
even if you had it on a uart rather than spi would be cool . just flick a button to switch between PC setup mode and triggering mode.....

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
an awesome little TINY13

wow I forgot I have a AVR dice board with a tiny13 on it, see if I can suck out the code out of it :) and reassemble it just for fun. You may remember the AVR Dice drives 30 leds with the T13 using Chalieplexing.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I just checked the Tiny13's specs. At 1KB FLASH and no hardware SPI, I2C or UART, I think I'd have to waste the entire flash just making drivers. I think for such a project I'd have to go a slightly larger AVR with hardware to support it. IIRC, I have a 90S2313 sitting around here somewhere...

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I'd have to waste the entire flash just making drivers

Ahemmm not if you use assembler....

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'm with you, Dean, pick a part with HW support for I2C/SPI. Trying to do full speed I2C receiving in software could be difficult. Just a gut feeling, I haven't checked out the timings, but the last time I wrote any software implementations of I2C receive (on a PIC admittedly) it was only feasible because I was able to slow the master down to a snail's pace.

Four legs good, two legs bad, three legs stable.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

js wrote:
Quote:
I'd have to waste the entire flash just making drivers

Ahemmm not if you use assembler....

Or with some tricks, avr-gcc. With some luck, you could only waste most of the flash.

- John

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well no dice with the AVR Dice. The reset pin must be used as an IO pin in the Tiny13 so cannot enter program mode. Correct? Is the only way to recover the chip HV programming or does anyone know a way around it? Never used the Tiny13 before. Don't really want to erase the chip without it's code but I can't find even a mention of the Dice (apart from my posts) on Google or Atmel's site. No diagram or code, surely it isn't top secret!

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Dragon MOUNTING:
Can we have a consensus of opinions on the 3 pads which look like positions for mounting holes? 1 is located between pins 1 and 28 of the 28 pin socket (or 1 and 40 of the larger socket), 1 is located near the leds and one is located near the USB connector between the 2 inductors. I hope the board is not multilayer and I drill trough some tracks. I'll leave it till the morning I think. The board is so light that the USB cable drags it everywhere and I'm afraid it will short out on something and goodbye Dragon. I want to mount it in a plastic box with some ballast to keep it from going everywhere.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Removed, because the reply is outdated ...

Last Edited: Fri. Jul 7, 2006 - 03:24 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
plastic box with some ballast

I suggest the 60 Watts version should do the trick.

Ken

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You could store your defective PIC processors in the box, only for weight purpose :-)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

That little Tiny13 board was intended for driving a (heatsink mounted) FET, which in turn drove a 3 Watt Luxeon Star LED for a caving headlamp.. But it's a good little 'smart christmas light' or whatever too. :)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hey--my Dragon is "Scheduled for delivery".

So, once the dust settled should I make sure that I have build 485 or 488 of Studio/SP3? Or will both work?

Lee

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

theusch wrote:
Hey--my Dragon is "Scheduled for delivery".

So, once the dust settled should I make sure that I have build 485 or 488 of Studio/SP3? Or will both work?

Lee

Lee,

And for the record...

Even though my Dragon was up and running with SP3 build 485...

This morning, after a good night sleep, I re-installed SP3 build 488 on my machine. Upon connection to the Dragon, I was asked to upgrade - and I did.

Everything went as it was supposed to and the Dragon now works with SP3 build 488, as does my STK500.

I don't know what I did wrong to cause myself so much grief upon the initial installation of SP3 build 488. I guess it was a combination of being tired, overly eager, and stupid little mistakes of which, I can't really account for. What I do know is that, I spent about 6 hours doing the same things that I did this morning but, with radically different results..

So, all I can say is that I plead incomentence in the matter.

Edit:

As I did initially have a working Dragon before upgrading from SP3 build 485 to SP3 build 488 the very first time and, looking back on the whole event, I seem to remember a volley of questions with bluegoo about proper settings for the JTAG enable, Serial Download enable and, Debug enable fuse settings. I am thinking that what I actually did was lock myself out of the controllers that I was using while trying to get the thing working.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

js wrote:
Dragon MOUNTING:
Can we have a consensus of opinions on the 3 pads which look like positions for mounting holes? 1 is located between pins 1 and 28 of the 28 pin socket (or 1 and 40 of the larger socket), 1 is located near the leds and one is located near the USB connector between the 2 inductors. I hope the board is not multilayer and I drill trough some tracks. I'll leave it till the morning I think. The board is so light that the USB cable drags it everywhere and I'm afraid it will short out on something and goodbye Dragon. I want to mount it in a plastic box with some ballast to keep it from going everywhere.

Thinking Inside The Box! :shock:

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Maybe Atmel will make us a hard plastic case just like that?

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Am I mistaken or do you have a small mill/cnc MicroCarl?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

bluegoo wrote:
Am I mistaken or do you have a small mill/cnc MicroCarl?

Yes I do.

I use it mostly for drilling and routing PCB's, though, I have milled out a couple of simple panels and project boxes. Nothing complicated or to write home about.

Edit:

I currently have 11 Model No.131 plastic cases. The outside demensions are: 4.4"long by 3.2" wide by 1.5" deep.

As it happens, the Dragon will fit within this box with about a 32nd of an inch to spare.

Looks like I've got my case, though I'd perfer 1/2" hieght rather then 1.5" high.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

Last Edited: Thu. Jul 6, 2006 - 03:44 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

well if you have a carbide bit there is an equally simple solution but it does take more than 15 seconds and it will reward you with exactly what you requested for each of the Dragons you proposed using....I posted the solution that is within the reach of all who have an Xacto Knife

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
though I'd perfer 1/2" hieght rather then 1.5" high.
yes my enclosure is .400" thk. sort of like Dragon Skin :idea:

get to milling!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Can't right at the moment! I have to go earn some money to pay bills. But, I'll be thinking about this at work tonight!

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
The board is so light that the USB cable drags it everywhere

That is the exact reason I mount stuff like this to a piece of board :)

I am making up a nice board for the dragon...it will have a small pc board next to
the dragon with sockets to put avr chips into for programming...a variable pwr supply
will also be on the board.

This is just what I did for my tiny programmer I got from ere.co.th

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

The Dragon cardboard box in it's original state will be a collector's item in a hundred years or so and I intend to cash in then....
when I retire....

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

May I ask anybody who already owns Dragon to post it's dimensions here?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

4.1" (104.4mm) x 2.1" (53.1mm) +/- about 0.01" (0.02mm)

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

From the Dragon help file (link) on page 1 of this thread:

Quote:
AVR Dragon Requirements

System Unit

Physical Dimensions...................................... ( H x W x D ) 53 x 105 x 15 mm

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Where are you guys getting the dragon from? Did Atmel send them to you for beta testing? I want one of these now, I was just about to buy ICE-mkII the other day.

Man I am so happy that there is a low cost way to ICE lower end AVRs. I was going to jump to the Zilog encore platform because they seem to everything AVR does except their tools are so much cheaper. Now with the dragon, I can stick with the AVR.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

toalan wrote:
Where are you guys getting the dragon from? Did Atmel send them to you for beta testing? I want one of these now, I was just about to buy ICE-mkII the other day.

Man I am so happy that there is a low cost way to ICE lower end AVRs. I was going to jump to the Zilog encore platform because they seem to everything AVR does except their tools are so much cheaper. Now with the dragon, I can stick with the AVR.

You could say we're beta testers :). Atmel very kindly sent out a bunch of them to members who had responded to a few select threads here. Full production won't be until the end of the month at the earliest. and the service pack for AVRStudio for Dragon support is still in beta.

My experiences so far mirror a some of the responses here. I've jammed my new MEGA168 (thanks Adam!) into my STK500 and connected the dragon via ISP. The default ISP speed for the Dragon is 1MHz, which is also the default speed for the 168. Because of this, the dragon read back everything as 0x00 from the chip - fuses, lockbits, signature, the works. Once I lowered the speed to 125KHz it worked as expected. I am using the latest studio beta, build 488 SP3.

If the dragon programming window is closed on the "Board" tab and the dragon's power cycled, the next time the programming window opens the option to read the ISP speed will fail, as will writing any new speed. The ISP speed also ramps up back to 1MHz after a power cycle - the only way to reset the ISP speed is to choose another tab, go back to the board tab (the ISP speed will now read sucessfully at 1MHz) and then write the ISP speed as 125KHz again.

Should I send this to avrbeta@atmel.com, or are the Dragon Atmel people reading this thread?

EDIT: Sent them an email.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

Where are you guys getting the dragon from? Did Atmel send them to you for beta testing?

Atmel gave a few away to people who contributed to another thread where the Dragon was first discussed. If I understand things correctly the Dragon is already selling in China. "Western world" suppliers should begin stocking it at the end of July or so, according to Atmel.

You are aware that the Dragon is much more limited than the mkII when it comes to ICE? The Dragon will only do ICE (JTAG) on devices with less than 32K FLASH. So if you want to ICE on eg. a ATmega128 then the Dragon is not the thing.

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Fellow Dragon users.

I took the liberty to make a drawing of the proto-area of the Dragon. Also I was able to add the interconnects for ISP and JTAG in schematic form.

While this is currently only for the Mega32, now that the hard work is done, it wouldn't be to hard to provide this type of cheat sheet for all of the AVR devices supported by the Dragon.

Please review for any errors and let me know if you think a set of these drawings would be useful for the currently supported devices.

Please note, I did not have room for the High Voltage Programming setup.

Attachment(s): 

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You are showing vcc going to ground (pin 10 for isp programming) Also the chip will need to be fully powered (vcc + avcc + gnd + agnd) for JTAG use (programming and debugging) and ISP programming. Someone else will pick up something I have missed.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Carl!

Are you aware of the "cheat sheets" in the AVR Tools help? Take a look under AVR Dragon, Device Connection Sheets, ATmega32:

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I can't build myself a Dragon Cave for two reasons. One, I could never desecrate an Atmel box in such a manner, and two my box looks like it was sat upon during transport. Actual Dragon came out of it OK, but perhaps it was dizzy from the ordeal and that's why it was late in arriving 8).

I received a response from the beta team saying they would look into the problem I outlined to them and it will be fixed soon. Very prompt :).

Attached it a picture of my DragonSteak (Dragon + STK500 :D) I'm using to test the Dragon. It's currently programming a MEGA168 which I'm running Dan's servo code on, hence the servo.

- Dean :twisted:

Attachment(s): 

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JohanEkdahl wrote:
Carl!

Are you aware of the "cheat sheets" in the AVR Tools help? Take a look under AVR Dragon, Device Connection Sheets, ATmega32:

Johan,

Yes, I'm aware of the cheat-sheets. Thats what I used to create the schematic style interconnection on the left side of the drawing.

I did this because I wanted to understand what was being connected to what. I have diffucltly just connectiong junpers and not knowing what I'm actually connecting.

JS,

I'll look into your observations and correct those issues and update the attachment.

Dean,

I'm running my servo controller with a 4x20 LCD display. Currently, I am showing the command on one line and another line is displaying the current servo position that the servo controller has commanded. I cheat somewhat as, I use a "Serial Backpack" from Scott Edwards, See-Tron.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ok, Johan, JS, Dean, Bluegoo, and who ever else...

I think I have corrected the errors that JS has pointed out. Could you please review the following two documents for their accuracy and usefullness.

If you find these documents useful, I would be happy to make a set for all of the devices currently supported by the Dragon.

Thanks.

Attachment(s): 

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Looks fine to me, but why are you connecting up the ISP power/GND for high voltage programming? I was under the impression that was not necessary (but not detrimental).

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Dean,

If you are refering to pins 30 & 31 on the 40 pin header, I put them there because there is no mention in the Dragon about the remaining power pins being connected on the AVR device. I did this because as JS pointed out a few posts above that, I didn't make all of the required power connections to the AVR on the ISP and JTAG interface schematics. I assuemd that the HVP would require the same power connection requirements as the ISP and JTAG.

Now, Assuming that they are accurate, if these documents were set up to reflect the proper connections for ISP, JTAG & HVP for the flavor AVR that you prefer, are they what you would reach for or would you just refer to the abstract color coded connection map in the AVR Dragon manual.

I made these documents because the color coded map doesn't give me a clue as to what is connected to what and, because I like to kown how things work, as much as possible, the schematic form gives me a better understanding of the circuitry involved.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I'd probably go both. Your documents makes it a hell of a lot easier for users to install their own sockets and such while still being able to wire them up correctly. The Atmel documents are good for those who just want to get things done, your documents actually show what is being done.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

abcminiuser wrote:
I'd probably go both. Your documents makes it a hell of a lot easier for users to install their own sockets and such while still being able to wire them up correctly. The Atmel documents are good for those who just want to get things done, your documents actually show what is being done.

- Dean :twisted:

Then which do you think would be the most popular, the Maga88 or the ATtiny2313?

Also, on page 259 of the Mega32 (document 25031-AVR-04/06) data sheet, it shows both VCC and AVCC being connected to +5V.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Oh yes, both VCC and AVCC should be connected to +5V, no contensting that. I was talking about the connection to the ISP VCC header from the power header in the parallel programming method section (see attached screnshot). Why do you need to hook up the ISP header VCC for parallel programming?

As for the M88 vs the 2313, I really couldn't say. I think I hear more about the latter here rather than the former but it may just be that more people are having issues with the latter than with the former.

I'm off to try DebugWire for the first time. Wish me luck!

- Dean :twisted:

Attachment(s): 

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
it shows both VCC and AVCC being connected to +5V.

One thing I would like to mention is that for programming chips what you have done should work. If however one is debugging a project with either DW or JTAG at a voltage other than 5V supplied by the USB, let's say working with 2 x 1.5 V batteries (~3V), then the connection from the VTG pin of either the ISP/DW connector or the JTAG connector would just simply go the the chip's VCC and NOT to the EXT power connector. The VTG pin is used to power up the AVRISP or the JTAG ice in non USB tools but it is there only to measure the target's voltage in USB tools like the Dragon, or at least that is my understanding. It seems that the USB tools will measure the target's VCC and adjust it's own supply accordingly. But then I could be wrong :)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

abcminiuser wrote:
Oh yes, both VCC and AVCC should be connected to +5V, no contensting that. I was talking about the connection to the ISP VCC header from the power header in the parallel programming method section (see attached screnshot). Why do you need to hook up the ISP header VCC for parallel programming?

As for the M88 vs the 2313, I really couldn't say. I think I hear more about the latter here rather than the former but it may just be that more people are having issues with the latter than with the former.

I'm off to try DebugWire for the first time. Wish me luck!

- Dean :twisted:

Well Dean, unless I'm having a major Brain Fart The connection is shown in the color coded connection map for HV programming for the Mega32.

I have to work this weekend but, I'll try to get the ATtiny2313 drawings done sometime early next week.

I wish you luck with the DW experiments!!!

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Just had a pleasant Dragon experience: I was playing around with PWM, and had problems. Searching for an explanation and a solution, I ran the code under dW. Rather than changing the timer setup and compare values in the code and restarting (ie. re-programming FLASH) I just ran the app controlled by dW, paused and manipulated the timer control registers and then resumed the app. Good enough, I thought. But then...

In the "Dragon options" (reachable when debugging is active but paused) I found a check box "Run timers in stopped mode". I checked it, and a little piece of debugging heaven showed up: Without the app even running I could manipulate the timer control registers and the timer immediately reacted to the changes. There I was changing prescalers, timer modes, TOP values and compare values ad hoc. A trial and error work that I expected would take hours was done in minutes!

I love my Dragon! Thank you Atmel!

Aside: What I was doing? Trying to generate PWM to control a Futaba S3003 servo. What I found? 1 MHz precaled CLK/64 yields a PWM with f=61 Hz, and with this the servo reaches it's end points at 35% and 5% duty cycle. The latter was a surprize as several posts here (and other Internet resources) state that servos wants a duty cycle in the range of 5 to 10 %. The usual frequency referenced is 50 Hz. Could my deviation with 11 units explain this? Or could it be that I ran the whole shebang off the STK500 supply (the STK regulators didn't get that hot :shock: ). I also expected the servo to be faster. I estimated a full stroke (180 degrees) to take more than half a second.

@Carl: In an old post you have attached a servo manual. Alas, the attachement has gone into the great void (prolly in/sfter one of the forum server crashes). Could you post it again, please? There is a recent servo thread running. That might be a good spot: https://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&p=240355#240355

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Johan,

I have been involved in three motion related threads.

The first was quite a while back that involved PWM driving a DC servo motor in "Phase Anti-Lock" mode unind an LMD1802T full H-Bridge driver.

The second was more resently and involved my experimental single axis test bed, driven by a Bipolar 170 ounce/inch 1.8 degree stepper motor, dirive with a Gecko stepper motor controller.

The third and most resent discussion involved driving standard R/C servos with the LynxMotion SSC-32, 32 channel servo controller.

I suspect you are refering to the first discussion and I will try to find that manual and post it sometime today.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Man I chose the wrong week to take a week off!

I decided to have the Dragon shipped to my work address because I figured I'd have a better chance of being around to sign for it and all.

But I've been out of the office all week! I'll bet my Dragon is sitting down in receiving, patiently waiting for me to get my paws on it. It's driving me batty!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Johan ,
I need the animal, i need to tame my rampent code , which zoo is it hiding in , seems to be the best item out of the atmel stable this year ! , no doubt it will be a few months before it reaches Europe from the far East .if production and distribution goes according to plan

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Has anyone downloaded the newer SP3 (build 490)? Does it fix some of the Dragon's "issues"?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I've downloaded 490 but only in the hope that the Dragon "supported device" list might have expanded - but sadly it hasn't yet. I want JTAG for the Mega16 !!

Cliff

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

I want JTAG for the Mega16 !!

Me too!!

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

C'mon you people buy a Mega32 chip then simply move your code to the M16 :)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

buy a Mega32

Uh-huh? I've found no supplier of the m32 in Sweden, so I've put the m32 on my DigiKey shopping list...

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
no supplier of the m32 in Sweden

Doesn't Farnell keep them? (a bit expensive but..) They have them in stock in Australia, I'll be ordering 1 today plus a couple of M168 as I will be utilising them more for debugging M8 code.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JohanEkdahl wrote:
Quote:

I want JTAG for the Mega16 !!

Me too!!

Me three! Oh, and the M169 too :).

Did anyone else have issues with the Dragon when opening the programming screen if the selected tab was the board tab? On B488, reading/writing the Dragon's speed settings would fail until another tab was selected before returning to the board tab.

I submitted it as a bug and I've downloaded B490. I'll test to see if the problem has been corrected tonight.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

OK just ordered a couple of each of M48, M88, M168 and 1x M32 from Farnell. I will make a 2 wire debugWire lead (gnd+reset) because the board I sell most of (LED display) doesn't have an ISP connector because it was late at night when I finished the board (a couple of years ago) and could not be bothered waiting to do it the next day. So I'll hook up the DW on the pullup resistor for the reset and remove the cap to ground. I will need to turn on DWEN on another board first.
I will also need to change the project from the ICE200 to DW and remove all the equates and conditional statements I have as I was using the 90S8535 to emulate the Mega 8 on the ICE200. Fun fun fun :)

edit: DRATS not as simple as I first thought as the M8 and the M88 are not the same (int vectors,USART regs etc.), should have looked up the app note first :( not to worry a bit more conditional assembly for the time being until I run out of M8 stock. All new stuff will be done on M88.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

Last Edited: Thu. Jul 13, 2006 - 05:46 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have just checked and with B490, I cannot read or write the Dragon's ISP setting - it will give a failed message for both. It's rather interesting to see a new Atmel product in beta with bugs rather than ButtLoad :P.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

abcminiuser wrote:
I have just checked and with B490, I cannot read or write the Dragon's ISP setting - it will give a failed message for both. It's rather interesting to see a new Atmel product in beta with bugs rather than ButtLoad :P.

- Dean :twisted:

Thanks Dean,

I was just getting ready to download B490, when I read your post.

In lou of the initial problems I have with B488, I think I'll hold for a while and let the bug dust settle. Or, would that be the Dragon breath???

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
User of the Mighty AVR Dragon

Being used by the Mighty AVR Dragon? :lol:

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Actually John, I've been using it quite a bit. I just don't like the RESET hang with JTAG. True, I just use it for ISP right now. The little woman alotted me $50.00 to but some controllers that the Dragon supports. I'll probably order them tomorrow, after work. Maybe, if what I want is in stock, I'll get them early next week.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
The little woman alotted me $50.00 to but some controllers that the Dragon supports.

I just spend about AU$100.00 (US$75.00 ? ) on various chips supported by the Dragon but at the same time I have just received a purchase order for products (Mega8 based) worth many times more, so I didn't get into trouble....much ;)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Ahh it's the batchlor life for me. All I gotta do is eat Ramen all week and I got money for a Dragon.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
with B490, I cannot read or write the Dragon's ISP setting

Do you have by any chance the DWEN fuse enabled in the chip you are woking with? This will stop anything else from happening and will need to turn it off first.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

js wrote:
Quote:
with B490, I cannot read or write the Dragon's ISP setting

Do you have by any chance the DWEN fuse enabled in the chip you are woking with? This will stop anything else from happening and will need to turn it off first.

I know that, with some selections, I have gotten the message "Selection won't take effect until the connection dialog is exited and re-started." or, some such message.

May the god of the Dragon breath it's fire of life on the AVR and make it "ALL POWERFUL!"

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

When will the Dragon reach Europe ? (esp. Germany)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

js wrote:
Quote:
with B490, I cannot read or write the Dragon's ISP setting

Do you have by any chance the DWEN fuse enabled in the chip you are woking with? This will stop anything else from happening and will need to turn it off first.

No, it's definetly not set. Does anyone else have the same problem? Everything else in the Dragon seems to work correctly, but the setting of the ISP frequency was extreamley buggy in B488 for me too...

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

JohanEkdahl wrote:

Quote:
Uh-huh? I've found no supplier of the m32 in Sweden, so I've put the m32 on my DigiKey shopping list...

FYI: Lawicel has the M32 (lawicel-shop.se/shop/) for ~78SEK/piece. Haven't checked Digikey to compare prices though.

/C

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have a Tiny13 on a board and are running it using the debugWIRE and the Dragon, no problem on that part,
But if I want to program the tiny then it will not program that is because the debugWIRE and ISP can not be enabled at the same time.
I can resolve this by removing the Tiny and use hi voltage programming to erase the chip.
In the Dragon help file I found that I can disable it using the debugWIRE but how ?

Dragon Help file

Quote:

When the DWEN fuse is set, the ISP Interface normal functionality is disabled. This because the debugWIRE must have control over the RESET pin. When DWEN is set it is no longer possible to use ISP. Use debugWIRE or High Voltage programming to disable the DWEN fuse.”

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Start a debugging session (Debug menu, Start Debugging). Now you have an item AVR Dragon Options in the Debug menu, and in the dialogue that it brings up, on the Connection tab:

.

Attachment(s): 

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

That was the button that I was looking for, I had expected it in the programming part of the dragon,
Thanks
:lol:

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Well my conversion of a M8 project to M88 project to use the Dragon is now complete. Unfortunately I don't have ISP facilities on this board (the one I sell most of :oops: ) because it was going to have a bootloader and....well it didn't happen, so I had to make an octopus adatptor for debugWire which connects across the pullup resistor for the reset pin (picks up reset and v+) and one leg goes to ground. All working well except it seems that the Dragon has problems writing to the EEPROM of the M88 (upload/download memories) as it brings up a writing to memory error, the first 10 bytes or so seem to stick but the rest will disappear once the processor runs. The eeprom is ok as I can manually change it's values through my monitor program. Can some fellow Dragonian "Illuminato" check this up for me please? I'm still using B488 so perhaps it has been fixed in B490 if in fact it is a bug.

Forgot the (horrible) snapshot

Attachment(s): 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

John!

How did you attach the Dragon to the bottom of that box? My Dragon has no mounting holes...

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi js :)

I see you mounted a 40pin zif to the mighty dragon.
I just love zif sockets...that looks like the kind I get
from futurlec?

Your board looks nice too...I see a toroid on it...I love
to wind those little toroids...it's sort of like sewing or
basket weaving...a real art-craft kind of thing to do :)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
How did you attach the Dragon to the bottom of that box

I didn't :lol: just resting it inside the box so I don't short things out on my messy bench (as you can see though it may get mounted in that box in the future as it can accomodate the 40 pin ZIF socket). There seems to be 3 positions for holes, 2 near the USB connector and one under the 40 pin socket but I haven't drilled them yet, too chicken. I'm now commited with 2 products with the Dragon and if I kill it I'll need to rush out and get a JTAG2 in a hurry.

Can you confirm that the Dragon has problems with writing to the EEPROM please? It seems to only program the first 10 bytes. I can program the EEP with ISP but when I go back to debug mode it gets erased and downloading memories doesn't work as above, it is now getting annoying programming it by hand 1 byte at the time.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
it's sort of like sewing or basket weaving

I get to do a bit of that in the rest home but it's hard when they tie the knots in the straight jacket :lol: well have you fired it up yet?? I need to know if the EEPROM writing work or not...anyone please? :)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I only have a M168, but I can test the EEPROM for you if you want. I'm currently running the non-beta B490, which has major issues with the Dragon and its ISP setting in my experience.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
I only have a M168,

It should do, but it needs to be done within the debugWire mode, ISP works fine. I seem to remember some error message with the Tiny2313 also but didn't pay much attention then as I wasn't really using the EEPROM

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

DebugWire is amazing!

Using a M168 and AVRStudio B490, I had no problems entering dW mode, programming the first 15 bytes of EEPROM (via the Up/Download Memory option) and debugging. The EEPROM both wrote and read back correctly.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

abcminiuser wrote:
I only have a M168, but I can test the EEPROM for you if you want. I'm currently running the non-beta B490, which has major issues with the Dragon and its ISP setting in my experience.

- Dean :twisted:

It seems that its not just the Dragon that has issues with ISP settings.

I upgraded to AVRStudio B490. I'm using the STK500 to program an Tiny2313 with a 4x20 LCD connected to it. I am continually having to go back and set the STK500 ISP frequency selection. It keeps resetting back to the highest frequency setting (3.???MHz). It used to be that, once set, I never had to touch the ISP frequency setting. I'm running the Tiny2313 at 8MHz.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

I upgraded to AVRStudio B490. I'm using the STK500 to program an Tiny2313 with a 4x20 LCD connected to it. I am continually having to go back and set the STK500 ISP frequency selection. It keeps resetting back to the highest frequency setting (3.???MHz). It used to be that, once set, I never had to touch the ISP frequency setting. I'm running the Tiny2313 at 8MHz.

We've drifted off of Dragon a bit. This is the second thread I've seen now on STK500 "drift"--your ISP frequency, and another from jporter on target voltage.

My STK500 is my main programming tool, normally driven by CodeVision's built-in ISP. I've got a variety of apps, and some are 3V only, some need to be programmed slower, and some I like to do fast (Mega64 at 75%) for speed. While I do frequently fire up AVRStudio to check the settings (build 485) I've never seen either setting "drift" from what I remembered setting it to.

Lee

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

theusch wrote:
Quote:

I upgraded to AVRStudio B490. I'm using the STK500 to program an Tiny2313 with a 4x20 LCD connected to it. I am continually having to go back and set the STK500 ISP frequency selection. It keeps resetting back to the highest frequency setting (3.???MHz). It used to be that, once set, I never had to touch the ISP frequency setting. I'm running the Tiny2313 at 8MHz.

We've drifted off of Dragon a bit. This is the second thread I've seen now on STK500 "drift"--your ISP frequency, and another from jporter on target voltage.

My STK500 is my main programming tool, normally driven by CodeVision's built-in ISP. I've got a variety of apps, and some are 3V only, some need to be programmed slower, and some I like to do fast (Mega64 at 75%) for speed. While I do frequently fire up AVRStudio to check the settings (build 485) I've never seen either setting "drift" from what I remembered setting it to.

Lee

Well, I wouldn't say that the topic has drifted. abcminiuser made a statement relating to ISP issues and I expressed that I am having the same or similiar issue since upgrading to AVRStudio 490. In fact, JS has also expressed issues relating to ISP settings changing for no reason in the past

My point is:
I did not have this issue with AVRStudio 4.12 build 485 when using the STK500. This problem seems to have crept in, starting with AVRStudio 4.12, SP3, build 488 and continuing with build 490. Now I do have this problem when using the STK500 with AVRStudio 4.12, SP3, build 490

The intent of my statement to abcminiuser was that it may not be directly related to Dragon hardware but, rather, upgrades to AVRStudio to accomodate the Dragon.

Having said that, I don't see where the thread is drifting.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Interesting. As I mentioned, I'm using build 485. Do any of you remember whether there was an STK500 firmware upgrade between 485 and 490? Lessee--firing up the STK500 tool reports

Quote:

Detecting on 'Auto'...
STK500 with V2 firmware found on COM1:
Getting revisions.. HW: 0x02, SW Major: 0x02, SW Minor: 0x07 .. OK

Is that what you also have with 490?

[to Carl: I was trying to make a semi-pun with "drifted" & the settings "drift". Regular readers know that I'm probably the worst offender here at taking threads on a tangent.]

Lee

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

theusch wrote:
Interesting. As I mentioned, I'm using build 485. Do any of you remember whether there was an STK500 firmware upgrade between 485 and 490? Lessee--firing up the STK500 tool reports
Quote:

Detecting on 'Auto'...
STK500 with V2 firmware found on COM1:
Getting revisions.. HW: 0x02, SW Major: 0x02, SW Minor: 0x07 .. OK

Is that what you also have with 490?

[to Carl: I was trying to make a semi-pun with "drifted" & the settings "drift". Regular readers know that I'm probably the worst offender here at taking threads on a tangent.]

Lee

Lee,
Yes, I have and am using B490.

Here is the revision status from my STK500

Quote:
Getting revisions.. HW: 0x02, SW Major: 0x02, SW Minor: 0x07 .. OK

Here is the AVRStudio revision list.

Quote:
AVR Studio 4.12.490 Service Pack 3
GUI Version 4, 12, 0, 490

Operating System
Major 5
Minor 1
PlatformID 2
Build 2600
Service Pack 2

Plugins:

AvrPluginAvrAsmObject 1, 0, 0, 43
AvrPluginavrgccplugin 1, 0, 0, 6
Stk500Dll 1, 0, 0, 60

I am not very good at interperting Puns and Dry Humor - I never seem to get the underlying meaning. While I am of English decent, I am afraid I just wouldn't make a very good Englishman.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

I am not very good at interperting Puns

and I'm not very good at creating them. ;)

So we are all running with the same STK500 firmware, right? And using CV to program doesn't seem to cause drift. And using build 485 to ISP and otherwise use the STK500 interface doesn't seem to cause drift. But build 490 does, apparently. I wonder what "piece" of the app is causing problems--the ISP part or others?

If y'all set up your STK500 and then go in and out of the STK500 tool a number of times, and look at various tabs each time, and find a sequence that seems to cause drift, post the suspected sequence and I'll hammer it a few times with my setup to see if it appears.

Lee

You can put lipstick on a pig, but it is still a pig.

I've never met a pig I didn't like, as long as you have some salt and pepper.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

theusch wrote:

If y'all set up your STK500 and then go in and out of the STK500 tool a number of times, and look at various tabs each time, and find a sequence that seems to cause drift, post the suspected sequence and I'll hammer it a few times with my setup to see if it appears.

Lee

Well, I'm off to work right now but, when I get home tonight, I'll do some messing around and see if I can pin it down.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

abcminiuser agrees.

I'm having horrendous trouble with the Dragon and build 490. Like others (and Carl in the case of the STK500, I haven't hooked mine up to a B490 yet) my Dragon is currently "forgetting" the set ISP speed (defaulting to 1MHz every single time the window is opened). If this is a genuine problem I can send in an email to the folks at Atmel - avrbeta (at) atmel, is it not?

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
programming the first 15 bytes of EEPROM

That's 5 bytes more then what I can manage :( OK so I will DL B490 perhaps it has been fixed already.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
defaulting to 1MHz every single time the window is opened

That's about right in my experience. It was a problem all along even with B488.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Just DL B490 and having the same problem, the first 10 bytes program OK, the 11th is 0x0f and the rest does not get programmed. I have tried another chip with the same results. I have send an offcial bug report to Atmel and mentioned the ISP frequency problem also.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

abcminiuser wrote:
abcminiuser agrees.

I'm having horrendous trouble with the Dragon and build 490. Like others (and Carl in the case of the STK500, I haven't hooked mine up to a B490 yet) my Dragon is currently "forgetting" the set ISP speed (defaulting to 1MHz every single time the window is opened). If this is a genuine problem I can send in an email to the folks at Atmel - avrbeta (at) atmel, is it not?

- Dean :twisted:

Yep! 1MHz is is. But, I still haven't pinned it down, as to exactly which operation I am conductiong causes the ISP frequency setting change.

As I am using a Tiny2313 on the STk500 and programming with the STK ISP, I haven't tried the Dragon yet with build 490. I will do that and get back to you.

Edit:

Ok...

The STK500:
Every time I call up the Connection dialog, the STK ISP frequency defaults to 1.845MHz. The device in the STK500 won't even read the chip ID at that frequency. It's odd, because with the STK500 the only ISP frequency that works is 115.2KHZ. Take that literally! Now, I'm only running an 8.000MHz crystal so, by Atmel's definition, I should be able to read the fuses and program the target at the 1.845MHz setting because this is less then 1/4 of the CLK frequency - BUT it won't.

The Dragon:
When entering the Connection dialog, the ISP frequency always defaults to 8.000MHz.

At the 4.000MHz ISP selection, I can read the chip ID and read the fuses but, the target will not program. The same goes for the 2.000MHz ISP selection - this may be within Atmel spec. because the spec. does day < 1/4 of the CLK frequency.

All other ISP frequencies 1.000MHz and lower work fine with the Dragon ISP.

Again, I'm using AVRStudio 4.12, SP3, build 490.

You can avoid reality, for a while.  But you can't avoid the consequences of reality! - C.W. Livingston

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Your results mirror mine. Each time the programming window is opened the ISP frequency defaults to 8MHz (or perhaps 1MHz, I can't remember) and I need to set it to ~250KHz (for my AVR running at 1MHz clock), switch to another tab, go back and set the ISP speed a second time before I can program. If I don't set it the second time, it doesn't seem to take effect.

For the EEPROM tests I was using dW on a MEGA168, which might be different in its storage methods than your MEGA8.

- Dean :twisted:

Make Atmel Studio better with my free extensions. Open source and feedback welcome!

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
MEGA8.

Mega88 that is. I may try and rebuild the project for a M168, shouldn't be too hard, just change the vector file and inc file.....famous last words ;)

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

So I have rebuilt one of the projects for the M168 and yes it was just as easy to do as above :) the problem is still there with the M168 except that it will program 19 bytes instead of 10 as in the M88. So Dean your test was correct but not a full test, try and copy more text or data into the eeseg and try again please just to confirm my findings. I also had a lot of troubles setting the fuses for the ISP and it only worked when I went down to 125KHz with the internal 1MHz clock. The EEPROM problem occurs at both 1 MHZ int. osc. and with the 8MHz ext. crystal osc.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly