Atmel Studio stopped seeing AVR Dragon; possibly Win 10 update related

Go To Last Post
180 posts / 0 new

Pages

Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

 

I've been using an AVR Dragon for several years, first on Windows 7 x64, and I successfully upgraded to Windows 10 at the end of July. The AVR Dragon continued to work correctly under AVR Studio 6.2 SP2 (details below).

 

Friday evening August 28, I was using AS 6.2 + AVR Dragon with a target ATmega32U4 via ISP. After several successful programming sessions, AS suddenly no longercould access the AVR Dragon - I spotted an error regarding "license  not valid" in one of the alerts. Note that around this time, I noticed an alert from Windows 10 that an update had been installed. This PC is an HP i7-4770 system, fast, with 16GB of RAM. There were no changes to the target fuses, voltages, etc.

See below; the same target and Dragon work fine on an old, slow Windows Vista box.

 

So of course I rebooted, uninstalled, reinstalled and generally spent over an hour messing around.

 

No luck. I can see the AVR Dragon in Windows Device Manager, under the Jungo node. Windows thinks the AVR Dragon driver is installed correctly and working; AS 6.2 simply does not see it as a target under any circumstances.

 

I fired up an old Windows Vista x64 machine, installed AS 6.2, and the Dragon works fine with the same target.

 

I'm guessing a Windows 10 update changed something how the Dragon is enumerated and AS 6.2 no longer sees it.

 

Has anyone else seen this?

 

Dana

 

This topic has a solution.

Dana  K6JQ

Last Edited: Sat. Feb 6, 2016 - 01:55 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Do you see what recent updates you have received in Windows 10? Would be interesting if you could post a list so that we can cross-check...

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

These are the suspects:

 

Cumulative Update for Windows 10 for x64-based Systems (KB3081448)

Update for Windows 10 for x64-based Systems (KB3081452)

Update for Windows 10 for x64-based Systems (KB3081449)

 

Microsoft doesn't reveal much of what was updated, just a (very long) list of files.

 

Dana  K6JQ

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

Hmh, have you tried uninstalling and then installing the drivers again? (they are downloadable from the Atmel Studio 6 page on atmel.com). 

 

Also, running sfc might tell if some files have been corrupted...

 

My dime is on KB3081449 btw...

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

meolsen wrote:

Hmh, have you tried uninstalling and then installing the drivers again? (they are downloadable from the Atmel Studio 6 page on atmel.com). 

 

Also, running sfc might tell if some files have been corrupted...

 

My dime is on KB3081449 btw...

 

I totally tried uninstalling, rebooting, and re-installing the drivers a couple of times. The Atmel USB driver package. Device Manager tells me that the drivers installed correctly, the Dragon is functioning. But AS doesn't enumerate it. sfc /scannow says it can't find any integrity violations.

 

 

Dana  K6JQ

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

I tried uninstalling KB3081449 and KB3081448 to no avail. KB3081452 wasn't uninstallable.

Dana  K6JQ

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

Exactly same situation here avr dragon not detected inside atmel studio 6.2.1563 service pack 2. I was using avr dragon for several years, upgraded to windows 10 on july and setup worked fine until tonight 2015-08-31. It was working last week.

Windows update KB3081452,KB3081449,KB3074678,KB3074686 nealy installed

Jos

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

Hmh, I have added this to our internal bug tracker. AVRSV-6873.

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

Thank you. Please feel free to contact me for any additional information I can offer.

 

 

Dana  K6JQ

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

I have a plan, so I might need you to test a new driver sometimes tomorrow :) 

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

meolsen wrote:

I have a plan, so I might need you to test a new driver sometimes tomorrow :) 

 

I am more than happy to help.

 

Cheers!

 

Dana  K6JQ

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

I did a windows system restore and rolled back to a configuration of last week.. Same result, avr studio can't see avr dragon. I also did a repair of atmel studio and atmel USB driver from the window control panel->programs. No success.

Jos

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

On a second laptop, windows 10 , KB3081448,KB3081449,KB3081452 already installed and without atmel studio on it. I downloaded and installed a fresh atmel studio.  Conclusion: Avr dragon is displayed in the list of programming tools and working.

 

possible solution:

To repair my main laptop setup, I will try to uninstall atmel studio and manually delete all files related to atmel studio before re-installing it ?....

Jos

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

I thought I tried this experiment on my PC - uninstall/delete all files, including older Jungo drivers and what not, reinstall - and had no success.

 

Dana  K6JQ

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

Hmh, my brilliant idea didn't work... Hope to get a new one tomorrow :)

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

Failed again, desesperate.

 

From programs, I uninstalled Atmel studio, atmel usb, atmel usb driver package.

In control panel -> device manager I unstalled jungo windriver.

With the file explorer I deleted c:\users\my user\appdata\local\atmel, c:\users\my user\appdata\roming\atmel, c:\program files (x86)\atmel.

with regedit I deleted all the keys with the word atmel. also in the system part usb avr dragon removed.

 

After rebooting in control panel device manager, AVR Dragon was yellow.. so fine! driver is really deleted.

 

