Post Created date
Xmega256A3U "reset"?
After some more debugging, it starts to look like it has to be HW problem. I think some simultaneous I/Os might cause a notch in the supply voltage(s).   Thanks for the help...
Friday, 23 November 2018 - 18:04
Xmega256A3U "reset"?
Those are messages in disassembly window and memory window. And after break. At the start (break at main) they were available.  
Friday, 23 November 2018 - 11:09
Xmega256A3U "reset"?
Does this explain anything?   09:56:14: [ERROR] Unexpected response (0x70) received from the debugger. Debugger command Memory read failed., ModuleName: TCF (TCF command:...
Friday, 23 November 2018 - 08:09
Xmega256A3U "reset"?
It starts to look like NULL-pointer problem. Something somewhere might be writing in the I/O space.  
Thursday, 22 November 2018 - 18:30
Can't view memory
I doubt it. Rebooted the machine, restarted AtmelStudio, opened the project and started debugging - now in breakpoint at 'main'.
Thursday, 22 November 2018 - 12:19
Can't view memory
I'll try. I just reboot my machine first - just in case...   BTW, could this mean something? When I open a project...   (show output from: Script) Error during...
Thursday, 22 November 2018 - 12:06
Can't view memory
I'm talking about memory window(s) (and disassembly window).  
Thursday, 22 November 2018 - 11:44
Interrupt Service Routine problem (XMrga192A3).
There are exceptions. Like debugger or executive. You use interrupt or break to enter the "supervisor" which may change the processor context, and return to somewhere else....
Wednesday, 21 November 2018 - 18:45
Xmega256A3U "reset"?
Hmm, it was not that, although got it once to a breakpoint within the BADISR-handler. There were also jumps to reset vector that didn't go through a bad ISR. I suspect that some...
Wednesday, 21 November 2018 - 18:33
Xmega256A3U "reset"?
Loads of thanks!   I'm bebugging someone else's code.
Wednesday, 21 November 2018 - 10:32
XMEGA interrupts
A-ha, It doesn't remember anything but the return address. The rest needs to be done in SW.
Saturday, 10 November 2018 - 11:55
XMEGA interrupts
Thanks, but that still doesn't show how the status before interrupt (where to return to) is remembered.   I'm trying to figure out from someone else's code, why the...
Saturday, 10 November 2018 - 10:00