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 domen.pun...@visionect.si 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 /

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

2010-12-13 Thread Steve Bennett
On 13/12/2010, at 8:12 PM, Domen Puncer wrote: On Thu, Nov 25, 2010 at 15:45, Domen Puncer domen.pun...@visionect.si 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.

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 ste...@workware.net.au 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' elements, we only need to allocate

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

2010-12-13 Thread Steve Bennett
On 13/12/2010, at 11:00 PM, Domen Puncer wrote: On Mon, Dec 13, 2010 at 12:47, Steve Bennett ste...@workware.net.au 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

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 ste...@workware.net.au wrote: On 13/12/2010, at 11:00 PM, Domen Puncer wrote: On Mon, Dec 13, 2010 at 12:47, Steve Bennett ste...@workware.net.au wrote: Can we see the code being evaluated here? ==32465==    by 0x4B6DB2: Jim_Eval_Named

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

2010-12-13 Thread Steve Bennett
On 14/12/2010, at 5:50 AM, Domen Puncer wrote: On Mon, Dec 13, 2010 at 20:32, Steve Bennett ste...@workware.net.au wrote: On 13/12/2010, at 11:00 PM, Domen Puncer wrote: On Mon, Dec 13, 2010 at 12:47, Steve Bennett ste...@workware.net.au wrote: Can we see the code being evaluated here?

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 ste...@workware.net.au wrote: On 14/12/2010, at 5:50 AM, Domen Puncer wrote: On Mon, Dec 13, 2010 at 20:32, Steve Bennett ste...@workware.net.au wrote: On 13/12/2010, at 11:00 PM, Domen Puncer wrote: On Mon, Dec 13, 2010 at 12:47, Steve Bennett

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 oyvind.har...@zylin.com 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

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 s...@spen-soft.co.uk 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

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 pe...@stuge.se 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 be helpful if you could recompile openocd with

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

2010-11-26 Thread Spencer Oliver
On 25/11/2010 14: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 snip config file is rather boring: interface ft2232 ft2232_layout jtagkey ft2232_vid_pid 0x0403 0xcff8

[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

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

2010-11-25 Thread Peter Stuge
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 be helpful if you could recompile openocd with debugging symbols, and send a backtrace of the output from that.