On 04/28/2011 05:49 PM, Eric Cooper wrote:
On Wed, Apr 27, 2011 at 05:33:50PM -0700, Mike Dunn wrote:
On 04/27/2011 03:12 PM, Eric Cooper wrote:
I think it must still be executing the unmodified instruction out of
the i-cache. Shouldn't openocd flush that when it sets a software
breakpoint
On 04/27/2011 09:42 AM, Eric Cooper wrote:
I'm a JTAG newbie and could use some help configuring openocd for use
with a Seagate DockStar, a Marvell Kirkwood (feroceon) board similar
to the Sheevaplug.
The setup mostly works: I can halt, resume, and single-step the
target reliably from the
On 04/27/2011 03:12 PM, Eric Cooper wrote:
I'm using:
GNU gdb (Sourcery G++ Lite 2010q1-188) 7.0.50.20100218-cvs
BTW, be careful using openocd through telnet while gdb is connected. Openocd
assumes exclusive use of one or the other, and does things like clear all
existing breakpoints
On 03/17/2011 01:57 AM, Anders Törnqvist wrote:
1. Why is the debug stepping hopping?
Yes, your guess that it is due to compiler optimization is correct. The kernel
code is optimized aggressively, which makes source level debugging difficult to
impossible unless you debug at the assembly
On 02/25/2011 02:03 PM, Ryan Kuester wrote:
Has anyone had success with OpenOCD and the i.MX35? I thought I
was having success. On my custom hardware based on the Freescale
PDK, things seem fine if I halt while my bootloader (u-boot) is
running; however, Linux gets lost somewhere in early
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 miked...@newsguy.com
---
src/target/xscale.c | 138 ---
src/target
On 10/12/2010 09:57 AM, Nived wrote:
This might be a silly question, but i was wondering what exactly the role of
OpenOCD is in debugging. I mean the internal functioning. I am assuming it
acts like a mediator and just enables debugging on a remote device. But i am
still not clear how this
is superflous, since the infrastruture
code currently checks this before calling target code. Is this being
reconsidered as well? Also, should we stop returning anything other than
ERROR_OK and ERROR_FAIL?
Comments gratefully received.
Thanks,
Mike
Signed-off-by: Mike Dunn miked...@newsguy.com
.
Thanks,
Mike
Signed-off-by: Mike Dunn miked...@newsguy.com
---
src/target/xscale.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/src/target/xscale.c b/src/target/xscale.c
index 77f0f1b..37a2438 100644
--- a/src/target/xscale.c
+++ b/src/target/xscale.c
@@ -2401,6
Hi everyone (again),
Watchpoints on xscale are quirky, so I thought a little explanation in the
user's manual was warranted.
Comments gratefully received.
Last one, Øyvind :-)
Thanks,
Mike
Signed-off-by: Mike Dunn miked...@newsguy.com
---
doc/openocd.texi |9 +
1 files changed, 9
On 09/14/2010 01:45 PM, Drasko DRASKOVIC wrote:
On Tue, Sep 14, 2010 at 10:24 PM, Nived nive...@gmail.com wrote:
Hi,
i am using openocd 0.4.0 to debug an intelmote2 device. I am able to set a
break point and then transfer control to that point. When i do a continue
(c) or a next (n) the
On 09/15/2010 08:47 AM, Drasko DRASKOVIC wrote:
If somebody can confirm this, than we can sign-off cache coherency as
a problem and concentrate on a breakpoint handling.
I sent in a patch a while back to fix this very problem on the xscale; i.e.,
software breakpoints didn't work because of
On 09/15/2010 08:35 AM, Nived wrote:
Mike,
Yes, the intelmote2 is Xscale. Could it be a configuration issue then ?
Perhaps.
I am using the default cfg files pxa270.cfg, crossbow_tech_imote2.cfg and
olimex_arm_usb_tiny_h.cfg.
I'm using the same Olimex i/f as you (finally upgraded from
Hi Øyvind,
On 09/12/2010 12:23 PM, Øyvind Harboe wrote:
A general observation: wouldn't it be better to properly report
the error at the failure site rather than try to interpret errors?
I always assumed that for a project like OpenOCD, which manages and performs
operations on a set of
Hi Øyvind,
Thanks for indulging me. Don't mean to drag this out, but let me see if I
understand...
1) error are reported when they occur (which would put them down in the target
or interface code most of the time, I would guess).
2) return codes are basically considered by the common
received.
Mike
Signed-off-by: Mike Dunn miked...@newsguy.com
---
src/target/xscale.c |9 +
1 files changed, 5 insertions(+), 4 deletions(-)
diff --git a/src/target/xscale.c b/src/target/xscale.c
index 2b8bff1..82b0f34 100644
--- a/src/target/xscale.c
+++ b/src/target/xscale.c
the liberty of adding item 3.
This was thoroughly tested, mindful of the fact that breakpoint management is
somewhat dicey during single-stepping.
Comments and criticisms of course gratefully received.
Mike
Signed-off-by: Mike Dunn miked...@newsguy.com
---
src/target/breakpoints.c |3 +++
src
think
this is imprudent, the patch can be dropped.
Also changed the error code to something more appropriate in two cases where
hardware resources are unavailable.
Comments and criticisms of course gratefully received.
Mike
Signed-off-by: Mike Dunn miked...@newsguy.com
---
src/target/cortex_a8.c
On 09/10/2010 07:02 AM, Teratux wrote:
this is how I configured the linux version:
./configure --prefix=/usr --enable-parport --enable-maintainer-mode
--disable-shared --enable-verbose --enable-parport-ppdev
Am I missing something here? Why does it work on MSWindows and not on Linux ?
Is
register cache as invalid on
debug entry (before the two exceptions are retrieved), thus forcing retrieval
(when requested) from the target across resumptions in execution, and avoiding
the reporting of stale values.
Signed-off-by: Mike Dunn miked...@newsguy.com
---
src/target/xscale.c |5 +
1
On 09/06/2010 09:20 AM, Teratux wrote:
I get the following error:
Open On-Chip Debugger 0.4.0 (2010-08-31-15:56)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
parport port = 0x0
1000 kHz
jtag_nsrst_delay: 100
jtag_ntrst_delay: 100
On 09/02/2010 11:20 AM, Nived wrote:
Hi,
i am trying to configure openocd to work on a PXA271 platform. When i start
the server, i am getting the following error
pen On-Chip Debugger 0.3.1 (2010-01-18-14:21)
$URL$
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
On 09/02/2010 07:30 PM, Nived wrote:
Hi,
i have been trying to write an image onto an intelmote2 using the flash
write_image command. But i keep getting the following error
flash write_image main.bin.out
couldn't open main.bin.out
File not in pwd? Specify the full path to the file.
On 08/04/2010 12:45 AM, Fredrik Hederstierna wrote:
Then openOCD gives error back that FLASH_CONFIG_SIZE is not in
global scope.
It seems like main script file is not running in global scope?
Because if I change variable declaration in main.cfg to explicit set
global namespace, it works!?
, 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 miked...@newsguy.com
On 07/31/2010 06:26 PM, Peter Stuge wrote:
This is a standard FT2232 device. More info at their web page:
http://shop.ngxtechnologies.com/product_info.php?cPath=26products_id=30
Hopefully this is not OT or inappropriate... anyone care to comment on
this product? Done business with them?
On 07/14/2010 08:01 AM, Alex Hornung wrote:
It seems that the first jtag scan works successfully, but subsequent
scans fail miserably. The 'reset' command works (the device *is* reset)
but it throws an error:
JTAG scan chain interrogation failed: all ones.
Check JTAG interface, timings,
Hi all,
I am working with an xscale target. The debug hardware on xscale supports
watchpoints (data breakpoints) with an optional address mask. This very useful
feature allows breaks upon an access across a range of addresses. However,
theOpenOCD wp command does not support this, and to
From: Mike Dunn miked...@newsguy.com
Fix problem with the xscale icache and dcache commands. Both commands were
enabling or disabling the mmu, not the caches
---
Hi David, et.al. I didn't look any further after my earlier patch fixed the
trivial problem with command argument parsing. Turns
Hi folks,
Simple patch that fixes the broken xscale icache and dcache commands. I guess
maybe this broke when the helper functions and macros were changed at some
point.
I'm a relative newbie to the code base. If David or others prefer a more
correct way to fix this, please let me know and
30 matches
Mail list logo