I reinstalled again atmel studio, rebooted... and sh...t .. no avr dragon in the programmer list.. 

In device manager Avr dragon seems in health.

 

?????

Jos

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

I found another guy with the same trouble.

 

http://www.mikrocontroller.net/t...

Jos

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

I'm not *really* suggesting this as a practical work-around, but I start up an Ubuntu virtual machine (under VirtualBox), attach the AVR Dragon to the VM (Devices > USB > AVR Dragon), access the binary ELF file via a shared folder, and then I can program the AVR using avrdude. Every time I do it, AVR Dragon detaches from the VM and I have to reattach it. Very tedious. It does, however, work.

 

Dana  K6JQ

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

Eh, I'm not really able to reproduce this... I have just tested with a Windows 10 with all patches listed here applied, and the driver works just as it should... 

 

Could you try to force a fw upgrade of the tool, using atfw? See for instance http://atmel.force.com/support/a... for an example (substitute the tool name and paths). This is to check the full usb stack...

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

Thanks to help us, it is also working on my small laptop windows10 Intel i5. I will try to upgrade the dragon like you said and let you know. I cannot do it right now, around +8hours I will test it.

Thanks again, I appreciate that you have tested the setup.

Jos

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

 

I attempted the forced upgrade as described; it does not succeed and reports "No tool is found." Of course I see the AVR Dragon in the Windows Device Manager under the Jungo node. Driver version is 11.1.0.0.  There's also a WinDriver that's version 11.5.0.0. Well, OK. I uninstalled both of these, then 'Scan For Hardware Changes'. A device node for AVR Dragon re-appears (v11.1.0.0). No luck accessing the tool, though. Note that I am running 64-bit Windows 10, if that makes a difference.

 

 

Dana  K6JQ

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

You'll need to re-add the WinDriver node as well... To do that, right click the root node in the device manager -> add legacy hardware -> next -> bottom of the two radio buttons -> Find Jungo in the list -> Jungo -> WindDriver...

 

(... ish)

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

I find both "Jungo" and "Jungo Connectivity" - is one preferred?

Dana  K6JQ

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

No, not really (although, there should only be 1... Try one and see if it works, and if not try to switch)

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

Last Edited: Thu. Sep 3, 2015 - 05:56 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I managed to uninstall/delete all version of AVR Dragon and WinDrvr, reboot, freshly install the Atmel USB drivers package, and then plug the AVR Dragon. Device Manager shows me both the AVR Dragon and WinDrvr nodes under Jungo; AS 6.2 still does not see the tool.

 

I'm suspecting something persistent in the Windows Registry at this point. Any points to clearing out the registry for a re-try?

 

Dana  K6JQ

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

Good news, I was able to reproduce the problem on my laptop #2 working laptop. In atmel studio, you have just to update your ASF TO Release ASF3.26 (Aug 2015) . Then reboot your computer and you will loose AVR dragon from the tool list.

Jos

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

So I made some progress.

 

I do not believe drivers are the problem here. Windows Device Manager thinks there are working drivers attached to the AVR Dragon. Yet, applications don't see the AVR Dragon. So I fished around a bit and discovered something called libusb-win32 is likely being used by the Atmel applications. On a whim, I downloaded libusb-win32-devel-filter-1.2.6.0.exe, installed it, and added a filter for AVR Dragon.

 

Well, that's some progress there - now I can launch the debug/programming tool for the AVR Dragon and successfully program the AVR target. The only problem I'm seeing so far is an error when attempting to close the programming tool:

 

19:39:17: [WARNING] TCF command: Tool:tearDownTool timed out
19:42:29: [ERROR] , ModuleName: TCF (Tool:tearDownTool:Timed Out)

 

after waiting a minute or two.

 

Is libusb0.dll involved? Perhaps it is signed and that signature has been revoked in a Windows update? Something like that?

 

Dana  K6JQ

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

I followed your recommendation, installed the filter and it worked (after rebboot). Not only for the Dragon but also for then AVRISP mkII where I ecperienced the same problem.

I'm also seeing the error after a while when trying to close the tool. However that only happens if the target is still connected to the tool; if you remove the connection prior to closing it closes immediately and no error is shown.

Anykey

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

Hmh, this is sort of perplexing. libusb is (should) not be involved unless you have used avrdude and the libusb filter before... Have any of you had avrdude (arduino ide) before the update?

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

I never installed avrdude. Anywhere.wrong theory.

Jos

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

