AVR Dragon does not appear in tools menu

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

I've been using the AVR Dragon for about two weeks now, but from one day to the other (to my knowledge) the Dragon disappeared from my list of tools. I've updated Atmel Studio from 6.2 to the latest 7, reinstalled the drivers many times, but it just does not reappear in the list of tools. I've also tried different USB cables and USB ports, but nothing helps. During the process of installing the drivers it does ask me to remove the device from the USB port in order to fully install the drivers. To me this assures me the device is OK. Lights on the device are a big red one and a smaller green one. Please refer to screenshots in attachment.

 

What might be my issue? Here are some details about my setup:

 

Atmel Studio version: 7.0.582 

Processor: Intel Core 2 Duo T9300 @ 2.50GHz 
OS: Windows 10 Pro

Target AVR: ATmega32U4 (Not relevant I think...)

Attachment(s): 

Last Edited: Tue. Oct 6, 2015 - 11:24 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 3

 

We have yet to figure out why the new Studio 7 breaks existing installations of Studio (and possibly other sw that uses Jungo to access Atmel tools).

One of the posted workarounds is switching the tools to use libusb0, which almost works for Studio 6.2 and Studio7.0. While we are fixing the remaining issues with libusb0 , we are now testing another fix that switches all Atmel tools to the new Windows10 compliant windrvr12.sys driver.

 

We'd appreciate some help in testing this out:

 

WARNING : THIS IS ONLY FOR FOLKS THAT HAVE PROBLEMS WITH DRAGON, JtagIceMKII, Stk600 and other Jungo tools.

 

1.Install the windrvr12 Atmel driver package : https://www.dropbox.com/s/b1xtv1...
This will switch the tools to use windvr12.sys as kernel driver

 

To make software use windrvr12 instead of windrvr6, download this DLL  :

 

win64:  https://www.dropbox.com/s/oppwz8...
win32:  https://www.dropbox.com/s/2w0hr1...

 

For Studio 7 , rename the DLL to wdapi1010.dll and copy it to C:\Program Files (x86)\Atmel\Studio\7.0\atbackend\codeCache
For Studio 6.2 , rename the DLL to wdapi1010.dll and copy it to corresponding codecache directory in Atmel Studio 6.2 directory. Update: This may require a rebuild of Studio 6.2 to use a new license string. 

By copying it to the codecache , it should take precedence over the original wdapi1010.dll which is installed in the \Windows\system32 or Windows\SysWOW4 directories.

 

I don't have AvrStudio4 installed, but I hope this trick would work for it as well (just rename the dll to match the version used by AVRStudio4)

 

UPDATE: If using atfw, you also need also to copy the dll to the atbackend directory, to be used by fwupgrade.dll

UPDATE UPDATE: After  a while (4 days for Dave), you may get invalid license error messages. For studio 7 , please drop this DLL https://www.dropbox.com/s/w0gkok...  into the codecache directory to install a new license string. 

 

Let me know if this helps you.

 

Best regards, Dan

Last Edited: Mon. Oct 12, 2015 - 09:56 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

On initial testing this seems to have worked for me. Although I am not comfortable with having to rename DLLs in windows.

SpiderKenny
@spiderelectron
www.spider-e.com

 

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

Re: renaming the dll, this is the only option we have to make  existing software use windrvr12.sys

Future versions of Studio will probably link to wdapi1200.dll directly.

 

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

I have a jtagice mkII, stk600 and an ISP all have disappeared, I have tried this and cannot see my devices in studio 7 or 6.2. I am running a 32bit system for programming in the lab, to date my 64 bit laptop still works as does another 32 bit laptop I have available works but our programming station is down and I need to fix it as getting the other devices in the location I need them is problematic and time consuming. I have not been able to successfully apply the libusb0 fix either but I am not comfortable that I am applying it correctly.

 

 

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

 

Hi Mark

 

We haven't tested the workaround on win32 since we only have a win64 machine with the symptoms.

Do you see the tools in the Device Manager ? What driver version (sys file) are they linked to ?

 

Could you try with both wdapi1200 dll's that I linked to ?

 

Regards, Dan

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

Using Atmel's technical support ticket system I received this reply:

 

"The Jungo driver of AVR Dragon can fail with an 'Invalid License' or 'Internal system' error on some Windows 10 machines . Workaround is to use the libusb0 driver to connect to the tool. Use Zadig from http://zadig.akeo.ie/ or libusb-win32 from http://sourceforge.net/projects/... to change the driver to libusb0, and the tool should appear in Atmel Studio as normal."

 

I got it to work again using the libusb0 drivers. Thank you for your replies, I hope it may help others with similar problems.

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

Future versions of Studio will probably link to wdapi1200.dll directly.

That's good. Hopefully you'll be able to get to the bottom of the issues, and provide a patch or update for AS7 soon.

If there is anything we can do to help please let us know!

 

SpiderKenny
@spiderelectron
www.spider-e.com

 

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

 

It does work, but it's a cludge!

Hopefully Atmel will have a solid fix for us soon!

The trick above worked for me.

 

empewoow wrote:

Using Atmel's technical support ticket system I received this reply:

 

"The Jungo driver of AVR Dragon can fail with an 'Invalid License' or 'Internal system' error on some Windows 10 machines . Workaround is to use the libusb0 driver to connect to the tool. Use Zadig from http://zadig.akeo.ie/ or libusb-win32 from http://sourceforge.net/projects/... to change the driver to libusb0, and the tool should appear in Atmel Studio as normal."

 

I got it to work again using the libusb0 drivers. Thank you for your replies, I hope it may help others with similar problems.

 

SpiderKenny
@spiderelectron
www.spider-e.com

 

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

