diff options
| author | Mike Dunn <mikedunn@newsguy.com> | 2010-08-02 12:50:29 -0700 |
|---|---|---|
| committer | Øyvind Harboe <oyvind.harboe@zylin.com> | 2010-08-02 22:39:48 +0200 |
| commit | 7682877c8ca59226f7131db5fe35253acf117bb4 (patch) | |
| tree | 5db8570a570953a8d28530319119b2b92c379dc0 /src/target/ecos | |
| parent | bfa34f88f8b77596d6f70be446708a3f5a604e9b (diff) | |
| download | openocd_libswd-7682877c8ca59226f7131db5fe35253acf117bb4.tar.gz openocd_libswd-7682877c8ca59226f7131db5fe35253acf117bb4.tar.bz2 openocd_libswd-7682877c8ca59226f7131db5fe35253acf117bb4.tar.xz openocd_libswd-7682877c8ca59226f7131db5fe35253acf117bb4.zip | |
xscale documentation: vector table handling
Hi everyone. I noticed some incorrect information in the user manual
regarding how the vector table is handled on the xscale, so for your
consideration, here's a short patch that corrects it, and adds a
little more detail I thought might be helpful.
The documentation states that OpenOCD does not attempt to synchronize
the vector tables in memory with those stored in the "mini instruction
cache". In fact, on each resume it does copy from memory to the cache
all entries in the high and low tables that were not previously
defined using the 'xscale vector_table' command. (In
src/target/xscale.c, see xscale_update_vectors(), which is invoked by
xscale_resume().) I take advantage of this during Linux boot-up. The
extra detail describes in general terms how I do this.
Corrections, comments are of course gratefully received.
Thanks,
Mike
Signed-off-by: Mike Dunn <mikedunn@newsguy.com>
Diffstat (limited to 'src/target/ecos')
0 files changed, 0 insertions, 0 deletions