how do i get atmel-ice driver back?

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

The forum seems to have eaten another post.

 

I seem to have done it again.

In yet another struggle to get AS7 to see my atmel ice,

I seem to have deleted or damaged its driver.

 

How do I get it back?

 

The thing labeled atmel data gateway is gone from the device manager. 

A HID device comes and goes depending I have an a-ice plugged in,

but AS7 doesn't see it and neither does atprogram list.

 

 

 

 

 

 

 

 

 

 

 

International Theophysical Year seems to have been forgotten..
Anyone remember the song Jukebox Band?

Last Edited: Tue. Jan 16, 2018 - 11:56 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Duplicate.  Your other thread is http://www.avrfreaks.net/forum/f...​  You should keep this topic there.

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

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

larryvc wrote:
Duplicate.  Your other thread is http://www.avrfreaks.net/forum/f...​  You should keep this topic there.
Not quite.

This time, I did some damage and want to know how to repair that damage.

Whether said repair would give me access to the device again remains to be seen.

International Theophysical Year seems to have been forgotten..
Anyone remember the song Jukebox Band?

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

skeeve wrote:
In yet another struggle to get AS7 to see my atmel ice,

I seem to have deleted or damaged its driver.

 

How do I get it back?

Deleted the driver, did you delete it manually?  Did you answer yes to a "do you want to remove this driver" prompt while in the process of uninstalling the driver?

 

Since we have no idea what you actually did, could you post a detailed sequence of events that led up to this driver issue.  No need to recap the old thread contents, just focus on what happened this time.

 

What Windows version are you using?  Are you running in a VM?  Are you using a powered USB hub?

 

You may want to clean up post#1

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

Last Edited: Tue. Jan 16, 2018 - 11:53 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

In the Windows 10 device manager, I seem to have clicked on uninstall atmel data gateway.

Not on purpose.

W10 is not a VM.

The HID device that comes and goes when I connect and disconnect the ICE is still there,

but neither AS7 nor atprogram list claims to see the ICE.

 

International Theophysical Year seems to have been forgotten..
Anyone remember the song Jukebox Band?

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

skeeve wrote:
In the Windows 10 device manager, I seem to have clicked on uninstall atmel data gateway.

Did you also select the "Delete the driver software for this device." box in the Uninstall Device pop up?  I bet you did. wink​  You will find the Atmel-ICE Data Gateway in the Device Manager under Other devices.  Now WE need a driver.

 

I'll figure it out and get back to you.

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

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

Okay skeeve, follow the steps below

 

right click on the Atmel-ICE Data Gateway in the Device Manager under Other devices

select update driver

search for drivers in this location

browse to C:\Program Files (x86)\Atmel\Studio\Drivers, select include subfolders

click on Next

 

Done!

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

Last Edited: Wed. Jan 17, 2018 - 06:36 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

For want of anything else at the time, I removed
all things labeled atmel from the device driver,
uninstalled AS7 and installed AS7 again.
Didn't work.

I'm back roughly where I was before.
Atmel-ICE Data Gateway is under Atmel.
USB Input Device is under Human Interface Devices.

 

After the reinstall, I tried to update Atmel-ICE
Data Gatewayin the Device Manager under Atmel.
After I browsed to C:\Program Files (x86)\Atmel\Studio\Drivers
and clicking on next, W10 told me the best drivers were already installed.

 

I have access to three Atmel-ICEs.
One AS7 and atprogram do not see at all.
The other two are seen by both until I try to use them.
Their serial numbers are readable
When trying to use them,
AS7 tells me no JTAG device found,
despite having just read the serial number.

 

I just noticed that the invisible Atmel-ICE is apparently invisible to the device manager:
the Data Gateway stays gone when I plug it in.

 

I'm at a loss.

 

International Theophysical Year seems to have been forgotten..
Anyone remember the song Jukebox Band?

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

A colleague suggested power cycling the *target*.

Much to my surprise, it worked, even on the invisible ICE.

International Theophysical Year seems to have been forgotten..
Anyone remember the song Jukebox Band?

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

