On 09/24/2010 03:58 PM, Karl Kurbjun wrote: > I have been able to run a similar function on the DM37x without halting > the processor. The DM37x is very similar to the OMAP. One thing I > noticed is that the write did not work when the processor was halted > unless I called "mww phys" to set DBGEN. For some reason just "mww" was > failing even if the MMU was not enabled. > > Have you tried using a physical address write?
Karl, Given your explanation, I tried the following instead of my original patch, and it has the desired effect. Thanks for reminding me that we recently improved the command syntax for 'mww' and friends. I will commit this new patch sometime soon, barring objections. -- Zach Welch CodeSourcery [email protected] (650) 331-3385 x743
>From 3f0a1129db69a9cc11dc2c37c9f0cd3b6fda22c2 Mon Sep 17 00:00:00 2001 From: Zachary T Welch <[email protected]> Date: Fri, 24 Sep 2010 16:13:04 -0700 Subject: [PATCH] Fix omap3_dbginit to write to physical memory. Setting the OMAP3530 DBGEN bit must be done in physical memory, so update omap3_dbginit callback to use the new 'mww phys' command syntax. Signed-off-by: Zachary T Welch <[email protected]> --- tcl/target/omap3530.cfg | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/tcl/target/omap3530.cfg b/tcl/target/omap3530.cfg index 74edd72..ba130a9 100644 --- a/tcl/target/omap3530.cfg +++ b/tcl/target/omap3530.cfg @@ -56,7 +56,7 @@ proc omap3_dbginit {target} { # General Cortex A8 debug initialisation cortex_a8 dbginit # Enable DBGU signal for OMAP353x - $target mww 0x5401d030 0x00002000 + $target mww phys 0x5401d030 0x00002000 } # be absolutely certain the JTAG clock will work with the worst-case -- 1.7.2.2
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
