atmel studio 6 programmer [busy]?

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

I just started using atmel studio 6, I've got an avrisp programmer and after every time I program a device, next time I open the device programming box it says AVRISP MKII [busy] and I can go no further - !? what does this mean, and how do I stop it from happening? I am having to close and re-open the program every time I want to program the chip....

 

thanks!

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

Of course you have to close the Programmer when you have finished with it.

AS6 will not do anything else when you have the Programmer window open.

 

Of course,  you could use a third-party Windows program and just change context.

However,   AS6 would not be able to "upload code without debugging" because your other Windows App is using it.

 

David.

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

how do i close the programmer? do you mean the programmer window? I have closed the programmer window, and when I re-open it it says the programmer is busy. 

if you mean I have to close the programmer, how do i do that? I never had any problems doing this in avrstudio 4 - not knowing much about thsi stuff im a bit confused

 

thanks

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

At the bottom right hand corner, you will see a [Close] button.

 

Are you sure that AS6 has not got several "waiting for device" windows?

This laptop is not super fast.    So AS6 is forever stopping.

 

Heaven knows how a student in the third world manages AS6 with an 'old' XP PC.

Or even worse,  an 'old' laptop.

 

David.

Last Edited: Mon. Dec 1, 2014 - 10:25 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

hi, perhaps I am not making myself clear - the problem is that after I close the window and then re-open it (having programmed the device), the programmer is listed as busy and wont let me do anything

im not sure what you mean about the waiting for device windows, but my computer is plenty fast. 

 

thanks

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

just thought id give this a bump - still not found any way round this

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

My piece of voodoo to get around this, though I am using the STK-600, but have the same problem. Turn off the STK or unplug it. Close Atmel Studio. Open Atmel Studio. Turn on/plug in. This seems to take it out of busy quite reliably. It is a little bit of a PITA. I find it only goes busy generally when something goes wrong, like I try to do a ISP program when the jumpers are not correct, that kind of thing.

 

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

If you select the "Device Programmer" from the Tools menu in AS6,   you should be able to :

Connect to AVRISP-2,  Connect to AVR,  Read / Write memory / fuses,   Close

 

You should be able to do the same sequence as many times as you like while in AS6.

 

Since you say that you have a fast PC,   everything should work smoothly.

 

In practice,   you seldom use the "Device Programmer".    When developing programs,  you Build,  then "Start without debugging"

 

I don't own a AVRISP-2.    I do have an STK500 and a Dragon.    They behave 'reasonably' on a fast desktop PC.

Most of the time,   I will Build, then upload to an avrdude programmer.    This means that I have to click on the Tools menu for the specific "avrdude combination".     (generally a USBASP or a bootloader)

 

David.

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

Ok, that isn't what happens on mine. I suppose I'll have to put up with it til I find the reason for it

 

thanks,

Philip

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

Hi, Philip

 

Did you find a solution to your "busy" programmer problem?  I'm having the same issue with the Atmel ICE in AS6.2.  The only solution I've found so far is to disconnect / reconnect the USB lead to the Atmel ICE.

 

Ironically, I don't have the same problem using an AVRISP mkII with avrdude set up as an external tool.

 

I wonder whether it's another AS6.2 thing.  AS6.1 seemed much more stable than the latest release which has wobbled in several areas since I moved over a month ago.  I would go back to 6.1 but it doesn't support the new ICE.

 

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

no, i didn't unfortunately. It is driving me round the bend :( but yes, disconnecting the USB lead does work.

I used to use avr studio 4 and by comparison AS6 seems quite problematic, though i am no expert. 

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

I also have a similar problem....When I use the green arrow to "START WITHOUT DEBUGGING"  ....I can make changes to code and the repeat the process, fine.  

 

However if I want to  go into  "Device Programming" the Dragon is shown as still "[busy]"  (from the "START WITHOUT DEBUGGING" action)  so in order to connect/program I have to shut down Studio 6 and restart. 

 

Disconnecting the USB does not always work, although I think it does SOMETIMES, restarting Studio 6 ALWAYS works.

 

[UPDATE, FIXED?] :  So far an upgrade to  Atmel Studio 6 (Version: 6.2.1548 - Service Pack 2)  seems to have fixed it, will update if problem recurs .

 

[UPDATE,Not fixed.] Problem came back efter several "cycles" switching between   "Device Programming"  & "START WITHOUT DEBUGGING" actions.

