diff options
| author | zwelch <zwelch@b42882b7-edfa-0310-969c-e2dbd0fdcd60> | 2009-06-11 21:23:24 +0000 |
|---|---|---|
| committer | zwelch <zwelch@b42882b7-edfa-0310-969c-e2dbd0fdcd60> | 2009-06-11 21:23:24 +0000 |
| commit | b3edde7b7dea4bcc0916c2d23519449f6a318cb5 (patch) | |
| tree | 24e3bd09fded51cbcec3c4f8ad282d07fbf1eab6 /testing/examples/STR710Test/prj | |
| parent | 2e0be4e18b5aec576d429c75ddee736fd0831229 (diff) | |
| download | openocd_libswd-b3edde7b7dea4bcc0916c2d23519449f6a318cb5.tar.gz openocd_libswd-b3edde7b7dea4bcc0916c2d23519449f6a318cb5.tar.bz2 openocd_libswd-b3edde7b7dea4bcc0916c2d23519449f6a318cb5.tar.xz openocd_libswd-b3edde7b7dea4bcc0916c2d23519449f6a318cb5.zip | |
David Brownell <david-b@pacbell.net>:
Update "arm9tdmi vector_catch" command description to highlight both
use cases (display configuration, or first change that config) and
to explain a bit more about what this is: an alternative to using
hardware breakpoint resources.
Note that I tried this on an arm920t, but it didn't work. Set bits,
then examined them and they weren't set. And it didn't seem to act
as if vector triggering was noticed, either.
Also some minor unrelated tweaks: @ignore some unused or don't-use
event names; fix a few typos; tweak chip-specific reset descriptions.
git-svn-id: svn://svn.berlios.de/openocd/trunk@2203 b42882b7-edfa-0310-969c-e2dbd0fdcd60
Diffstat (limited to 'testing/examples/STR710Test/prj')
0 files changed, 0 insertions, 0 deletions