skeeve wrote:

A colleague suggested power cycling the *target*.

Much to my surprise, it worked, even on the invisible ICE.

So the Atmel-ICE was connected to a target during the time you were trying to troubleshoot the driver issue and the "here now, gone again" Atmel-ICE?  That was a crucial piece of information that you left out in both threads. The Atmel-ICE most likely would have shown up just fine in the Device Manager had you disconnected the target and only had the Atmel-ICE connected to the PC.  

 

In essence, you were troubleshooting a target caused issue, had we known that we probably could have steered you to that solution much earlier.

 

Glad you got it working.

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

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

larryvc wrote:
skeeve wrote:

A colleague suggested power cycling the *target*.

Much to my surprise, it worked, even on the invisible ICE.

So the Atmel-ICE was connected to a target during the time you were trying to troubleshoot the driver issue and the "here now, gone again" Atmel-ICE?  That was a crucial piece of information that you left out in both threads. The Atmel-ICE most likely would have shown up just fine in the Device Manager had you disconnected the target and only had the Atmel-ICE connected to the PC.

I'd thought that was the norm.

What can one do with an ICE without a target?

That said, I did at least hint at it in the other thread (ATmega2560).

Quote:
In essence, you were troubleshooting a target caused issue, had we known that we probably could have steered you to that solution much earlier.
The problem might have been target-caused, but I am not convinced.

Had I thought in advance to test the hypothesis,

I would have done the power-cycling with the target disconnected.

Quote:
Glad you got it working.

International Theophysical Year seems to have been forgotten..
Anyone remember the song Jukebox Band?

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

Also, just to point out, ONLY the HID part is used by Studio and atprogram... The other parts are used by other programs (Data Gateway is for Data Visualizer).

 

As for why it wasn't seen by Studio, I have nothing to suggest (even weirder that it came back after cycling target....)

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

skeeve wrote:
I'd thought that was the norm.

What can one do with an ICE without a target?

Determine whether or not the target is causing the problem for one.  Disconnecting from the target would only leave the Atmel-ICE in the equation for troubleshooting. 

 

You can connect to the Atmel-ICE from within AS7 without having a target connected by selecting Device Programming, Tool as Atmel-ICE, Device as the device you are using, Interface appropriate for the device you are using, click Apply and then click Tool Information.

 

Doing that and/or looking in the device manager would have confirmed the target as the cause immediately, thus allowing you to focus on the target instead of thinking that Windows 10 or the Atmel-ICE were problematic.

 

Hopefully you wont have to worry about it any longer.

"void transmigratus(void) {transmigratus();} // recursio infinitus" - larryvc

"It's much more practical to rely on the processing powers of the real debugger, i.e. the one between the keyboard and chair." - JW wek3

"When you arise in the morning think of what a privilege it is to be alive: to breathe, to think, to enjoy, to love." -  Marcus Aurelius

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

meolsen wrote:
even weirder that it came back after cycling target....

Could be a Windows "phenomenon". Power cycle (or unplug/re-plug) triggers something special re enumeration?

As of January 15, 2018, Site fix-up work has begun! Now do your part and report any bugs or deficiencies here

No guarantees, but if we don't report problems they won't get much of  a chance to be fixed! Details/discussions at link given just above.

 

"Some questions have no answers."[C Baird] "There comes a point where the spoon-feeding has to stop and the independent thinking has to start." [C Lawson] "There are always ways to disagree, without being disagreeable."[E Weddington] "Words represent concepts. Use the wrong words, communicate the wrong concept." [J Morin] "Persistence only goes so far if you set yourself up for failure." [Kartman]

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

But it's HID... Either it enumerated or it doesn't...

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

Remember folks, AS7 claimed it couldn't see the ICE.

Why would it try to see an AVR through an ICE it thought wasn't there wasn't there?

 

That said, it can't be just a W10 phenomenon.

The AVR is not connected to the USB port.

To get to the USB port, the effect has to travel through the ICE.

International Theophysical Year seems to have been forgotten..
Anyone remember the song Jukebox Band?