From b5a5c69833107e68e7f612702d90870a681a63fb Mon Sep 17 00:00:00 2001 From: TC Wan Date: Mon, 29 Nov 2010 18:38:45 +0800 Subject: fixed comment regarding hardware debugging support --- AT91SAM7S256/Debugger/debug_stub.S | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'AT91SAM7S256') diff --git a/AT91SAM7S256/Debugger/debug_stub.S b/AT91SAM7S256/Debugger/debug_stub.S index 3aa2cb7..f9c7f9a 100644 --- a/AT91SAM7S256/Debugger/debug_stub.S +++ b/AT91SAM7S256/Debugger/debug_stub.S @@ -340,13 +340,15 @@ debug_cmdJumpTable: /* The Debugger Interface can handle a total of (n-1) Breakpoint States and 1 Single Stepping State, * where n is a power of 2. The value of n is given by __breakpoints_num__ defined in the linker file. * - * In addition, a Debugger Stack contains the User Mode Register Stack Frame + SPSR = Bkpt Instr Addr. + * In addition, a Debugger Stack contains the User Mode Register Stack Frame + SPSR + Bkpt Instr Addr. * These are currently stored in the .stack area in RAM, so there is no fixed address * location that is used for this purpose. * * The Breakpoint feature assumes that the program is executed in RAM. It is not possible - * to set breakpoints for programs executed from Flash in the AT91SAM7S which lacks a hardware - * Debug interface. + * to set dynamic breakpoints for programs executed from Flash in the AT91SAM7S which lacks + * instruction breakpointing support in hardware without using JTAG. The only type of breakpoints + * that can be supported in Flash based programs are Static (predefined) breakpoints inserted into + * the code. * * Each Breakpoint State i is a struct comprising the Breakpoint Address + Memory Contents * stored in 8 bytes as: -- cgit v1.2.3