Solution for boards not recognized in Atmel Studio 6.2

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

For those of you having trouble with boards being recognized in Atmel Studio 6.2, after trying all kinds of stuff with no luck, I found this in a convoluted thread :

From cpirius:
"To fix the issue I copied JLinkARM.dll from:
C:\Program Files (x86)\Atmel\Atmel Studio 6.2\atbackend
TO
C:\Program Files (x86)\Atmel\sam-ba_2.12\drv"

Occam's razor.

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

This one?, also known as the topmost sticky thread in this forum?

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

Wow, wish I had seen that one first, it's a little cleaner than where I found the above, and let's me know that I'm wasting my time until a fix is implemented. Thanks!

I have no issue with my Xplained boards, it's just the Atmel-ICE at this point.

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

I've never used any of the "boards," and just describe what I have to the program.

My atmel-ice works slick. What's yours doing? Perhaps we can sort it for you.

If you don't know my whole story, keep your mouth shut.

If you know my whole story, you're an accomplice. Keep your mouth shut. 

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

Well Windows 8.1 updated today on its own, and now I'm back to nothing working, Xplained boards included. Windows no longer recognizes them as devices, period. I un-installed the AtmelUSB driver, and re-installed. In the week that I've had 8.1, the Xplained boards have been touchy, and the Atmel-ICE enumerated when I did the .dll move described above, then Windows "Updated." Atmel-ICE has never been seen by any software - data visualizer, Studio 6.2, or SAM-BA 2.12 patch 7.

I've lost three days at this point, and rolling back to Windows 7 is not an option, unfortunately because I'm on a new machine (old one's motherboard took a dive).

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

Do you have the update history? (should be able to get somewhere, not sure where though...)

Maybe (hopefully) something stands out if we can have a look at it.

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

Looking at the list I'm fairly certain Windows Offender may have something to do with this and will try to search threads relating to adding permissions/disabling parts of it...

The Updates :
7/28 (KB2919355) - After this update and restart, tools stopped working again.

I believe these may have had something to do with windows asking me to allow the Xplained Boards to access network resources, and what they should connect to:
7/28 Windows Defender Definition (KB2267602) Definition 1.179.1360.0)
7/27 Windows Defender Definition (KB2267602) Definition 1.179.1270.0

7/26 Update for IE 11 (KB2961851) without KB2919355
7/26 x64 (KB2843630)
7/26 x64 (KB2911106)
7/26 Security Update (KB2893294)
7/26 x64 (KB2917929)
7/26 x64 (KB2916036)

I just bought the computer on 7/24, so there are a whole slew of these on 7/24, and no way to list them, other than manually copying them out.

