Atmel studio 7 can't find Atmel ICE

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

Hello, everybody,

 

i can't see/select the Atmel ICE in the Atmel Studio.

 

With the Commandlinetol atfw -l it is displayed.

 

C:\Program Files (x86)\Atmel\Studio\7.0\atbackend>atfw -l
Connected tools:
atmelice J41800017297

 

I am using Windows 7 and Atmel Studio 7

 

If someone can help me, I'm stuck.

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

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

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


Hello,

 

i find the Atmel ICE under the Atmel node,

 

 

but the Studio still don't find it:

 

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

Do you have a process called atbackend.exe running?

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

Yes, atbackend.exe is running.

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

IIRC, 'Atmel-ICE Data Gateway' is one of two (Atmel-ICE is a composite USB device, DGI plus HID for programming and debugging)

Try Atmel Studio 7 - How do I get my Tool to be recognized by Atmel Studio?

May you create joy!

 

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

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

I tried this at #3, without succes.

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

1. After update the Atmel Studio from previous one to 7.0.2389 There is not any EDBG (SAMR34XplainedPro) or ICE into "Device Programming" -> "Tool" drop list. (my system is Microsoft Windows 10 Home)

 

2.  Via Device Manager -> Microchip Tools -> Atmel-ICE Data Gateway (Driver version: 43.0.0.0 1/10/2019)

      Via Device Manager -> Microchip Tools -> EDBG Data Gateway (Driver version 43.0.0.0 1/10/2019)

 

3. Go to Atmel Studio -> Tools -> Options…->Tools -> Tool settings -> Hide unsupported devices” & Make it “False” and click on “OK - does not help.

 

4. The re-installation does not help.

 

using Revo Uninstaller Pro

https://www.revouninstaller.com/revo-uninstaller-free-download/?gclid=Cj0KCQiAs9zSBRC5ARIsAFMtUXFLvfy46DOX3_HAWZW55PNl_fHsX_AF7FC8ugHlBfaxpHh6Xe9VVOEaAkBVEALw_wcB

and

the following command.

wmic product where "vendor like 'Atmel%'" get Name, Version

It should not list 'Atmel Studio IDE 7.0' or 'Atmel Studio Development Environment'.

 

5. But the Start Local Backend Agent maybe clean the situation.

 

The "Start Local Backend Agent" is enabled as default.

I start the Atmel Studio - nothing under "Tool" but the ICE - connected to PC.

I Unchecked the "Start Local Backend Agent" - nothing but the ICE- connected to PC.

I Checked the "Start Local Backend Agent" again - I saw the ICE.

I Connected the EDBG (SAMR34XplainedPro) - the ICE is disappeared from "Tool" and EDBG I do not see also.

 

6.  Are the tools listed in atprogram command line interface?

I navigated to the atbackend folder from the studio installation path in your PC - C:\Program Files (x86)\Atmel\Studio\7.0\atbackend

Opened command window there. (Shortcut: Press Shift+ Ctrl and right click the mouse, you will find an option called “Open command Window here”)

Run the command “atprogram list”.

 

I noticed if the EDBG is connected the error occurs. 

 

 

 

I have not resolved this problem yet.

Please advice.

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

I have the same issue on one computer, but not another.

 

I have two different computers, both running win10 pro.

One is a new Dell latpop, the other an older workstation.

On the dell, I'm having this same problem: upgraded from a working 1931 to 2389, and then the ICE stopped being recognized.

I un-installed 2389, went back to 1931, and that appears to work again (so far).

 

On the workstation, clean install of 2389 works fine (so far).

 

If anyone has any ideas pls post!

pondzone

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

Try disabling the "Data Gateway Interface" in the windows device manager.

(AFAIK, this is the driver that permits I2C, SPI, and maybe GPIO access through the EDBG chip.  It's not actually used for programming or debugging.)

 

(I'm also in the situation where "it works OK on on PC, but not on another" (without disabling the driver.)  It's very weird.)