AVR32 Studio and Windows 7

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

Hi All

Suddenly AVR32 Studio V2.6 has started working better. It is now possible to debug where previously the system would hang all the time or take several minutes (if one was patient enough to wait) for the debugger to jump over a loop.

What helped? Executing AVR32 Studio V2.6 as administrator causes it work quite diffently. It does need the projects to be imported again (as administrator it starts with an empty environment even when there were several projects imported when opening it as a regular user) but then things started working which had never worked correctly before...

Regards

Mark

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

I'm just guessing maybe the new workspace created.
Thats why you get a clean workspace, all of the Studio settings reseted. When you imported the projects back to the workspace then also converted to the 2.6 version.
could you create a new workspace as a regular user?

What does work differently?
BR
Oneill

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

Oneill

I just tried creating a new workspace and indeed things also work normally. This means that it was not the fact that administrator were being used but that the administrator was getting a fresh workspace.

It is not that easy to explain the problem that it originally had since the debugger would do strange things:
1) I could connect to the debugger and step through the startup code (single stepping) but when I press f8 (to run) it didn't run - it was then not possible to connect to the debugger again and there were timeouts saying that it couldn't interrupt the process.
2) I could get the board to run by pressing the reset button and then pausing the debugger - I could then single step through the code where it happened to be but when pressing f8 again it would hang as in 1)
3) Breakpoints could be set but they were never actually hit (that is, the code certainly ran to them but the debugger didn't stop). Sometimes a breakpoint was however actually hit but it seemed to take the debugger a very long time to get to the line - as if it were single stepping the whole code slowly to get there rather than actually running it (once I had a break point at the end of a subroutien and tried running from the start of it - it seemed to hang as in the other cases but I didn't try stopping the debugger - after a minute or so I say that the debugger suddenly hit the breakpoint...(?)..I couldn't repoduce it though). As I said, difficult to actually say what was going on, but it was always like this and so was not actually usuable as debugger.

These problems no longer exist after switching to a fresh workspace...

Regards

Mark

P.S. I have been comparing ATOLLIC TrueStudio with AVR32 Studio and have made a report here: http://www.utasker.com/forum/ind... - I will update the fact that the administration rights are not necessary but a fresh workspace could cure debugger problems if they are encountered.

P.P.S.
This is the main problem that I am still having: https://www.avrfreaks.net/index.p... any ideas???