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

Go To Last Post
186 posts / 0 new

Pages

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

I can't vouch for anything until I understand the issue... So I would hold off a bit :)

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

Eh, I'll have to dive into the source to answer that correctly... However the driver for the Jungo tools does explicitly point to Jungo, so I'm leaning more to the theory that installing libusb (again) jiggles something enough for things to sort of work. 

 

Could you collect a diagnostic log while you use the debugger now? 

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

Since the AVR Dragon is not recognized at all, I can't use the debugger or programmer. All I can do is launch AS 6.2; here's the backend log:

 

12:01:19: [INFO] Starting local Backend Agent atbackend.exe 127.0.0.1:0
12:01:19: [INFO] Process: C:\Program Files (x86)\Atmel\Atmel Studio 6.2\atbackend\atbackend.exe /connection-port=49833 
12:01:21: [INFO] Connecting to backend agent atbackend.exe(pid:2252) 127.0.0.1:49833
12:01:21: [INFO] Connected to backend at 127.0.0.1:49833
12 01 21 765: usb WDU_INIT failed: error 0x20000009.
12 01 21 783: msg send(b8):R 1
12 01 21 784: msg recv(b8):E Locator peerAdded {"Port":"49833","Host":"127.0.0.1","ID":"LocalHIL0","Name":"Local HIL","OSName":"Windows","TransportName":"TCP"}

 

I suspect  "12 01 21 765: usb WDU_INIT failed: error 0x20000009" is the interesting error. I googled it and found that it is almost surely a return code from the Jungo WinDriver:

 

WD_NO_LICENSE = 0x20000009L

 

Cheers,

Dana

 

 

Dana  K6JQ

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

It is... No license is something we see when there are multiple WinDriver instances loaded at the same time... However the fix is as easy as reinstalling the Jungo driver...

 

I'm attaching an internal build of the Jungo installer (has a higher version than the one you are using). Does it help to run this? It should cause the kernel driver to be swapped out...

Attachment(s): 

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

This does not appear to solve this issue. Any special sequence of installing/uninstalling/etc. I should try?

Dana  K6JQ

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

Looking at the Jungo / Windrvr instance in the Device Manager, I see this notice in the WinDriver Properties:

 

Device ROOT\JUNGO\0000 requires further installation.

 

Not sure what to make of this.

 

 

Dana  K6JQ

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

Dear Dana,

 

This is the only thread that is helping me - I have an AVRISP Mk2, Windows 10, upgrade from windows 7, 64 Bit and using Studio 6.2.  The AVRISP was working fine, now Studio 6.2 doesn't see it, with no error messages at all - my only choice is 'simulation'.  The AVRISP has both LED's solid green (all good), and the device manager can see it.

 

In another document ATMEL have, they said that some programmers can't be found if you have Norton AV running.  There is an 'exe' file you need to allow (I forget what it's called) - so I did this, and nothing changed.  But they did say this 'may' be a problem. 

 

I think the key is this libusb - so I'm going to back track and try that part.

 

Thanks Dana,

Ren.

Last Edited: Wed. Sep 9, 2015 - 04:22 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I had the same experience with my Win10 system: Studio 6/ASF 3.26 with the Dragon was working fine for several weeks until Friday night Aug 4; I did not use Studio Saturday, but the Dragon (and AVRISP mkII also!) no longer showed in the dropdown list when I tried running Studio Sunday morning Aug 6.

 

Like the others who have posted, the WinDriver and AVR Dragon show in the Device Manager without any logged error events.

 

I tried the standard stuff, all to no avail (in the following order):

 

1. Reinstalled the USB driver package.

2. Reinstalled Sudio 6 (without an uninstall).

3. Uninstalled all Atmel studio and driver packages (thru the Windows uninstaller).

4. Manually removed any remaining files.

5. Did a fresh download of the install from Atmel.

6. Reinstalled.

7. Tested (no ASF), Dragon not available in the tools dropdown list.

8. Installed ASF 3.26.

9. Tested (with ASF), Dragon not available in the tools dropdown list.