Hi Danv

Sorry for the confusion but when I went back in to replace the dll's I found they had the wrong name (my fault, I had downloaded multiple copies so I had a little(1) at the end. I can report this as working with the original instructions.

 

Thanks

Mark

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

Thanks a mill danv!

 

Ive spent a whole day trying to get my JtagICE mk2 to be recognised by Studio!  It worked fine just the other day, then yesterday studio just didn't see my ice!  I installed studio 7 from 6.2 i was using still no luck. . .

 

I tried uninstalling everything, including jungo drivers, deleting directories, removing entries from registery and reinstalling. . . same problem.  I knew my Ice was still working as tried it on an old xp machine with studio 4 and all worked!

 

Finally danv's #2 post worked! Thanks again!

 

I'm running: Windows 10 64 bit; Studio 7 now and all is working!

 

Will see about the after 4 days liscensing issue and post an update if i find i needed it!

 

Thanks again!

 

 

 

 

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

 

Not a Windows person and trying to follow Dan's instructions, above (next to top). Instructions say

 

copy it to corresponding codecache directory in Atmel Studio 6.2 directory

 I do not find a directory named "codecache". What does this refer to?

 

Also says:

This may require a rebuild of Studio 6.2 to use a new license string

In this context, what is "rebuild"?

 

Thanks

Jim

Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net

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

After some help in another thread, this was suggested for "codecache" and it worked for me. Putting it here so that others with the same question will have an answer:

 

C:\Program Files (x86)\Atmel\Atmel Studio 6.2\atbackend\codeCache

 

No "rebuild" was needed.

 

Jim

Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net

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

Amazing, thanks danv for support.

While (Jandcan->_status == ALIVE){

           figth(&Jandcan);

};

 

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

danv wrote:

For Studio 6.2 , rename the DLL to wdapi1010.dll and copy it to corresponding codecache directory in Atmel Studio 6.2 directory. Update: This may require a rebuild of Studio 6.2 to use a new license string. 

 

What does that "rebuild" refer to? I tried the procedure you describe (install driver, place dll in codecache) but it did not work.

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

Hi Rev1.0

 

What error messages do you see in the backend log ?

http://atmel.force.com/support/articles/en_US/FAQ/Obtaining-Debug-Agent-log-from-Atmel-Studio

 

(You may be better served by moving to Studio 7.0. If you can wait a few more days, the next service release will include Jungo12 driver as default)

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

danv wrote:

Hi Rev1.0

 

What error messages do you see in the backend log ?

http://atmel.force.com/support/articles/en_US/FAQ/Obtaining-Debug-Agent-log-from-Atmel-Studio

 

(You may be better served by moving to Studio 7.0. If you can wait a few more days, the next service release will include Jungo12 driver as default)

 

Ok, I installed 7.0. After install, the tools were still missing AS7 but it "suddenly" worked for AS6.2. I remembered that I already copied the "wdapi1010.dll" to the AS6.2 codecache folder according to the suggested workaround that was posted here somewhere (but it did not work before). Then I copied the dll to the AS7 codecache folder and now it works for both studio versions.

 

Looking forward to the AS7 service release anyway ;)

 

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

Thank you, Danv for the procedure -- after trying 10 other ways, this finally worked for me on Windows 10 with JTAGICE MKii.  Thanks again!

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

I was having the same problem with AtmelStudio 7 on a Windows 10 system using an AVRISP mkII.  The device did not show up in the "Tool" drop down.  I updated to the latest version of AtmelStudio (7.0.634 as of this writing) and the device is available now.  I had to perform a software update on the AVRISP mkII before the I could use it, but that went fine.

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

There are several similar forum questions here... I will repost the solution that worked for me:

 

uninstalling everything Atmel: app, directory, registry then reboot and reinstalling Atmel Studio 7.0 fresh did the trick for me!

 

https://www.avrfreaks.net/comment/1716141#comment-1716141

 

I realized that it was not just the Dragon that was not being recognized, but NO other debuggers seen; apparently cause after recent updates.

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

hi, to help all of you struggling with programming using atprogram.  and to answer dozens of posts.

I just spent another 400 hours trying to pdi my xmegas.  4th time in my xmega life. studio 6.2 & 7.0 do nor see any tools, awful, can't use studio.

the answer is:

1.  copying 3 files to ...studio7\7.0\atbackend:

      ATxmega128A4U.atdf    change these for your micro

      ATxmega128a4udef.inc

      specs-atxmega128a4u

      don't know (and don't care 1 hoot) if all 3 have to be copied.  this solves the ERROR can't set device...

2.  use command prompt inside studio.  don't know (and don't care 1 hoot) if windows command prompt works--I am so burned out.
 

<p>Vern</p>

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

I have a ATMega128 board with the ARVIPS MKII and I am using ATMEL Studio 7.0. My Computer is running Windows 10.

 

The ATMEL Studio gives me a error when trying to Build/Deploy the multi-file project, i get a "failure to open; MPCOMM_Invalid_Handle". 

 

In ATMEL Studio 7.0, under "Tools>Device Programming", i see the correct "Tool"(AVRISP "Connected"), "Device" (ATMega128), and "Interface" (ISP). However when I click apply i also get the same popup "failure to open; MPCOMM_Invalid_Handle".

 

Both LEDs on the AVRISP MKII are solid green and when I connect the USB to the PC, the ARVISP device shows up in the list under Devices. I have tried updating the driver which it states is the best driver for this device.

 

Lastly i loaded the ATMEL Studio 7.0 on another laptop running Windows 8.1 SP2 with exactly the same results.

 

Any suggestions, i am leaning towards a defective AVRISP MKII device.

 

In the 

Jallen