Last Edited: Mon. Feb 23, 2015 - 02:36 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Same problem with AVR DRAGON AS6.2 sp2. In my case restarting AS and disconnecting Dragon from laptop not always works.

 

I've found workaround in one of the treads at this forum: open your project -> start debugging [F5] -> from dropdown Debug menu -> Choose Disable debugWire and close  -> choose ISP mode in Tool menu

It should bring the Dragon to live from BUSY .

 

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

This is the same problem I am having running the simulator or using the STK500. After stopping the simulator it will only restart where it left off even if I changed the code and recompiled. Reset does not work, nor does closing the file and reopening. I have to exit Studio to run another simulation. The STK500 always shows [Busy] if I use it once. It does matter if it is turned off or disconnected I have to exit Studio to use it again. Sometimes when I exit Studio I get a pop-up asking if I want to stop the debugger even though I already stopped it.

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

Similar issues - Atmel Studio 6.2, with AVRISP mkII connected by USB.

 

Debug - Start Without Debugging - just gives error "Upload requires a serial port or programmer. Upload cancelled"  No problem, I just bring up Tools - Device Programming and the "Device Programming" dialog is displayed.  Tool (the AVRISP mkII that is connected), Device and Interface are correct, and press "Apply" - and everything is good.  I don't do anything else with the programmer and then press Close.  The "Device Programming" dialog goes away.

 

Select Tools - Device Programming again and display the "Device Programming" dialog.  The correct tool is still listed in Tool dropdown - but it is now "Busy" and the only way to use it again is to either restart Atmel Studio or disconnect/reconnect USB port.

 

Any kind of solution would be appreciated.  Thanks.

 

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

Hi !

 

I have also the same problem here, AS 6.2.1563 - SP2, latest USB drivers from the Gallery installed and with a Dragon. I'm only using the programming dialog (i.e. no debug). But I can only program my device as long as I don't close the programming dialog. As soon as I close it, the dragon appears as busy. Sometimes a simple unplug/replug of the dragon suffice, but sometimes I also have to quit AS.

 

I hadn't the problem before. Can someone from Atmel bring us some light on this ? Is it something you are aware of and working on it ? Are we only a few people with the problem ?

 

Many thanks !

Have a nice day,
Kraal

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

I have also the same problem at long time with ATMEL STUDIO 6.2 (:

 

My AVRISP MK2 is in ATMEL STUDIO 6.2 often busy. I have try new USB drivers from ATMEL website but to no avail. I have try ATMEL STUDIO 6.2 reinstalled but to no avail.

I reconnect the AVRISP MK2 from USB and then it works a short time.

 

I flash an ATxmega128 and ATmega328 with the AVRISP MK2 in ATMEL STUDIO.

 

I sent an email to ATMEL. My system data see below.

 

Greetings from Germany. Rolf

Windows 10 Home 64Bit, ASUS M4A89GTD-PRO/USB3, AMD Phenom II X6 1055T, Ram 2x 4GB, SSD Samsung EVO840 250GB, SATA HD 2.0TB, NVIDIA GeForce GTX 750

Last Edited: Thu. May 28, 2015 - 09:41 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

... same story in my just implemented DRAGON + STK500 + AVR Studio 6.2.

 

Both became busy after a session of doing something and no way to release them.

 

who hasn't this behaviour should explain how he deals with this matter. I am seeing it is a trouble for a lot of people.

 

Ciao.

Mario

 

 

oiram revenac

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

Hallo Mario

 

I have written the ATMEL support but received no response.

 

I do it again and send all post from here to atmel. I hope it helps.

 

If I get an answer I write here.

 

Greetings from germany. Rolf

Windows 10 Home 64Bit, ASUS M4A89GTD-PRO/USB3, AMD Phenom II X6 1055T, Ram 2x 4GB, SSD Samsung EVO840 250GB, SATA HD 2.0TB, NVIDIA GeForce GTX 750

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

http://www.avrfreaks.net/forum/c...

msg #11 from dandumit dated Posted : Wed. Jan 7, 2015 - 10:02 PM

 

This is the whole msg

I forgot to tell you that I have received an answer to case where I have been told that

"This problem has been identified and reported as a bug in Atmel Studio 6.2. This issue might be fixed by our development team in the upcoming Atmel Studio releases. Unfortunately as of now there is no work around other than restarting the Atmel studio. We are sorry for the inconvenience."

 

Unbelievable  ! 

Why I should buy original products ?

This guy didn't had at least curiosity to read this thread ...

End of original message


 

This is my feeling too:

Unbelievable  ! 

Why I should buy original products ?

This guy didn't had at least curiosity to read this thread ...

 

I am coming from STM8s platform and only God knows why I have accepted to migrate to Atmel.

Always in time to comeback and sale all the Atmel toys.

 

90% it is a problem of the USB driver. I don't understand why a so big company doesn't engage a young Indian Engeneer and solve the problem releasing a patch.

Why lose the face for a problem becoming so popular.

 

I hope this message can stress a little somebody inside Atmel.

Probably should help the email address of the PR of Atmel company ...

PR can move everything, engeneer - like me - hasn't the sensibility to understand the damage a thing like this can do.

 

cheers!

 

Mario

 

 

oiram revenac

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

Did anyone find a solution to this? I've been having the same problem ever since I upgraded from Atmel Studio 6.0 (which didn't have the problem) to 6.2. It used to be the case that I could get round the problem by plugging the AVRISP into a different USB port, but that no longer works. I am running under Windows 7 64-bit.

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

