| commit | e11ce3e6b00f02eba9a15673a54f5345eba8398b | |
| author | David Brownell <dbrownell@users.sourceforge.net> | |
| Sun, 31 Jan 2010 08:26:21 +0000 (31 00:26 -0800) | ||
| committer | David Brownell <dbrownell@users.sourceforge.net> | |
| Sun, 31 Jan 2010 08:26:21 +0000 (31 00:26 -0800) | ||
| tree | 08f1881d9f7d82093af53c404c3ab9bdaf36c3ff | treesnapshot (tar.gz zip) |
| parent | 695666d294e7d572bc5799e0cef4fc384b28c733 | commitdiff |
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>
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>
| src/target/arm_adi_v5.c | diffblobblamehistory |