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

2010-01-21 Thread Domen Puncer
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] segfault when gdb connects, but target is not connected

2010-11-10 Thread Domen Puncer
Hello, I can reproduce this one easily, amontec tiny dongle, stm32 target, which isn't connected. Fire up gdb to connect to openocd, and this happens: (gdb) r The program being debugged has been started already. Start it from the beginning? (y or n) y Starting program: /home/domen/tmp/openocd.git

Re: [Openocd-development] segfault when gdb connects, but target is not connected

2010-11-10 Thread Domen Puncer
On Wed, Nov 10, 2010 at 22:59, Øyvind Harboe wrote: > Could you try reproducing this problem using the dummy driver? > > openocd -c "interface dummy" -f yourconfig.cfg Gdb can't connect to openocd when using a dummy driver. My config, in case it matters: interface ft2232 ft2232_layout jtagkey f

Re: [Openocd-development] segfault when gdb connects, but target is not connected

2010-11-11 Thread Domen Puncer
On Thu, Nov 11, 2010 at 08:48, Øyvind Harboe wrote: > Try: > > openocd -c "interface dummy" -c "gdb_memory_map disable" -f target/stm32.cfg > No segfault in this case. --     Domen ___ Openocd-development mailing list Openocd-development@lists.berlios

Re: [Openocd-development] segfault when gdb connects, but target is not connected

2010-11-14 Thread Domen Puncer
On Sat, Nov 13, 2010 at 13:08, Øyvind Harboe wrote: > Does the attached patch fix the problem? Jup, did the trick. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development

[Openocd-development] Aborted; stm32 with too high clock

2010-11-25 Thread Domen Puncer
I can reliably reproduce this one with: jtag_khz 1000 verify_image my_image.elf # some prints about too high clock reset init # openocd aborts Open On-Chip Debugger 0.5.0-dev-00620-g1892a2b (2010-11-25-15:32) ... Error: 654 48021 adi_v5_jtag.c:335 jtagdp_transaction_endcheck(): MEM_AP_CSW 0x23

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-11-26 Thread Domen Puncer
On Thu, Nov 25, 2010 at 19:29, Peter Stuge wrote: > Domen Puncer wrote: >> I can reliably reproduce this one with: >> jtag_khz 1000 >> verify_image my_image.elf >> # some prints about too high clock >> reset init >> # openocd aborts > > It would b

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-11-27 Thread Domen Puncer
On Fri, Nov 26, 2010 at 13:29, Spencer Oliver wrote: > Just tried to reproduce this on two boards with your exact config - all ok. You tried setting clock to too high etc., as described in original post? It works fine otherwise, it's just this one bug I noticed while playing with jtag_khz > > Ha

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-11-30 Thread Domen Puncer
On Sat, Nov 27, 2010 at 13:15, Domen Puncer wrote: > On Fri, Nov 26, 2010 at 13:29, Spencer Oliver wrote: >> Just tried to reproduce this on two boards with your exact config - all ok. > > You tried setting clock to too high etc., as described in original > post? It works fi

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-11-30 Thread Domen Puncer
On Tue, Nov 30, 2010 at 16:09, Øyvind Harboe wrote: > Could you try to reproduce this with the dummy driver? > > configure --enable-dummy ... > > openocd -c "interface dummy" Not reproduceable with dummy. ___ Openocd-development mailing list Openoc

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-12-01 Thread Domen Puncer
On Wed, Dec 1, 2010 at 08:41, Øyvind Harboe wrote: > Can you try with a 32 bit OpenOCD executable? I don't have a 32-bit linux box around. Can someone share a binary? ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://list

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-12-13 Thread Domen Puncer
On Thu, Nov 25, 2010 at 15:45, Domen Puncer wrote: > I can reliably reproduce this one with: > jtag_khz 1000 > verify_image my_image.elf > # some prints about too high clock > reset init > # openocd aborts Additional info. valgrind: ==32465== Invalid free() / delete / delete

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-12-13 Thread Domen Puncer
On Mon, Dec 13, 2010 at 12:47, Steve Bennett wrote: > > On 13/12/2010, at 8:12 PM, Domen Puncer wrote: >> >> but code only allocates space for extra len-1 objects. > > There is already one "slot" allocated for the arg. If the arg expands to 'len' >

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-12-13 Thread Domen Puncer
On Mon, Dec 13, 2010 at 20:32, Steve Bennett wrote: > On 13/12/2010, at 11:00 PM, Domen Puncer wrote: > >> On Mon, Dec 13, 2010 at 12:47, Steve Bennett wrote: >>> >>> Can we see the code being evaluated here? >>>> ==32465==    by 0x4B6DB2: Jim_Eval_

Re: [Openocd-development] Aborted; stm32 with too high clock

2010-12-13 Thread Domen Puncer
On Mon, Dec 13, 2010 at 21:17, Steve Bennett wrote: > On 14/12/2010, at 5:50 AM, Domen Puncer wrote: > >> On Mon, Dec 13, 2010 at 20:32, Steve Bennett wrote: >>> On 13/12/2010, at 11:00 PM, Domen Puncer wrote: >>> >>>> On Mon, Dec 13, 2010 at 12:47, Stev

Re: [Openocd-development] [PATCH] dsp563xx: fix alignment warnings

2011-03-15 Thread Domen Puncer
On Mon, Mar 14, 2011 at 15:33, Øyvind Harboe wrote: > Signed-off-by: Øyvind Harboe > --- >  src/target/dsp563xx.c |   12 ++-- >  1 files changed, 6 insertions(+), 6 deletions(-) > > diff --git a/src/target/dsp563xx.c b/src/target/dsp563xx.c > index cb2025e..19f793e 100644 > --- a/src/targ