Actually yes, as part of WinAVR (I had used Programmer's Notepad for a while).

FYI: Both AVR Dragon and AVRISP mkII are recognized on my second PC under Studio 6.2, running Window10 64bit and no WinAVR installed

Anykey

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

Try to install Asf3.26 update in atmel studio on your second pc, this should create the problem.

Jos

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

ASF 3.26.0 is already installed - no problem

Anykey

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

Mmm.. Have you rebooted your computer? Could you try to reboot and see?

Jos

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

I have not ever used avrdude or the libusb filter on this Windows system before, nor have I used the Arduino IDE on this system. I noticed that the Atmel USB Drivers directory contains libUSB0 and that's what led me to experiment with libusb. 

Dana  K6JQ

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

It does, but it's only used for firmware upgrade of the mEDBG kits and DFU... So I can't really fathom why it should interfere...

 

Also, how ASF should be involved is also... not going to state impossible, but improbable? It does nothing whatsoever with usb....

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

meolsen wrote:

It does, but it's only used for firmware upgrade of the mEDBG kits and DFU... So I can't really fathom why it should interfere...

 

I love these kind of problems. Well, by "love" I mean I hate them. I know next to nothing about USB device I/O on Windows so I'm stumbling around a bit in the dark. What interface does the programming tool use to enumerate and access the USB-connected tools? Is it possible the tool attempts using more than one interface and falls back to libusb?

 

Quote:

Also, how ASF should be involved is also... not going to state impossible, but improbable? It does nothing whatsoever with usb....

 

I tend to think that is coincidental, or provides one piece of the puzzle. It seems that this problem is not the result of a single element - perhaps a few pieces need to be present for this to happen.

 

Dana  K6JQ

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

laugh time to take a long weekend methinks...

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

meolsen wrote:

laugh time to take a long weekend methinks...

 

Cheers, Morten! I'm a little surprised to have a somewhat-workable work-around.

 

Dana  K6JQ

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

I had a problem with Vista when changing the drivers associated with a particular VID/PID. Windows cached a driver for each particular USB port so even removing the device and deleting the driver did not get rid of the old association.  Replugging would magically find the old driver again even after it was supposedly deleted.

 

I had to plug it into every USB port, let it enumerate, then remove device and delete driver software. Until it finally said it could not find a driver after making the complete rounds. Then i could load the new .inf file.

 

Don't know if W10 works that way but it can't hurt to plug into every USB port to see if one of them has links to an old driver.

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

I was not beleiving on the patch found by danak6jq about libusb-win32 but I tested it and working also on my side, I am able to download into xmega. Like he said, many freezing glich, like switching from isp to jtag and no debugging possible..

Thanks man!.. still waiting for the final fix...

Jos

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

hello josbleuet,

 

i know, it dont help you, or us, but i have the same problem. :-( Windows 10 with avr dragon and the installed ASF 13.26. at first I thought, the problem are on my laptop, but then i found here the thread about the same "lovely" problem. Many thanks to you that you have descripe your problem here on that forum!

 

That is a really big problem.... wow, the avr often sells, not only in asia, but also in other countries. surprise 

If i have coded a so big mistake on my job, I know that there would be a work for the weekend and in a lot of nights to, fix the problem.

 

Back to my problem:

I have reinstalled many times, but it doesent help me, i have try to editing the windows registry, nothing helps.

I will try out the libusb setup.

 

I hope that they really fix that.

 

 

Last Edited: Fri. Sep 4, 2015 - 08:28 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

libusb-win32-devel-filter-1.2.6.0.exe worked for me as well, even with the freezing, better than no programming at all!! Thanks.  

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

Another data point: I am also having the same issues. I have upgraded to Windows 10 x64 from Win8.1, and my AVR Dragon exhibits the exact same problems as others in this thread.

 

Not only my Dragon, but my JTAGICE3 is also no longer visible in AVR Studio 6.2

 

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

Meolsen, could you try to reproduce our problem on your machine?

Jos

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

I have, and I am not able to. However it as far as I can see related to updating Windows 10 (we only have clean installations of Windows 10 on our test machines).

 

However see also this thread for some more info...

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

 

Bit terrified to try it - tight deadlines, no Dragon, stuffed (Atmel ICE not yet tested)

However, I tried the Dragon on the home PC; Win10 Pro, 32-bit. Seems Okay...
But, when I upgraded windows 10, when it registered, I got the new key (with Belarc Advisor) and did a fresh install of everything*. All is up-to-date, and working.

I did the same on the work PC (Home/64Bit)...bit scared to try it.

I'll be watching this thread anxiously.

Use Windows Media Creation tool http://www.microsoft.com/en-us/s...

 

 

 

 

Last Edited: Tue. Sep 8, 2015 - 06:01 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Atmel-ICE should not be affected, as it does not use the Jungo kernel driver, but the default Windows HID driver...

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

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

 

My victim system is a 64-bit system, was running Windows 7 Pro from the factory. I upgraded to Windows 10 (pro) on July 29. AVR Dragon continued to work until 28 August when I got a batch of Windows 10 updates while running AS 6.2 + using the Dragon. I'm wondering if there's a twist here - that the Dragon needs to be in actual use when the Win 10 update (not upgrade to Win 10, but an update to Win 10) is applied.

Dana  K6JQ

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

Hello Morten,

 

I'm wondering what interfaces the Atmel tools use, since libusb does make the AVR Dragon somewhat usable. Do the Atmel tools try multiple interfaces as a fall-back? Is there a simplified test-case that is interesting?

 

Cheers,

Dana

 

Dana  K6JQ

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

Meolsen, is your windows 10 a 64bits, have you rebooted your computer at least two times and retested? If the answer is yes yes, I will re-install windows10 from scratch...

Jos

Pages