AVRISP mkII and JTAGICE mkII on Windows 10 not working after fresh install

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

Had to reinstall Windows 10 and Atmel Studio 7.

 

Now both my programmers AVRISP mkII and JTAGICE mkII don't show in Atmel Studio.

They just appear in Device Manager with an exclamation mark and the following error message:

 

"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"

 

Anyone know how to fix this problem?

This topic has a solution.
Last Edited: Fri. Mar 10, 2017 - 10:10 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

"Dare to be naïve." - Buckminster Fuller

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

I ran into a similar issue for my JTAGICE mkII. One workaround that I came across is the following:

 

 

ATMEL JTAGICEmkII - Windows 10 Driver setup Workaround:

 

Use Zadig from (http://zadig.akeo.ie/) or libusb-win32 from  (http://sourceforge.net/projects/libusb-win32/files/libusb-win32-releases/1.2.6.0/) to change the driver to libusb0.
Then the tool should appear in Atmel Studio as normal.

 

At this point you have installed ATMEL Studio and your USB Controller Driver appears in the Windows Devices list.

(If there is a Driver conflict as shown below, reinstall the driver to correct this.  Right click on the driver and select "Uninstall" then reboot.)

Driver install Conflict

 

Once the Driver is correctly installed, perform the steps shown below…

 

  1. Open the Zadig program you just downloaded.
  2. Select OPTIONS > List All Devices
  3. Then Select your Controller as shown
  4. Select libusb-win32 as the driver to be converted.
  5. Then simply select the “INSTALL DRIVER” Button.
  6. All Done!  The USB controller will now be visible in AVR Studio 7.

 

Zadig Program

 

Hopefully this will work for you.

 

Cheers!

-Gerry

Last Edited: Tue. Jan 31, 2017 - 03:03 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Once you have completed the driver patch using ZADIG, the Atmel JTAGICE mkII driver will appear under "ATMEL USB DEVICES" on the Windows Device list.

 

You can see the installed driver details from the screen cap below:

 

JTAGICEmkII Installed Driver Details

 

 

Atmel JTAGICE mkII USB controller connected

 

 I Hope this info can help some of you.

 

Cheers!

-Gerry

 

Last Edited: Tue. Jan 31, 2017 - 03:32 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks.  I will try it.

 

I like the idea of using libusb.  I use winusb to communicate with my AVRs which I think is similar.

 

libusb is used for DFU, which shows up like this:

 

 

 

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

My JTAGICE mkII does work with Studio 7.0.1188 on Windows 10.  So I figured Atmel is using libusb in this case.   I took a look and was dismayed to find it still uses jungo.  Isn't life interesting?  wink

 

I'm still going to try your fix for Studio 6.2.

 

Here's what the JTAGICE mkII looks like on Win10 Studio 7.0.1188.

 

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

Yes, it works!!!  I now have my JTAGICE mkII working with Studio 6.2 on Windows 10.   There was some confusion about the procedure which I will mention in another post.  Apparently it is foolproof though because I managed to make it work.  wink

 

 

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

So I figured Atmel is using libusb in this case.   I took a look and was dismayed to find it still uses jungo.  Isn't life interesting?

Hah... I have some news about that up my sleeve (probably). More info coming pretty soon (but not libusb...)

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

Maybe I spoke too fast.  The device programming thing seemed to work, but when I tried to close it, it hung.  A minute later it asked if I wanted to close it immediately.  I said yes, and it closed.  More testing will be required before I deem it fit for use.

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

Thanks guys, I haven't tried this yet, I created a support case with Atmel.

 

Here is an update from Atmel:

The new issue with the drivers is for the latest version of Windows, specially if it has SecureBoot.
The next release of Studio will fix this by swapping out the drivers for these old tools. Unfortunately this new release will not arrive for at least two weeks.

 

In the mean Time the workaround mentioned by Gerry_78 above I believe is the same workaround Atmel suggests and claims works.

 

This link sounds like the problem:

https://blogs.msdn.microsoft.com/windows_hardware_certification/2015/04/01/driver-signing-changes-in-windows-10/

 

​Turning off SecureBoot​ could be another alternative

Last Edited: Thu. Feb 2, 2017 - 07:49 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Not so good.  My use of libusb with Studio 6.2 works but with a nasty quirk.  It won't quit.  For instance device programming seems to do everything but close.  When trying to close, I have to wait a minute for the "Ongoing operation is taking longer..." message.  Clicking on "stop waiting" closes it but I then have to close studio and reopen it to do anything else.

 

Similarly the debugger seems to work but clicking on the "stop debugging" causes the same "Ongoing operation..." message a minute later.  One other thing about the debugger is something I think I've seen before.  The yellow arrow on the left margin where the debugger has stopped is missing.

 

This reply has been marked as the solution. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

Good news! I see a new update for Atmel Studio today. I can confirm it has fixed the problem.

My AVRISP mkII and JTAGICE mkII are now working again.

 

Install Atmel Studio Version 7.0.1416 or later

Last Edited: Fri. Mar 10, 2017 - 10:09 PM