Atmel-ICE firmware & driver hell

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

I'm running Win10 as a VM and using Atmel Studio 7. Today, stupidly, I decided to update AS without first taking a snapshot of the VM. Once the update was done I hit all manner of problems that, long story short, led me to completely remove AS, partly with the aid of Revo Uninstaller, and re-install from scratch. That seemed to solve my problems, right up to the point when I went to upload a program to an ATMEGA using my Atmel-ICE.

 

A dialog box popped up saying I needed to update the firmware on the ICE. I clicked the button to do this and it seemed to be doing stuff. A progress bar progressed while the dialog box said 'Waiting for bootloader usb enumeration'. The progress bar finished and the dialog box said the firmware had successfully updated.

 

It lied.

 

Because in the meanwhile, the ICE seemed to have disconnected and I got another window pop-up saying: The connection for the USB device ‘Atmel HIDBLDR’ was unsuccessful. Driver error.

 

This might be partly to do with VMware not recognising the 'Atmel HIDBLDR' device (this VM is configured so that the ICE automatically gets connected to Windows). I've now configured the VM to also automatically connect Atmel HIDBLDR.

 

I thought there might be a driver issue, so removed the Atmel drivers and tried re-installing. That seemed to go okay, but didn't fix the problem. I did a 'repair' of AS7, which seems to be pretty much a new install (takes as long). But no joy.

 