10. Ran SFC: "Windows Resource Protection did not find any integrity violations."

 

I can say that KB3081452 and KB3081449 do not appear to be the culprits, since I had been using the Dragon for a week AFTER these updates were installed.

 

The only update that occurred on Saturday was KB2267602, a Windows Defender definition file. (It's difficult to envision how this would interfere with a USB driver.)

 

This issue affected the AVRISP mkII tool as well; it no longer shows in the dropdown list.

 

I tried the new Jungo 7.0.136 driver install posted by meolsen (above), but the Dragon is still not available in the dropdown list.

 

Like  danak6jq above, I also see (50+) entries in the ApplicationStatus.log:

usb WDU_INIT failed: error 0x20000009.

 

I have another Win10 laptop that - so far - still works and will become my backup dev station. However, if it becomes "infected" (for the sake of a better word), I'm really dead in the water.

 

I compared the registry entries for the Jungo driver on both systems (my main non-working one and my backup). Unfortunately, there didn't seem to be any real differences other than the GUID supplied to the Jungo driver (apparently) during installation.

 

I tried tracing with SysInternals procmon: it showed that the Jungo driver registry entries were accessed just before the log entries were added to the app log.

 

I really hope that Atmel/Jungo/whoever is able to find out what's happening here. I have a number of new Atmel-based products I'm attempting to launch - this could be a real showstopper for me.

 

I'm willing to try other tests anyone might suggest.

 

Thanks!

Dave

The SiliconHacker  Plano, TX  www.siliconhacker.com

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

I have edited this post, because I didn't use the right fix that Dana listed.

 

Installing libusb-win32-devel-filter-1.2.6.0.exe worked for me using AS6.2.

 

I'm running windows 10 upgrade, without a reinstall, 64Bit and Norton AV.  AS6.2 is now seeing the AVRISP.

 

Thanks Dana.

 

Ren.

 

Last Edited: Fri. Sep 11, 2015 - 07:49 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hmh, 

 

Could you try to find a file called 'wdapi1150.dll' in C:\Windows\SysWow64 and copy it into the atbackend folder inside the studio installation folder? (with studio and atbackend.exe not running). Then restart studio and see if the diagnostic log still shows the WDU error...

:: Morten

 

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

 

The postings on this site are my own and do not represent Microchip’s positions, strategies, or opinions.

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

meolsen wrote:

Hmh, 

 

Could you try to find a file called 'wdapi1150.dll' in C:\Windows\SysWow64 and copy it into the atbackend folder inside the studio installation folder? (with studio and atbackend.exe not running). Then restart studio and see if the diagnostic log still shows the WDU error...

 

I tried this with no success.

 

Dana  K6JQ

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

I experience the same problem and spent the last hour re-installing Atmel Studio, USB drivers, trying different cables, programmers and so on.

 

I am on Windows 10, which was upgraded coming from Win7 64. It was  definitely working until a few days ago. Since have haven't used a programmer for several days, I can't be more specific.

 

As described by the others, there are no longe any Tools listed. I tried this with Studio 6.2 (SP2 1563) and Studio 4.19.

 

danak6jq wrote:

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.
 

I added a filter for my AvrISPmkII and the Tool is now listed in Studio 6.2 and seems to work normally. However, it does not show up in Studio 4 and it does not seem to work with command line Tools.

Since I don't really understand what the libusb filter does, this may be expected behavior...

 

If there is any additional information required, please ask ahead...

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

HI. General observation, that  the fix. Oh, and what's up with this crapware forum system? Because I wrote 'is' in italics, it reversed the letters and puts it at the end...(Microsoft EDGE browser?)si​

josbleuet wrote:

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...

 

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

josbleuet wrote:

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...

Pretty sure, from 2 machines I use, and collating all other comments, that a total reinstallation (not upgrade) of Win10 fixes it.

(Oh, and please don't use Microsoft EDGE on this forum, it'll drive you more insane than the buggy forum itself!)

 

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

I surely hope the solution to this issue is not 'reinstall windows 10 from scratch'. That's completely impractical :-)

Dana  K6JQ

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

My hunch is that there's some registry key(s) involved.

Dana  K6JQ

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

I finally reinstalled windows 10 using the windows 10 reset feature. http://www.howtogeek.com/224342/.... Avr dragon is now detected in the tool menu. Something different than before, now I have to re-select the avr-dragon each time I have to program, simulator is the default choice in the tool menu, before the atmel bug, avr dragon was the default choice!!  I am afraid now each time I am pressing the tool menu, and has a final fix, my network cable will stay unplugged and my computer running 24/24 until Atmel say's that the problem is found and fixed.. Hoping they will decide to take this problem seriously... Special thank to Dana for his support and the trick found ! ;-)

Jos

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

Totally agree with you Dana in that a total reinstall of windows 10 is impractical seeing as running libusb-win32-devel-filter-1.2.6.0.exe takes little time and sorts the problem.

 

Thanks so much Dana.

Ren.

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

renkitch wrote:
running libusb-win32-devel-filter-1.2.6.0.exe takes little time and sorts the problem.

For me, it sorts the problem only partially. As I already mentioned, the device is listed in Studio 6.2 but not in Studio 4.19 and the command line tools are not automatically recognizing it.

 

I am looking forward to some updates from meolsen. I hope Atmel figures it out soon.

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

I hope Atmel figures it out soon too 'Rev1.0'.  I had the same problem with Studio 5.1, so I assumed that the 'filter' would help all versions, but perhaps not Studio 4.  One thing is that the 'filter', using Studio 6.2, completely cured the problem for me - even on closing - it's just as it was pre-windows 10.  So I'm sorted, but this isn't the fix for everyone.  It will be interesting to know what's causing it, as a few more people are gradually going to start finding this out when they start up Studio thinking their 'untouched' system, now with Windows 10, is going to work as it did a few months back.  Or perhaps this may be a specific problem for a certain few of us?  I have a HP Pavilion i7, which was running windows 7, then I took the free upgrade to windows 10.  It has a set of standard USB ports, and some SSUSB ports on the top.

 

 

Last Edited: Fri. Sep 11, 2015 - 02:04 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hello All:

I'd like to add a few more datapoints to this issue:

 

First, to Josbleuet: just wondering, have you checked the Tools->Options->Tools "Automatically pick a tool" setting. Maybe this value changed after your reinstall?

 

Second, I ran Microsoft Message Analyzer on my two systems (both Win10, one with and one without the driver issue). The interesting thing is that the trace of the AVR Dragon driver events is identical on both systems. (I expected a variation somewhere along the line, but there wasn't any. I also looked for some error indication but also did not find any.)

 

At this point, I began to suspect the WinDriver (Jungo Connectivity). On a whim (or desparation?) I found the jungo site and downloaded an eval version 12 driver. That made no difference - except that now, even after uninstalling it, I can't seem to reinstall the version 11 WinDrive driver from the Atmel driver-atmel-bundle-7.0.888.exe installer. I may have to uninstall everything (again) and reinstall everything (again).

 

This is really an exasperating issue. I echo the sentiment (renkitch) that we hope Atmel is really digging into this. Studio 6 is a great app - and personally I really like Win10 - but if our brilliant new code can't be downloaded to the target, we're dead in the water. And the reality of it is this: it simply is not practical to try to revert to older systems that may still work today but might not tomorrow. Software/OSes/apps continue to change - we don't really have much alternative but to change with it.

 

Atmel, please give us an update on this issue. I/We love your products, but this is killing me/us. I have new Atmel-based products to release soon and this is definitely NOT helping.

 

The SiliconHacker  Plano, TX  www.siliconhacker.com

Last Edited: Fri. Sep 11, 2015 - 03:57 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi All,

 

I took a week break from coding (everything was working fine before) and come back to find the problem described here. Having quite a few projects with Atmel processor that need to be completed. Dana's solution is working for now.

Really hopping for a permanent solution. This forum is really help me from thinking I did something wrong. Now I often get this error message:

 

 

Waiting for an operation to complete

An ongoing operation is taking longer than expected.

Details: Tool ->tearDownTool

You can stop waiting for the operation, in which case you may need to restart AVR studio, or wait some more

 

(The timeout can be set using the "Tools->Options->Debugger->AVR Debugger -> AVR Communication Timeout" option.)

 

Mickey Nguyen

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

Hi All,

I also have the problem described by above, I started up Atmel Studio after a longer break and the Dragon disappeared from the tool list. Background is similar to the others: Win7 64bit -> Win10 upgrade, everything was working fine right after the upgrade and the Dragon went missing this evening. I have uninstalled/reinstalled the Atmel USB drivers, then the whole Studio 6.2 with lots of reboots, USB port checks and cable checks. Windows reports the device is present and ready. I do have the arduino ide installed and also avrdude.

 

The windows version of avrdude also has problems with the dragon: avrdude: usbdev_open(): did not find any USB device "usb" (0x03eb:0x2107)

Whereas I have the dragon in device manager under Jungo Connectivity status is 'Device is working properly' and HW Id's are: USB/VID_03EB&PID_2107

 

I did not try the libusb-win32-devel-filter.exe mentioned by others, but since the device is not found by the dragon I suspect that the driver rejects requests with the 'no license' error.

 

Hope to get a proper solution for this issue...

 

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

I compared the installed windrvr6 on my two PCs (one without problem the other with the problem described).

Just for fun I replaced the file windrvr6.sys (directory C:\windows\system32\drivers) with the version that did not show the issue - version 11.3.0.0 date 2013/05/12 and now both dragon and AVRISP mkII are recogniced in studio 6.2

strange but :)

Anykey

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

Can you upload the sys file wich will work?
So i can check it in my setup.

Thanks

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

As requested

Please note: There are two versions, one for  32 bit systems and one for 64bit systems

of course I first removed the libusb32 filter which I had installed according to the earlier posts

Attachment(s): 

Anykey

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

Thank you!
In my case, your solution didn't work :(
After replace the file, the device manager show an error because the signature was not correct.

Daniel

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

I suppose you used the correct file and you rebooted your PC. Device manager on my PC is showing no error.

Perhaps you need to install the complete driver package of version 11.3.

I will check where I downloaded it from but I assume it came with one of the previous Studio releases.

Anykey

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

I double checked the device manager. It still shows that version 11.5. which probably came from Atmel USB Driver Installer 7.0.888, downloaded from Atmel, however the windrvr file is definitely 11.3

Maybe that is the way to go. Install 11.5 first and then replace the file.

Just guessing.

Anykey

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

I downloaded the Atmel USB Driver Installer 7.0.888 and check the windriver version in device manager.

It was 11.5.0.0

 

Reboot => remove the file windrvr6.sys from C:\windows\system32\drivers => reboot => copy your attached windrvr6.sys (64) => reboot

 

It does not work :(

 

The Device Manager shows an error because the signature is not corret...

 

 

Daniel

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

I tried again with several different versions of windrvr6.

I only get an error in the device manager if I use the wrong type - 64bit instead of 32bit.

(I'm running windows 10 32bit on that particular machine)

Anykey

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

Hi all:

 

Per anykey's experiment, I compared the WinDrvr6.sys file on my laptop that still works against the one that doesn't: they are both identical (version 11.5 from the current Atmel install).

 

I then tried anykey's version 11.3 file for my system; unfortunately, it did not work. The same errors appear in ApplicationStatus.log and only Simulation appears in the dropdown in tools.

 

The newest driver from Jungo is version 12.0; I had already tried it but found it also did not work (as I noted in a previous post). However, I just noticed that the timestamp on the WinDrvr1200.sys file is BEFORE all this trouble started. Since I uninstalled it (or so I thought), I was surprised to find it.

 

I just renamed WinDrvr1200.sys, and removed all references to it from the registry, but still no joy. Arrgh..., this is really annoying.

 

For everyone's info: I opened a case with Atmel (00024676) yesterday. (I assumed others had as well, though a quick search before I opened the case seemed to indicate that one had not yet opened a case.)

 

Thanks, all. It would be great if someone found the secret handshake that makes this work - and what it is that broke it in the first place...

Dave

The SiliconHacker  Plano, TX  www.siliconhacker.com

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

This workaround from german mikrocontroller.net works

http://www.mikrocontroller.net/topic/376358?goto=new#4270744

Last Edited: Sun. Sep 13, 2015 - 08:02 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi all:

 

HOLD THE PRESSES!!!

 

The Dragon is now seen from Studio 6.2; here are what appear to be the critical steps:

1. I'm not using the lib32usb filters mentioned above.

2. I am using the 11.3 WinDrvr.sys driver (copied from anykey's zips).

3. I manually removed the WinDrvr1200.sys driver from System32\drivers.

4. I manually removed all references from the registry.

5. I REBOOTED the system. (This appears to be necessary, since until then the Dragon still could not be seen.)

 

Please note that I had already "uninstalled" WinDrvr1200.sys a few days ago. Obviously, the uninstallation left enough traces around to mess up the system.

 

It would be interesting to learn if the 11.5 driver would still work. So, for those of you that still experience the issue: is WinDrvr1200.sys in System32\drivers? If so, please try steps 3 thru 5 above (before changing to the 11.3 WinDrvr.sys driver) and let us know if that works. If it does, then some weird issue rolled in with an install of WinDrvr1200 (source unknown) that appears to have taken place sometime mid August (a Windows update maybe???).

 

We will have to wait to see if these steps hold.

 

Dave

The SiliconHacker  Plano, TX  www.siliconhacker.com

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

Hi All,

 

At first I tried the 'filter' solution, AS6.2 see the Dragon but I constantly get the timeout message so I couldn't really use it to debug.

Didn't want to do Windows 10 re-install, but I was desperate. Here is what I did and everything seem to work so far:

  1. Uninstall the 'filter' software and reboot to confirm that AS6.2' 'Tools' only available option is 'Simulator'.
  2. Uninstall AS6.2 and everything else that associated with it. Reboot.
  3. Use 'regedit' to search for anything Atmel and delete them all. (Of course, always backup your registry before doing so). Reboot.
  4. Use Microsoft Media Creation to create Windows 10 installation on the thumb drive.
  5. Run the 'setup.exe' from the thumb drive to reinstall Windows 10 and suck my thumb for the next 2-hrs for Windows to re-install.
  6. Re-install the latest AS6.2 ONLY (Version: 6.2.1563-Service Pack 2).
  7. I DID NOT installed the Atmel Software Framework Update nor the Standalone USB Driver from Atmel. (Everything seem to work so I am reluctance to update anything until I finish my project)
  8. Reboot and start AS6.2...
  9. .....so far so good...now I can get back to write codes...

 

Note: I did NOT do the 'clean-clean' installation of Windows 10. I chose to keep all my settings and apps. I agree that it's not practical to 'drop' your PC and all the apps. If I have to, I better off buy a new PC...

Mickey Nguyen

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

I had the same issue with a STK600 board on windows 10-64bit

 

I tried the link meldano posted to that German forum and it worked so far.

 

For those who can't read German...

 

1. download this program called zadig  at  : http://zadig.akeo.ie/

2. have Atmel studio completely installed

3. run zadig program

4. go to options > List all devices

5. select the programmer/board you want to modify the driver for (in my case STK600). Use the first selector box for that.

6. right next to driver in the second box right of the arrow select libusb-win32

7. press the replace driver button

8. look in windows device manager and your board/programmer will no longer be listed under Jungo , it will have its own category "Atmel USB Devices"

9. start Atmel studio and go to device programming and your board should be available again.

 

 

 

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

I tried this and ended-up with the same functionality as installing the libusb-win32 filter. The AVR Dragon is detected, but closing the AVR Dragon tool results in time-outs. It seems like this is just another way to use libusb-win32, which doesn't completely work with AVR Dragon.

 

I'm not inclined to do any kind of Windows re-installation. There's a bug here; it's possible that Atmel and/or Jungo are the victim of some change Microsoft made, but I'm really stuck until they can sort it out.

 

Dana  K6JQ

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

Just out of interest.

Did anybody else apart from Daniel and Dave try to replace windrvr6.sys by version 11.3

Anykey

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

Crikey!!! Sorry about the multiple comments...Massive delay (1 min. or so) from click to anything happening on this forum.

Oh, about the forum and windows 10, EDGE, by the way, try typing anything in ITALICS! !sdrawkcab si etirw uoy  revretahw​  Hilarious!

Last Edited: Wed. Sep 16, 2015 - 04:29 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

.

Last Edited: Sun. Sep 20, 2015 - 02:05 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Yep - just happened to me. I'm the "Reinsall Windows from 10" idiot, who thought that was it. No Dragon, no work. My Atmel-ICE is at another workplace. (and the connecting cable looks too fragile to even think about moving it).

BUT, just tried using the using the "Zadig" fix above....It's BACK!

Phew!

 

 

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

Yep - just happened to me. I'm the "Reinsall Windows from 10" idiot, who thought that was it. No Dragon, no work. My Atmel-ICE is at another workplace. (and the connecting cable looks too fragile to even think about moving it).

BUT, just tried using the using the "Zadig" fix above....It's BACK!

Phew!

 

 

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

Yep - just happened to me. I'm the "Reinsall Windows from 10" idiot, who thought that was it. No Dragon, no work. My Atmel-ICE is at another workplace. (and the connecting cable looks too fragile to even think about moving it).

BUT, just tried using the using the "Zadig" fix above....It's BACK!

Phew!

 

 

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

Yep - just happened to me. I'm the "Reinsall Windows from 10" idiot, who thought that was it. No Dragon, no work. My Atmel-ICE is at another workplace. (and the connecting cable looks too fragile to even think about moving it).

BUT, just tried using the using the "Zadig" fix above....It's BACK!

Phew!

 

 

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

Yep - just happened to me. I'm the "Reinsall Windows from 10" idiot, who thought that was it. No Dragon, no work. My Atmel-ICE is at another workplace. (and the connecting cable looks too fragile to even think about moving it).

BUT, just tried using the using the "Zadig" fix above....It's BACK!

Phew!

 

 

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

Yep - just happened to me. I'm the "Reinsall Windows from 10" idiot, who thought that was it. No Dragon, no work. My Atmel-ICE is at another workplace. (and the connecting cable looks too fragile to even think about moving it).

BUT, just tried using the using the "Zadig" fix above....It's BACK!

Phew!

 

 

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

Yep - just happened to me. I'm the "Reinsall Windows from 10" idiot, who thought that was it. No Dragon, no work. My Atmel-ICE is at another workplace. (and the connecting cable looks too fragile to even think about moving it).

BUT, just tried using the using the "Zadig" fix above....It's BACK!

Phew!

 

 

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

I wanted to try, but I don't have the windrvr.sys in system32/drivres. On my machine the only instance in the windows folder is located in DriverStore/FileRepository/<some funny foldername with long UUID>, and I'm not confident in overwriting it (Win10 64bit).

On the other hand I tried this:

- removed the 2 related devices in device manager with the "delete the driver" option

- uninstalled everything related to atmel, jungo, segger from programs and features

- manually removed everything from the registry matching the keyword jungo

- rebooted

- installed the latest studio

- ...and nothing changed! Dragon shows up in device manager, but neither studio nor avrdude is able access it

 

I want my Jungo Unchained! :(
 

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

same problem, AVR ISP mk2 not more recognized in AVR Studio under Win10.

(JTAGICE3 is recognized, but the ISPmk2 not, strange)

 

this help me get it working:

https://www.avrfreaks.net/comment...

 

Last Edited: Fri. Sep 18, 2015 - 12:33 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Happens to me exactly the same, and the same error "Invalid license"
Also I have Windows 10.
I tried lot of things and definitely solves no.
With Atmel Avr studio 6.1 if dragon appears but it is nothing to program.
I suspect the "atmelinf.cat" file, he says "This Restraint catalog is not valid".
Although I get the same message in all the .cat files that have nothing to do with Atmel.

Pages