I may try to set up the virtual machine and see how it goes, but I suspect the back end framework will still be blocked by 8.1 (if that's what is actually happening)

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

7/29 : It just installed 27 more updates, most of which are security definitions, and now the Xplained boards appear in studio 6.2 (for now at least).

The Atmel-ICE turns on (center RED LED), and shows up in Device Manager, ATMEL-ICE Data Gateway, but still not as a tool in 6.2.

Tried to update WinDriver for Jungo using Device Manager. Windows successfully updated, but now back to Xplained boards not being recognized.

Rolled back driver to 11.3. Boards still not recognized.

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

Uninstalled all drivers, re-installed, devices back to working. What I have found is that you cannot eject a tool with Studio 6.2 open, or else it will not enumerate again until the computer is restarted.

Still no dice with Atmel-ICE.

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

Quote:

Tried to update WinDriver for Jungo using Device Manager. Windows successfully updated, but now back to Xplained boards not being recognized.

The edbg based tools (xpro, atmel-ice etc) does not use the Jungo driver. It is actually a composite device, and does not need any driver to de debug (hid). The drivers are needed for the Data-Gateway which is another thing entirely made to confuse our users.

Quote:

Uninstalled all drivers, re-installed, devices back to working. What I have found is that you cannot eject a tool with Studio 6.2 open, or else it will not enumerate again until the computer is restarted.

Given that we basically do this numerous times a day, that sounds really weird.

Quote:

Still no dice with Atmel-ICE.

Did you look at the pdf I linked to in the sticky?

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

Ill be looking at it now because after updating to 3.19 for ASF, ATMEL-ice is gone again. Windows has also updated at least once since i last plugged it in, so here we go again with permissions, driver signing, etc...My xplained boards have been running smoothly for the last few months, no longer having the enum problems, but the ice has melted.

 

thanks for the pdf link, I will start there.

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

Has any one found a solution to this problem? 

I, too, have atmel-ice in device manager, but not in ASF.

I have tried Mortens suggestion (atprogram), but get the following error (Win 8.1)

I then found a thread saying to try atbackend, but that throws yet another error  (see both below).

Any ideas?

thx

 

 

C:\Users\Admin\Documents>atprogram -t atmelice info
Could not connect to 127.0.0.1:65004
[ERROR] An unexpected error occurred when executing.
Traceback (most recent call last):
  File "__init__.py", line 50, in run
  File "atmel\avr\cli\commandline.pyc", line 77, in execute_commands
  File "atmel\avr\cli\commandexecutor.pyc", line 52, in execute_commands
  File "atmel\avr\cli\resourcemanager.pyc", line 44, in prepare_resources
  File "atmel\avr\cli\resourcemanager.pyc", line 51, in _prepare_resource
  File "atmel\avr\cli\resourcecontainers.pyc", line 52, in allocate
  File "atmel\avr\cli\backend.pyc", line 143, in connect
  File "tcf\__init__.pyc", line 31, in connect
  File "tcf\util\task.pyc", line 143, in get

Exception: ('TCF task aborted', Exception('Could not connect to 127.0.0.1:65004',))

 

 

C:\Users\Admin\Documents>atbackend
01 11 45 687: osp.core.BundleLoader Failed to start bundle com_atmel_hil_simulator: Cannot load library: C:\Program Files (x86)\Atmel\Atmel Studio 6.2\atbackend
\codeCache\com_atmel_hil_simulator.dll
Some bundles failed to load. Terminating.

C:\Users\Admin\Documents>

 

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

Download the latest Atmel Studio from the Atmel site.  Do a full uninstall of the current Atmel Studio and then install the new version.  The latest version now has upgraded drivers and fixes that were botched before.

"I may make you feel but I can't make you think" - Jethro Tull - Thick As A Brick

"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

Download a program called USBdeview:

http://www.nirsoft.net/utils/usb...

 

run it and delete/uninstall ALL the Atmel devices you see.  Then restart the PC and try plugging in ONE atmel device and see if it enumerates and loads the driver, if not, run the program again and remove the device and then uninstall Studio Completely, restart teh PC and reinstall Studio and then try enumerating a device.

 

Jim

I would rather attempt something great and fail, than attempt nothing and succeed - Fortune Cookie

 

"The critical shortage here is not stuff, but time." - Johan Ekdahl

 

"Step N is required before you can do step N+1!" - ka7ehk

 

"If you want a career with a known path - become an undertaker. Dead people don't sue!" - Kartman

"Why is there a "Highway to Hell" and only a "Stairway to Heaven"? A prediction of the expected traffic load?"  - Lee "theusch"

 

Speak sweetly. It makes your words easier to digest when at a later date you have to eat them ;-)  - Source Unknown

Please Read: Code-of-Conduct

Atmel Studio6.2/AS7, DipTrace, Quartus, MPLAB, RSLogix user

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

Thanks for the suggestions. I did the reinstall as per Larrys suggestion, and that solved it for me.

Atmels download site actually mention an install bug in the 1548 build, and that was precisely the build I had installed.

Build 1563 is working right.

thx,.

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

larryvc wrote:
The latest version now has upgraded drivers and fixes that were botched before.

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

 

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...