Re: [Openocd-development] LPC2919 segmentation fault

2010-11-26 Thread Rolf Meeser
Hi Øyvind, --- Øyvind Harboe schrieb am Fr, 26.11.2010: > Von: Øyvind Harboe > Betreff: Re: [Openocd-development] LPC2919 segmentation fault > An: "MIroslav Dušek" > CC: openocd-development@lists.berlios.de > Datum: Freitag, 26. November, 2010 21:44 Uhr > 2010/11/26 MIroslav Dušek : > > Hi , >

Re: [Openocd-development] LPC2919 segmentation fault

2010-11-26 Thread Rolf Meeser
Hi Mirda, --- MIroslav Dušek schrieb am Fr, 26.11.2010: > mdw 0xE100 16 0xe100: Ooops, that's a broken device! Looks like it hasn't seen the final production test before shipping... I'll follow up on this by pri

Re: [Openocd-development] LPC2919 segmentation fault

2010-11-26 Thread Øyvind Harboe
2010/11/26 MIroslav Dušek : > Hi , > Thank you for help. > I am sorry, but what is openocd master branch? 0.4 is quite old. Your problem may have been long fixed. clone the openocd git repository, check out the master branch build OpenOCD. -- Øyvind Harboe Can Zylin Consulting help on your

Re: [Openocd-development] LPC2919 segmentation fault

2010-11-26 Thread MIroslav Dušek
Hi Rolf , Thank you for your help. > mdw 0xE100 16 0xe100: 0xe120: Best regards Mirda 2010/11/25 Rolf Meeser > Hi Mirda, > > --- mirda.

Re: [Openocd-development] LPC2919 segmentation fault

2010-11-26 Thread MIroslav Dušek
Hi , Thank you for help. I am sorry, but what is openocd master branch? Best regards Mirda 2010/11/25 Øyvind Harboe > Try the openocd master branch. > > > > -- > Øyvind Harboe > > Can Zylin Consulting help on your project? > > US toll free 1-866-980-3434 / International +47 51 63 25 00 > > h

Re: [Openocd-development] segfault idea

2010-11-26 Thread Alexandre Pereira da Silva
Maybe we could just print the stack trace by default in case of problems: http://tlug.up.ac.za/wiki/index.php/Obtaining_a_stack_trace_in_C_upon_SIGSEGV On Fri, Nov 26, 2010 at 6:38 AM, Øyvind Harboe wrote: > How about adding a handler(to Windows and Linux) that prints out > instructions on how to

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 sourc

[Openocd-development] segfault idea

2010-11-26 Thread Øyvind Harboe
How about adding a handler(to Windows and Linux) that prints out instructions on how to track down and report a segfault? -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XSc

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 be helpful if you could recompile openocd with debug