Does Studio 7 Fix "Tool Busy" Issue

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

I'm still running Studio 6.2.   I've always been sorry when I moved to a newer version of Studio.  Seems there's always a hassle getting going again.

 

However, I've been living with a very annoying issue for years and it would be worth moving up if it's been solved.  (Someone from Atmel posted on this forum that it would soon be fixed when I raised the issue a few years ago).

 

If I program a device once using Tools->Device Programming, then close the dialog to make a code change, I can no longer reprogram the device.  The tool is always busy.  I'm forced to exit the application, and restart it.

 

This really slows down the compile/program/test cycle. 

 

I'd like to give a newer Studio version a try if this issue is resolved.

 

Thanks!
 

Last Edited: Fri. Jan 6, 2017 - 08:42 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Have not had a "tool busy" error since changing to AS7. Other annoying little things but not that one.

 

Jim

Jim Wagner Oregon Research Electronics, Consulting Div. Tangent, OR, USA http://www.orelectronics.net

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

davethomaspilot wrote:
f I program a device once using Tools->Device Programming, then close the dialog to make a code change, I can no longer reprogram the device. The tool is always busy. I'm forced to exit the application, and restart it.

THere must be something wrong with your installation.  I am using 6_2 and I have only had this issue once. 

 

What tool are you using to program with?

 

While Studio 4.19 is still the most Rock Solid of the Versions, 6_2 is IMO the next most solid.

 

East Side 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

Quote:
What tool are you using to program with?

 

Two AVRISPs,, an Atmel ICE ,and two AVR dragons.  All act exactly the same.

 

Also, Studio 6.2 was uninstalled and re-installed (not for this issue), but the issue remaisn.

 

The issue was acknowledged by Atmel.   I can dig up the old thread to this forum, if you're interested The only work-around is exit and restart Studio.

 

Have you actually try doing this?  I'm not talking about a debug session.

 

I'll try Studio 7.

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

Here's the recreate--

 

Tools->Device Programming

 

Pick a tool and device.  Hit Apply, and Read Signature/Voltage.

 

Then program memories or fuses.

 

Close the dialog.

 

Try to repeat...

 

Message in tool box is "Atmel ICE busy", (or whatever tool you're using).

 

If you can't repeat this, I'd like to know and I will revisit with Atmel.

 

Thanks!

 

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

I have both Studio 6_2 and Studio 7 on the same PC.  The trick is to uninstall both, restart the machine.  Then install 6_2, restart the machine, then install Studio 7.  Then, depending on which version of Studio you want to use, you need to change the driver in Device Manager.

 

On a side note I have Studio 7 exclusively on one machine and it runs without any issues, and on another machine I have only Studio 6_2, again with no issues.

 

I used to use a dragon, but I gave it away, now I use an Atmel ICE, or AVRispMKII

 

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 Jim, I'll take your advice on doing the installs

 

I had issues with the Dragons getting into and out of debugWire mode reliably.  There are some long threads on this forum from a couple of years ago, if anyone's interested.    

 

The issues went away when I went to the Atmel Ice-- I should have bought the Atmel Ice much earlier.

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

The dragon has always been hit or miss...either it worked for you, or it was a headache. I kinda miss mine.

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

Surely this is about USB drivers then? Not sure if you can install a "later" set of the USB stuff but retain the older 6.2 or whether the AS and USB versions need to be matched as a pair?

 

But the fact that Jim can have both 6.2 and 7 on the same machine suggests that maybe the older 6.2 can use the newer USB drivers the AS7 will have put in place?

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

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

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

clawson wrote:
Surely this is about USB drivers then? Not sure if you can install a "later" set of the USB stuff but retain the older 6.2 or whether the AS and USB versions need to be matched as a pair?

 

It's a sticky at the top of the Studio Forum:

https://www.avrfreaks.net/forum/d...

 

clawson wrote:
But the fact that Jim can have both 6.2 and 7 on the same machine suggests that maybe the older 6.2 can use the newer USB drivers the AS7 will have put in place?

No, I have to shift gears between the two

 

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