I get the following in the CCS Console when I set an int to 0 while JTAG'd into my DSP. :/
C55xx_1: Trouble Reading Memory Block at 0x1a0eb on Page 1 of Length 0x1: Error 0x80000002/-1143 Fatal Error during: Memory, The memory at 0x000341D4 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,
C55xx_1: Trouble Reading Memory Block at 0x1a29f on Page 1 of Length 0x1: Error 0x80000002/-1143 Fatal Error during: Memory, The memory at 0x0003453C 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,
C55xx_1: Trouble Reading Memory Block at 0x1a29c on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory, The memory at 0x00034538 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,
C55xx_1: Trouble Reading Memory Block at 0x1a29c on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory, The memory at 0x00034538 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,
C55xx_1: Trouble Reading Memory Block at 0x1a29c on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory, The memory at 0x00034538 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,
C55xx_1: Trouble Reading Memory Block at 0x21620 on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory, The memory at 0x00042C40 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,
C55xx_1: Trouble Reading Memory Block at 0x1a29c on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory, The memory at 0x00034538 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,
C55xx_1: Trouble Reading Memory Block at 0x1a29c on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory, The memory at 0x00034538 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,
C55xx_1: Trouble Reading Memory Block at 0x1a29c on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory, The memory at 0x00034538 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,
C55xx_1: Trouble Reading Memory Block at 0x1a29c on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory, The memory at 0x00034538 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,
C55xx_1: Trouble Reading Memory Block at 0x1a29c on Page 1 of Length 0x2: Error 0x80000002/-1143 Fatal Error during: Memory, The memory at 0x00034538 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,
