diff options
| author | Mike Dunn <mikedunn@newsguy.com> | 2010-12-02 11:08:28 -0800 |
|---|---|---|
| committer | Øyvind Harboe <oyvind.harboe@zylin.com> | 2010-12-04 09:40:15 +0100 |
| commit | 2e7d51c96a80f7fb2135af8558886e6516ddf661 (patch) | |
| tree | 7130ef79698c8f8b9c9a928f1d54bab2aa20abfe /testing/examples/SAM7X256Test/src | |
| parent | 81790fb56a6db1e5cd9af2b6889071d1dc975052 (diff) | |
| download | openocd_libswd-2e7d51c96a80f7fb2135af8558886e6516ddf661.tar.gz openocd_libswd-2e7d51c96a80f7fb2135af8558886e6516ddf661.tar.bz2 openocd_libswd-2e7d51c96a80f7fb2135af8558886e6516ddf661.tar.xz openocd_libswd-2e7d51c96a80f7fb2135af8558886e6516ddf661.zip | |
xscale: trace buffer remains enabled until explicitly disabled
Hi everyone,
Since a call went out for patches... been sitting on this for months. For some
reason, the xscale trace buffer is automatically disabled as soon as a break
occurs and the trace data is collected. This patch was a result of the
frustration of always re-enabling it, or else hitting a breakpoint and checking
the trace data, only to discover that I forgot to re-enable it before resuming.
Don't see why it should work this way. There is no run-time penalty, AFAIK.
Along the way, I also cleaned up a little by removing the ugly practice of
recording wrap mode by setting the fill count variable to "-1", replacing it
with an enum that records the trace mode.
I've been using this for months. Comments, criticisms gratefully received.
Mike
Signed-off-by: Mike Dunn <mikedunn@newsguy.com>
Diffstat (limited to 'testing/examples/SAM7X256Test/src')
0 files changed, 0 insertions, 0 deletions