Yes, this is a serious time waster!!

 

On the project I am working on now, I am making many small edits and compiles, and need to blank the chip each time (by opening the programming dialog).

If I make 50 edits, this means 50 close and reopens for AS6! Ack!!!

 

I have version 6.2.1563 SP2

 

Hope this one is near the top of the fixes list.

 

Brad

I Like to Build Bikes : http://www.AtomicZombie.com

I Like to Hack Stuff : http://www.LucidScience.com

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

I was having the same problem with Ver 6.2, until I noticed the Studio was showing device type ATmega644 when I was actually using ATmega644P. I went to Project>>Properties... Device, and set the device type to exactly the same type as I was using. It seemed there was a problem with the device signature not matching.

 

If I select "Start without debugging", and have the correct device type setting, the build and download works repeatedly, (without even touching the Device Programming button).

 

 

Regards, David C

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

Yeah, that's not it.

Everything is set correctly, and the problem happens about 90% after the first programming cycle with the AVRISP.

The only way out of the vortex is to close Studio and reload your project.

To be honest, if I had another platform, I would switch for this project, as this is HIGHLY annoying.

 

Here is what happens, and why this is ruining my very limited free time....

 

1) Open Studio, power up my board, make a small code change, and then press "Start Without Debugging".

2) The AVRISP loads the XMega, and I then look on the VGA monitor connected to my project to see what happened.

3) The code is loaded without any error within a few seconds to the XMega-384C3.

3) I now have to click on the "Device Programing" button to blank the XMega so I can adjust wires on my project.

4) I click on the "Device Programing" button and then get kicked in the face by this...

 

 

5) The only way out is to save the project, close Studio, then reopen the project.

6) After waiting for the project to load again, I can now access the tool...

 

 

 

Now this may not seem like a big deal, but in this case, I have to do this jig over and over as I work on this project.

Today I have some limited free time, and will probably make 100+ changes to my board as I work on some of the logic.

Consider the lost 60 seconds for each time I have to dance around this bug, and my day off is not so productive.

 

Others have reported this bug for some time, so I feel i must publicly spank the Atmel developers...

 

1) Obviously you are aware of this issue, as I have seen it reported in other threads.

2) If I had the source code, I could probably fix this bug, and I am not even a great programmer!

3) With your paid team, there is no reason why you could not fix it very easily.

4) This issue is a HUGE turn-off. Do you think these things do NOT affect future sales?

 

So listen up folks...

 

Unless your development team consists of 2 part time students working from their parent's basement,

there is NO EXCUSE for a company of your size to allow a known bug like this to persist for even a few days.

I am a very patient dude, and yet here I am flailing you on a public forum. Others may not even bother.

 

Imagine what a less patient person who may influence some future volume purchases might do?

Please allot the extra day of development time to your team to fix this ultra annoying bug.

Even if you have to pay overtime, the costs to your company will be extremely insignificant.

 

If you cannot afford the expense, let me know and I will start a crowd funding campaign to help.

Let's say 2 decent programmers for 2 days of work... will $2000.00 cover it?

 

Ok, enough ranting, I am off to relax and spend time on my project, most of which will go to reloading Studio.

 

Atmel -> please print the above email and bring it to your next production / QC meeting!

 

Brad

 

 

 

I Like to Build Bikes : http://www.AtomicZombie.com

