diff options
| author | Mike Dunn <mikedunn@newsguy.com> | 2010-09-19 15:30:59 -0700 |
|---|---|---|
| committer | Øyvind Harboe <oyvind.harboe@zylin.com> | 2010-09-20 09:21:13 +0200 |
| commit | 103c1f9525436892b610b37d5efc4f2635f5a832 (patch) | |
| tree | 4e8622f91b48062f64769a755249686911711c28 /doc | |
| parent | ebfb2f4f3715f264ae4474c1b2e78812d1625cdc (diff) | |
xscale: some wp detail added to user manual
Hi everyone (again),
Watchpoints on xscale are quirky, so I thought a little explanation in the
user's manual was warranted.
Comments gratefully received.
Last one, Øyvind :-)
Thanks,
Mike
Signed-off-by: Mike Dunn <mikedunn@newsguy.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/openocd.texi | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/openocd.texi b/doc/openocd.texi index bc026b90..230e47c9 100644 --- a/doc/openocd.texi +++ b/doc/openocd.texi @@ -6390,6 +6390,15 @@ the @code{xscale debug_handler} command. The allowed locations for the debug handler are either (0x800 - 0x1fef800) or (0xfe000800 - 0xfffff800). The default value is 0xfe000800. +XScale has resources to support two hardware breakpoints and two +watchpoints. However, the following restrictions on watchpoint +functionality apply: (1) the value and mask arguments to the @code{wp} +command are not supported, (2) the watchpoint length must be a +power of two and not less than four, and can not be greater than the +watchpoint address, and (3) a watchpoint with a length greater than +four consumes all the watchpoint hardware resources. This means that +at any one time, you can have enabled either two watchpoints with a +length of four, or one watchpoint with a length greater than four. These commands are available to XScale based CPUs, which are implementations of the ARMv5TE architecture. |