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

Re: [Openocd-development] lpc3131 and Actel FPGA chain programming.

2010-11-14 Thread Andrew Leech
On Sat, Nov 13, 2010 at 1:28 AM, Peter Stuge wrote: >> There's specific HDR and similar commands in svf to define these >> paddings. > > Can you say more about them? Did you study the SVF output by > FlashPro? It would be interesting to diff a failing SVF with a > working one. > Yeah I've just b

Re: [Openocd-development] [PATCH] Build inline jimtcl

2010-11-14 Thread Steve Bennett
On 13/11/2010, at 1:13 AM, Spencer Oliver wrote: > On 12/11/2010 14:31, Spencer Oliver wrote: >> Hi, >> >> Started a new thread as the others are getting bogged down. >> >> This defaults to building the jimtcl inline - only one configure step >> required, eg. >> ./configure --enable-maintainer-m

Re: [Openocd-development] Disable stm32x block write by default?

2010-11-14 Thread Øyvind Harboe
On Sun, Nov 14, 2010 at 10:58 PM, Freddie Chopin wrote: > On 2010-11-14 18:49, Øyvind Harboe wrote: >> >> The problem is that the target is crashing while executing the programming >> algorithm, so it never completes. > > You mean crashing like having Hard Fault exception or sth like this? Yes.

Re: [Openocd-development] Disable stm32x block write by default?

2010-11-14 Thread Freddie Chopin
On 2010-11-14 18:49, Øyvind Harboe wrote: The problem is that the target is crashing while executing the programming algorithm, so it never completes. You mean crashing like having Hard Fault exception or sth like this? 4\/3!! ___ Openocd-development

Re: [Openocd-development] Disable stm32x block write by default?

2010-11-14 Thread Øyvind Harboe
> As I cannot reproduce, if this one is repeating at your side, maybe try > injecting some messages around there to see whether that's the exact point > of problems? The problem is that the target is crashing while executing the programming algorithm, so it never completes. -- Øyvind Harboe Ca

Re: [Openocd-development] Disable stm32x block write by default?

2010-11-14 Thread Freddie Chopin
On 2010-11-09 10:16, Øyvind Harboe wrote: Error: 793 186992 stm32x.c:582 stm32x_write_block(): error executing stm32x flash write algorithm Error: 794 186993 core.c:98 flash_driver_write(): error writing to flash at address 0x0800 at offset 0x (-302) On 2010-11-14 16:13, Øyvind Harb

Re: [Openocd-development] [PATCH] Add comments and tiny improvements to STM32 flash loader algorithm

2010-11-14 Thread Øyvind Harboe
>> Perhaps sharper error messages? > > It was in the previous code: > > -       tst             r3, #0x14 > -       bne             exit k. I missed that one. Unless I hear protests, I'll merge this code after a cool off period. -- Øyvind Harboe Can Zylin Consulting help on your project? US

Re: [Openocd-development] [PATCH] Add comments and tiny improvements to STM32 flash loader algorithm

2010-11-14 Thread Freddie Chopin
On 2010-11-14 16:13, Øyvind Harboe wrote: But you did add another error check? + tst r3, #0x14 /* PGERR (bit2) == 1 or WRPRTERR (bit4) == 1 => error */ + bne exit

Re: [Openocd-development] [PATCH] Add comments and tiny improvements to STM32 flash loader algorithm

2010-11-14 Thread Øyvind Harboe
On Sat, Nov 13, 2010 at 11:14 PM, Freddie Chopin wrote: > On 2010-11-13 16:47, Øyvind Harboe wrote: >> >> Is it conceivable that this would address the block >> flash programming problems I saw the other day >> and you were not able to reproduce? > > Rather not... The mechanics of this algorithm a