Trouble Writing Memory Block at 0x80780 on Page 1 of Length 0x100: Error 0x00000002/-1153 Error during: Memory, The memory at 0x00080782 continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should still be able to access memory and CPU registers. System state has been altered. It is strongly advised that the processor should be reset before resuming execution, Sequence ID: 66 Error Code: -1153 Error Class: 0x00000002 Trouble Writing Memory Block at 0x80000 on Page 0 of Length 0x781: Error 0x00000002/-1153 Error during: Memory, The memory at 0x00080002 continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should still be able to access memory and CPU registers. System state has been altered. It is strongly advised that the processor should be reset before resuming execution, Sequence ID: 66 Error Code: -1153 Error Class: 0x00000002 Error: Error 0x80000020/-1031 Fatal Error during: Execution, Device driver: Problem with the Emulation Controller. It is recommended to RESET EMULATOR. This will disconnect each target from the emulator. The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target. Sequence ID: 17 Error Code: -1031 Error Class: 0x80000020 Failed to remove the debug state from the target before disconnecting. There may still be breakpoint opcodes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging. Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x1005be: Error 0x0000000A/-2140 Error during: Memory, Break Point, Cannot access memory address at 0x00000800 Sequence ID: 7 Error Code: -2140 Error Class: 0x0000000A Breakpoint Manager: Retrying with a Legacy Hardware breakpoint Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x1005be: Error 0x0000000A/-1153 Error during: Memory, Break Point, The memory at 0x001005BE continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should still be able to access memory and CPU registers. System state has been altered. It is strongly advised that the processor should be reset before resuming execution, Sequence ID: 7 Error Code: -1153 Error Class: 0x0000000A Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x1005be: Error 0x0000000A/-2140 Error during: Memory, Break Point, Cannot access memory address at 0x00000800 Sequence ID: 7 Error Code: -2140 Error Class: 0x0000000A Trouble Removing Breakpoint with the Action "Terminate Program Execution" at 0x1005be: Error 0x00000008/-2044 Error during: Break Point, No breakpoint at 0x001005BE Sequence ID: 8 Error Code: -2044 Error Class: 0x00000008 Trouble Writing Memory Block at 0x100000 on Page 0 of Length 0x779: Error 0x00000002/-1153 Error during: Memory, The memory at 0x00100002 continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should still be able to access memory and CPU registers. System state has been altered. It is strongly advised that the processor should be reset before resuming execution, Sequence ID: 66 Error Code: -1153 Error Class: 0x00000002 Trouble Writing Memory Block at 0x80000 on Page 0 of Length 0x779: Error 0x00000002/-1153 Error during: Memory, The memory at 0x00080002 continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should still be able to access memory and CPU registers. System state has been altered. It is strongly advised that the processor should be reset before resuming execution, Sequence ID: 66 Error Code: -1153 Error Class: 0x00000002 Trouble Writing Memory Block at 0x80000 on Page 0 of Length 0x76f: Error 0x00000002/-1153 Error during: Memory, The memory at 0x00080002 continually indicated it was 'not ready' All memory operations currently in progress were aborted in order to regain control of the processor. This is considered a catastrophic event, but the debugger should still be able to access memory and CPU registers. System state has been altered. It is strongly advised that the processor should be reset before resuming execution, Sequence ID: 66 Error Code: -1153 Error Class: 0x00000002