Atmel Studio 7 Oddities

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

Hi all,

 

I am starting development with the SAMD21 dev board with Atmel Studio and I've noticed a few oddities that I hope you guys could help me with. I've googled these issues and have found various solutions but most seem to be supposivly fixed with an update to Atmel Studio(that was released more than a year ago) or just restarting Atmel Studio. 

 

Some Specs:

  • Dell Precision Laptop
  • i7-4702HQ
  • 16GB RAM
  • Windows 10
  • Atmel Studio V7.0.1931

 

1. When debugging, breakpoints don't get applied where I select. For example with the following code, I can't break on "x = i;" but if I restart Atmel Studio it lets me do it:

uint8 x = 0; i=0;
for(i=0;i<5;i++)
{
    x = i;
}

2. When debugging, breakpoints sometimes are just a red circle(not filled in) with the message "The breakpoint will not currently be hit. Unable to set requested breakpoint on target.". If I restart Atmel Studio this goes away.

 

3. The issue that I constantly get is the message "Waiting for an operation complete". I've attached the whole pop-up image. This seems to happen whether I have my SAMD21 connected or not. On a fresh PC boot this doesn't happen for a while but once it happens once, it keeps happening. I've read a few fixes to this and tried deleting the .vs folder but doesn't seem to help. The message says that I can adjust the timeout but the current timeout is 1000 seconds. The message pops up in about 30 seconds when starting a debug session so i'm not sure if it actually hitting the timeout.

 

I encounter this message at several different times:

  • When starting a debugging session
  • When debugging: There are times that I am debugging and the MCU is essentially sitting in a while loop waiting for some button until. If i leave it running > 5 min it pulls the "Waiting message"
  • When opening a solution
  • When starting Atmel Studio: This pops up several times when attempting to start Atmel Studio. AS opens to blank landing page with no solution loaded. I also getting the below warning message:

15:17:27: [WARNING] TCF command: Tool:getAttachedTools timed out
15:18:34: [WARNING] Reply to TCF command: Tool:getAttachedTools has arrived after the command has timed out
15:19:10: [WARNING] TCF command: Tool:setupTool timed out
15:19:30: [WARNING] Reply to TCF command: Tool:setupTool has arrived after the command has timed out
15:20:04: [WARNING] TCF command: Tool:setupTool timed out
15:20:24: [WARNING] Reply to TCF command: Tool:setupTool has arrived after the command has timed out

 

Any help would be great, Thanks! 

Paul

 

Attachment(s): 

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

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...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi awneil,

 

Thanks for the links to the posts about compiler optimization(Obviously a topic that is overly posted, sorry to contribute to that). I just finished going through them and I found that these two posts were particularly helpful. 

 

 

and to cherry pick a comment by you from "The shortcuts taken by optimized code may occasionally (sic?) be surprising"

And yet there is still a steady flow of people being "surprised" by the effects of optimization!

 

You would have thought that teachers, textbooks, tutorials, etc would be explaining this to their students/readers by now ...

Yes! I am definitely in that surprised group. My background is mostly in the HW realm with a handful of SW and Embedded classes thrown in. Large parts of these were directed knowledge of either learning a specific languages or knowing how to manipulate SW to control HW. Compilers, among other things, were something that were mostly glazed over. I have worked on various embedded projects but have built myself into a trap by using but not fully understanding the things in the background. A lot of things behind an IDE(Debugger, Compiler, Linker, Toolchains,Makefiles) are still largely a black-box for me that I plan to remedy in the future by taking advantage of some continued education programs at work.

 

Any thoughts on the 3rd topic about "Waiting for an operation complete"?

Things I've searched for: 

 

Thanks again.

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

psantos wrote:
The issue that I constantly get is the message "Waiting for an operation complete"

 

I have a continuous running battle with that one. When I was at Win10 1803, it was hopeless. Getting back to 1709 has helped, but not eliminated it. It happens whether I have hardware connected or not. As you say, once it starts happening, it gets brutal. I end up rebooting *a lot*. It makes something that should proceed briskly very very slow sometimes. And seems to be the phase of the moon as to when it will go astray. I disabled every security feature around (including defender, etc), and that din't help. Right now I just plod along praying sometime someone who develops AS7 will suffer from it and fix it.

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

Yeah, it seems like just restarting the computer is the best bet for now. Here are some of the situations that I've noticed it happens and ways to improve/ keep message from happening:

 

  • I currently use a USB dock for my laptop with a SAMD21 connected to the dock. If I have Atmel Studio open when I undock->dock when I have any Atmel Devices attached, AS7 doesn't like it. So before I undock, I make sure I close my debugging session and close AS7. 
  • I've been developing two sets of code with two SAMD21 boards and I switch boards when debugging/programming. In addition to AS7 not refreshing and seeing the new board, it incurs the pop up of the "Waiting for an operation to complete". So, I've made sure to close out a debugging session and AS7 before I switch.
    • Better solution when using two boards: 
      • You can have two boards connected at the same time. For me,  I have two projects(Project A, Project B). Opened each project's properties(Menu->Project->Properties). Went to tool and selected a separate debugger/programmer for each project. When I want to debug a specific project I just go to the solution explorer and right click the desired project and click "Set as Startup Project". Now when debug is run, it will debug what ever project is set as the startup project. 
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Apologies for bringing back an old thread, but I am experiencing the same "Waiting for Operation to Complete" issue and I was wondering if there have been any updates or solutions to this problem.

Thanks!

Last Edited: Wed. Aug 21, 2019 - 10:46 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

After recent googling have found a pseudo solution at another AVRfeaks post  https://www.avrfreaks.net/comment/2043856#comment-2043856.

 

Looks like the Corsair gaming keyboards are an issue. Without my keyboard connected, I don't see any freezing issues with Atmel Studio 7. 

 

Ticket is out to Microchip to see if they have a resolution at all. Will update when get a reasonable reply.

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

Thank you so much for linking me to this!  I too have a Corsair gaming keyboard.  I am looking forward to hearing what Microchip has to say!