Now I'm at the stage where I can plug in the ICE, hear Windows make its little noise that says it's seen a device (so it's being presented to the VM rather than the host), but then it pretty quickly disconnects again. So I'm stuck not being able to program the device.

 

In Device Manager, when I plug the ICE in, an 'Atmel-ICE Data Gateway' device appears under 'Atmel' and a 'HID-compliant vendor-defined device' and a 'USB input device' appear under Human Interface Devices.

 

Any suggestions where I go from here?

Last Edited: Tue. Apr 24, 2018 - 07:53 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

speculatrix wrote:
I've now configured the VM to also automatically connect Atmel HIDBLDR.

Microchip

Microchip

Atmel Studio

Manual Upgrade

http://www.microchip.com/webdoc/GUID-ECD8A826-B1DA-44FC-BE0B-5A53418A47BD/index.html?GUID-32EF9F94-0F7C-4165-ABD6-F3B53B877518

 

P.S.

speculatrix wrote:
I did a 'repair' of AS7, which seems to be pretty much a new install (takes as long).
Atmel Studio 7 clean (patch, delete, uninstall, reinstall)

Remove AS7 user data

by bentm

https://www.avrfreaks.net/forum/remove-as7-user-data

...

https://www.avrfreaks.net/forum/remove-as7-user-data#comment-2401206

 

P.P.S.

if push comes to shove then consider dual-boot to get a successful run of atfw.exe

Windows 10 can be installed without an activation key (iow with a setup key) and be functional for a "while" with nags and a watermark.

An alternative is the evaluation distribution of Windows 10 Enterprise; IIRC its lifetime is 90 days.

 

TechBench by WZT (v4.1.1)

https://tb.rg-adguard.net/public.php?lang=en-US

Microsoft

Appendix A: KMS Client Setup Keys

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj612867(v=ws.11)

 

Edit: 1st URL

 

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

Last Edited: Tue. Apr 24, 2018 - 10:13 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I've now discovered the setting that sets AS7 to ignore firmware updates for the tool, and that has got me back to a working system. So it seems pretty certain that it's a problem with the ICE becoming disconnected, effectively changing identity (from Atmel-ICE to HIDBLDR) and this causing problems with the VM. I'll try the atfw.exe approach and if that doesn't work I do have an old Win7 laptop knocking about somewhere.

 

[Edit] Tried using atfw - didn't go well. It was basically the same problem. The ICE goes into firmware flashing mode but is effectively disconnected from Windows in the process. For some reason, VMware isn't making it available. So I guess I'm stuck with the current version of the firmware for now.

Last Edited: Wed. Apr 25, 2018 - 08:14 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Gah! Well, just to round off this sorry tale, I booted up my old Lenovo Win7 machine that hasn't been switched on for some months. Several hours and multiple reboots later I finally had all the Windows updates installed. I completely removed the copy of Atmel Studio 6. Then I tried installing AS7. No go. The installer barfed during its 'Windows update' checks. It insisted I needed a specific update (KB2999266). I downloaded the update from MS and tried installing. 'Your computer does not need this update' insisted Windows. So there you have it... I'll just soldier on with the old firmware and remember never to update Atmel Studio ever again.

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

speculatrix wrote:
The installer barfed during its 'Windows update' checks. It insisted I needed a specific update (KB2999266). I downloaded the update from MS and tried installing. 'Your computer does not need this update' insisted Windows.

Catch22!

 

 

Click Link: Get Free Stock: Retire early!

share.robinhood.com/jamesc3274

 

 

 

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

speculatrix wrote:
It insisted I needed a specific update (KB2999266). I downloaded the update from MS and tried installing. 'Your computer does not need this update' insisted Windows.
That's true as the default for Windows 7 updates are cumulative updates that have superseded some of the previous updates (security-only and quality-only instead of roll-up which is cumulative)

IIRC, the work-around is to override several or many times, or, configure the Atmel Studio 7 installer to ignore warnings.

2999226 [sic] is popular here; might try searching for it.

 

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

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

Okay, so I tried one last time, running the installer from the command line (in admin mode) with the /SystemValidationErrorAsWarning flag. And the installer ran, for quite some time, and I was greeted with the message that AS7 had successfully installed. But again it lied. Not a trace of AS7 to be found anywhere on the machine - not even an Atmel directory. So I'm officially giving up.

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

I apologize for the lack of joy ability.

 

If willing to give one more go on Windows 7, there's a follow-on to the released 7.0.1645 in the interim 1652 :

Problem with atmel studio 7 on a new computer.

by wh4t3v34

https://www.avrfreaks.net/forum/problem-atmel-studio-7-new-computer

...

[Atmel Studio 7 extensions server moved, new extensions manager]

https://www.avrfreaks.net/forum/problem-atmel-studio-7-new-computer#comment-2410011

 

Though the following is for JTAGICE3, the sequence may work as JTAGICE3 and Atmel-ICE are both EDBG :

JTAGICE3 firmware upgrade failed - Atmel Studio 7 upgrade

by voiceafx

https://www.avrfreaks.net/forum/jtagice3-firmware-upgrade-failed-atmel-studio-7-upgrade

...

https://www.avrfreaks.net/forum/jtagice3-firmware-upgrade-failed-atmel-studio-7-upgrade#comment-2404021

 

Edit: 2nd thread

 

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

Last Edited: Fri. Apr 27, 2018 - 02:58 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

speculatrix wrote:
So it seems pretty certain that it's a problem with the ICE becoming disconnected, effectively changing identity (from Atmel-ICE to HIDBLDR) and this causing problems with the [VMware] VM.
fyi, HIDBLDR via a USB VBUS cycle may be functional in VirtualBox :

Microchip

Microchip

Atmel Studio

Firmware Upgrade Fails on VirtualBox
http://www.microchip.com/webdoc/GUID-ECD8A826-B1DA-44FC-BE0B-5A53418A47BD/index.html?GUID-EB3C29C4-BD7B-4F5F-B3C7-0AD2026DC48A

The above is dated as it's for an EOL AVRJTAGICE mkII.

IIRC, Atmel-ICE is USB 2.0

 

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

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

I had very similar thing happen & made a posting (unable to find now)...in my case I told the installer not to install the "32 bit processors"  (or some such naming)...then the install finally  proceeded fine.

 

 

 

perhaps see this:

 

I found this workaround (here in the forum):

launch the installer from CLI with the following argument: /SystemValidationErrorAsWarning

When in the dark remember-the future looks brighter than ever.