I Like to Hack Stuff : http://www.LucidScience.com

Last Edited: Sun. Aug 16, 2015 - 04:26 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Have you tried the 7.0 Beta? As far as I know this issue has been resolved there.

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

Had no idea such a thing existed.

I get the Atmel newsletters, and often check here for updates...

 

http://www.atmel.com/tools/atmel...

 

How would I join the secret society to gain access to the beta release?

I will certainly give it a try and report back if I can find it.

 

*** Update ***

Poking around, I found it in this forum.

Will report back tonight if the time-sucking AVRISP restart problem is fixed.

It will be nice to get back to fighting my prototype rather than the toolchain!

 

 

Brad

 

meolsen wrote:

Have you tried the 7.0 Beta? As far as I know this issue has been resolved there.

I Like to Build Bikes : http://www.AtomicZombie.com

I Like to Hack Stuff : http://www.LucidScience.com

Last Edited: Mon. Aug 17, 2015 - 01:30 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

How would I join the secret society to gain access to the beta release?

You spend more time here instead of elsewhere!  wink

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Indeed!

I should be flogged for my recent affair with that other 8 bit CPU!

 

After I try Studio7 tonight and it does not force a restart after every chip load, I may come crawling home.

To be honest, I would remain an AVR fanboy, even if I had to hand toggle every bit into the damn chip!

 

Brad

I Like to Build Bikes : http://www.AtomicZombie.com

I Like to Hack Stuff : http://www.LucidScience.com

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

Studio 7 fixed this issue for me! This is great.

Another quirk that is now fixed is the blank output window after build.

Normally, you have to build twice to see the data in the window.

 

Last Sunday, I had to restart Studio 6 a total of 34 times (yes, I counted).

This cut almost 45 minutes from the 6 hours I had to work on my project.

 

So yes, this fix is very welcome.

Please post the name of the programmer that made this happen so I can write a recommendation letter for a well deserved raise!

 

Brad

 

I Like to Build Bikes : http://www.AtomicZombie.com

I Like to Hack Stuff : http://www.LucidScience.com

Last Edited: Tue. Aug 18, 2015 - 12:30 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi all,

I had this problem too when using ATmel Studio 6.2.

At first I thought is my MKII, which Atmel had discon.

 

Until yesterday, I was doing some setting at the Tools->options->Tools.

Now I had to select the Tool everytime I do the programming.

 

I had no problem with AVR Studio 5.0.

 

I use ATmel Studio 6.2, mostly for the production.

 

ChawCS 

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

Just to add that I'm having exactly the same issues with the disconnecting, but worse. I also get BSODs only on the second extended desktop monitor, the primary monitor seems OK, I'm using Windows 7 Professional 64bit SP1. This happens with V1.18 of AVRISP code which is needed for AVRStudio V7. I've downgraded to AVRISP V1.17 and back to AVRStudio V6.2 and the BSODs seem to have gone (at least I haven't had one yet but it's only been a few hours since I did that). I still get the seriously annoying disconnects though even with V7. This has not been fixed, it appears to be a USB driver related issue and the second monitor dependence implies some kind of driver clash or interrupt problem.

 

The way I deal with this debacle currently is to open a second instance of AVRStudio, open the device programmer, connect the AVRISP and leave it open and connected even after programming. This is a little annoying as the device programmer is modal and it can't be minimized, but you can still open other windows on top of it.

 

I'll re-iterate though, I do not believe this disconnect issue has been fixed with V7 of AVRStudio, and the BSODs are very worrying and may well be related.

 

Mark.

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

Yet another person having programmer problems with 6.2. I repeatedly get 'busy' status after a programming attempt. I have been having this issue with programmers ever since version 4. I have used XP, Win10, and Vista pro as platforms, and Atmel AVR-ISP MK2,  Dragon, and the Olimex AVR_ISP MK2.  Like others I must exit and restart Studio (a 4 minute time sink repeated many times in the course of debugging) in order to do a new programming session. And yes, you must carefully match the device, and if using SPI make sure the clock is not too fast. This situation is akin to giving someone a free Ferrari, with the proviso that you will need to remove all 12 spark plugs and prime the cylinders, after which it may or may not start. Is there any workaround? Has Studio7 reliably fixed this, and is it a stable release? Is there any way to program the 8 bitters (AVR, TINY  XMEGA) that will bypass these problems? I am hoping that the Mchip guys have fixed this.

Harry