diff options
| author | David Brownell <dbrownell@users.sourceforge.net> | 2010-01-31 00:26:21 -0800 |
|---|---|---|
| committer | David Brownell <dbrownell@users.sourceforge.net> | 2010-01-31 00:26:21 -0800 |
| commit | e11ce3e6b00f02eba9a15673a54f5345eba8398b (patch) | |
| tree | 08f1881d9f7d82093af53c404c3ab9bdaf36c3ff /testing/results/v0.4.0-rc1 | |
| parent | 695666d294e7d572bc5799e0cef4fc384b28c733 (diff) | |
| download | openocd_libswd-e11ce3e6b00f02eba9a15673a54f5345eba8398b.tar.gz openocd_libswd-e11ce3e6b00f02eba9a15673a54f5345eba8398b.tar.bz2 openocd_libswd-e11ce3e6b00f02eba9a15673a54f5345eba8398b.tar.xz openocd_libswd-e11ce3e6b00f02eba9a15673a54f5345eba8398b.zip | |
Subject: ADIv5: fix more diagnostics
If the MEM-AP cache is invalid, don't display it; just report that
invalidity as an error. (This bug has been observed with "mdw 0 32"
after just a "reset halt". Some code is being wrongly bypassed...)
If it's valid, display that cache at DEBUG level, not ERROR. Also,
don't assume it's an AHB-AP; it could be another flavor of MEM-AP.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Diffstat (limited to 'testing/results/v0.4.0-rc1')
0 files changed, 0 insertions, 0 deletions