Atmel Studio 6.2 beta on Win 8.1
SAMR21 Xplained-pro.
Code (says it) downloads OK, but then this warning pops up.
This is unhelpful - it doesn't tell me where to find the "backend log"!
Where would it be?
Atmel Studio 6.2 beta on Win 8.1
SAMR21 Xplained-pro.
Code (says it) downloads OK, but then this warning pops up.
This is unhelpful - it doesn't tell me where to find the "backend log"!
Where would it be?
Deleting all breakpoints seems to have cleared the error (for now) - but still none the wiser as to where to find this "backend log"!
Backend log is at % appdata% / Atmel/..../ApplicationStatus.log
Only thing I can think of that could cause us to not be able to resume the device would be if we lost contact with the DAP in the core. I do however not really see any reason why this should happen, and why it 'fixes' itself by removing the breakpoints.
Thanks for that.
If it recurs, perhaps the ApplicationStatus.log will tell something useful - now that I know where to find it!
It should :) Also, the diagnostic logging option in Tools|Options|Tools will dump the raw DAP commands into the log as well, so it will be easy to see why we are unable to resume at least. (off by default, as the raw commands are plentiful and big)
The exact same thing happened to me today when I was migrating an XMEGA256A3U project from Atmel Studio 6.2.1563 to 7.0.1417. And like https://community.atmel.com/users/awneil mentioned, deleting the breakpoints seem to make the problem go away. Thank you "awneil" for posting!
The exact same thing happened to me today ...
You mean where they told you to examine your back end? ;) An example of a back-end log:
Backend log is at % appdata% / Atmel/..../ApplicationStatus.log
Suggestion for future version of Studio: Show this filespec in the message box - with the %appdata% expanded.
If you want to make your users really happy when encountering this problem, add a button "Open file location" to the message box (starts a Windows explorer with the file selected. Cf. right-clicking a Windows Explorer search result, or a finished download in e.g. Google Chrome).
EDIT: Regardless of if the subject text was truncated by the OP or the forum software, I loved it! Lee's Back End Log was also hilarious!
Lee's Back End Log was also hilarious!
Thanks; it was the most innocuous I could come up with. I could NOT pass on saying something about back-end examination and what logs might be nearby.
sorry still not getting where it is backend file