Re: [Openocd-development] commit 81aec6be "list number of HW breakpoints/watchpoints"

On Wednesday 09 December 2009, Nicolas Pitre wrote: > > > This is wrong for Feroceon and Dragonite which have only one of them.   > > > In that case arm7_9->wp_available_max is initialized to 1 in the > > > target_create method, but the above message is still wrong and > > > misleading. The appe

Re: [Openocd-development] imx31 breakpoints

On Thursday 21 January 2010, Edgar Grimberg wrote: > >> and want to see what a bisection that skips known-incomplete stuff > >> will turn up. > > 5eb893ec41c8c6cf6499558b6fed826b65e18a16 is first bad commit > commit 5eb893ec41c8c6cf6499558b6fed826b65e18a16 > Author: David Brownell > Date: Tue N

Re: [Openocd-development] Freescale iMX35 "Target not examined yet"

On Tuesday 19 January 2010, Alexei Babich wrote: > [imp...@kb33 openocd]$ src/openocd -f /home/impatt/openocd.cfg > Open On-Chip Debugger 0.4.0-rc1-dev-00118-gdab9297-dirty (2010-01-20-10:20) > For bug reports, read > http://openocd.berlios.de/doc/doxygen/bugs.html > trst_and_srst separate

[Openocd-development] [PATCH] telnet: fix strage blank spaces at beginning of telnet lines

Sometimes we saw two strange blank spaces at the beginning of the telnet lines. progress ogress > This patch fixes this problem: progress progress > The code changes are *reasonably* clean, but perhaps it could be made a bit more elegant, but I didn't want to change things after I finished di

Re: [Openocd-development] printing reason why GDB halts

This is annoyingly verbose in when connected to a target that is failing poll... otherwise it's ok. This is really a message that should be displayed in GDB only, but there is no mechanism today to check if there is a gdb session associated... Perhaps adding a "reason" to the event reporting mecha

Re: [Openocd-development] [PATCH 2/2] target: Fixed format problem for mdh

merged. Thanks! -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@li

Re: [Openocd-development] [PATCH] interface: Changed parport address to LPT1

merged. Thanks! -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@l

[Openocd-development] flash programming clock, and how it really matters for lpc2000, although things may appear to just work

Hello! In hope noone will deal with this issue again :-) I've never paid attention to clock parameter of "flash bank", since it just worked... well, with some odd problems, like code jumping to random places, read only data being wrong etc - and that happened RARELY. So I began suspecting a flas

[Openocd-development] [PATCH 2/2] target: Fixed format problem for mdh

Fixed format problem for mdh. It needs to display 4 chars. Signed-off-by: Edgar Grimberg --- src/target/target.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/target/target.c b/src/target/target.c index c56265c..ff5aef3 100644 --- a/src/target/target.c +++ b/src/t

[Openocd-development] [PATCH] interface: Changed parport address to LPT1

Changed the parport address to LPT1, since it's the most obvious default value. Signed-off-by: Edgar Grimberg --- tcl/interface/parport.cfg |8 +++- 1 files changed, 3 insertions(+), 5 deletions(-) diff --git a/tcl/interface/parport.cfg b/tcl/interface/parport.cfg index 22be8f3..0f18ce9

Re: [Openocd-development] imx31 breakpoints

>> and want to see what a bisection that skips known-incomplete stuff >> will turn up. 5eb893ec41c8c6cf6499558b6fed826b65e18a16 is first bad commit commit 5eb893ec41c8c6cf6499558b6fed826b65e18a16 Author: David Brownell Date: Tue Nov 24 01:27:16 2009 -0800 ARM11: partial support for standar

[Openocd-development] printing reason why GDB halts

Print reason why GDB halts. 1. srst detected: (gdb) c Continuing. Waking up GDB, srst asserted detected. [Thread ] #1 stopped. 0xda42bf3c in ?? () 2. failed to poll: (gdb) c Continuing. Failed to poll target, halting GDB. [Thread ] #1 stopped. 0x0004 in ?? () -- Øyvind Harboe US toll

Re: [Openocd-development] improved handling of target vs. gdb state

Take #3, I attached the wrong patch... -- Øyvind Harboe US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer From 902ac536d32073a0eb057b3a4342bdecba5ef847 Mon Sep 17 00:00:00 2001 From: =?utf-

[Openocd-development] improved handling of target vs. gdb state

Take #2 of this patch, now tested as per below. I'll be committing this unless there are any major protests. The target & gdb can be out of sync. The attached patch improves the case where the target is in the running state already when a stepi/continue packet is executed. 1. Case: target is run

Re: [Openocd-development] imx35.cfg question

On Wednesday 20 January 2010, Alexei Babich wrote: > > scan_chain >    TapName             Enabled  IdCode     Expected   IrLen IrCap IrMask > -- --- -- -- - - -- >  0 imx35.etb              Y     0x2b900f0f 0x2b900f0f     4 0x01  0x0f >  1 imx35