Re: [Openocd-development] [PATCH 0/7] RLink interface speedup, and fixes

2011-07-21 Thread Peter Horn
Am 19.07.2011 22:43, schrieb Peter Horn: Hi Andreas I have access to a standalone Rlink, an Olimex STM32-P103 board and a Raisonance REva STM32 connectivity board which has an onboard Rlink. I've applied your patches and built OpenOCD on Linux with success. A quick test revealed no problems but

Re: [Openocd-development] Problem with OpenOCD 0.5.0-rc1 and STM32 verify_image

2011-07-21 Thread Andreas Fritiofson
On Thu, Jul 21, 2011 at 10:44 PM, Magnus S. wrote: > Freddie Chopin writes: > > > > > I can partially confirm... > > > > Tested with 0.5.0-rc1 > > > > Comparing with "right image" works fine: > > > > > > Comparing with "almost right image" (compilation date inside has > > changed) works fine too

Re: [Openocd-development] Problem with OpenOCD 0.5.0-rc1 and STM32 verify_image

2011-07-21 Thread Magnus S .
Freddie Chopin writes: > > I can partially confirm... > > Tested with 0.5.0-rc1 > > Comparing with "right image" works fine: > > > Comparing with "almost right image" (compilation date inside has > changed) works fine too: > > > However... when checking against something completely wrong (

Re: [Openocd-development] [PATCH] add Fujitsu FM3 Family flash support

2011-07-21 Thread Spencer Oliver
On 21/07/2011 19:30, Ronny Strutz wrote: Hi, i've ported the fm3 port by Marc Willam to current git. Feel free to apply. As this has no impact on existing functionality i would like to commit this before 0.5 - objections? Cheers Spen ___ Openoc

[Openocd-development] [PATCH] add Fujitsu FM3 Family flash support

2011-07-21 Thread Ronny Strutz
Hi, i've ported the fm3 port by Marc Willam to current git. Feel free to apply. Ronny >From 7a14b88155486cba9d7e073e6edbb8292d2d4f64 Mon Sep 17 00:00:00 2001 From: Ronny Strutz Date: Thu, 21 Jul 2011 08:14:12 + Subject: [PATCH] add Fujitsu FM3 Family flash support Signed-off-by: Ronny S

Re: [Openocd-development] Problem with OpenOCD 0.5.0-rc1 and STM32 verify_image

2011-07-21 Thread Freddie Chopin
I can partially confirm... Tested with 0.5.0-rc1 Comparing with "right image" works fine: verify_image c://stm32_blink_led.bin 0x800 verified 29888 bytes in 0.468750s (62.267 KiB/s) verify_image c://stm32_blink_led.bin verified 29888 bytes in 0.484375s (60.258 KiB/s) verify_image c://s

[Openocd-development] [PATCH] Remove deprecated '-p' option from doc

2011-07-21 Thread Jie Zhang
The subject explains this patch. Jie From 26f44455cf1db6f2efb8531f5476ad2845e47f13 Mon Sep 17 00:00:00 2001 From: Jie Zhang Date: Thu, 21 Jul 2011 11:29:20 -0400 Subject: [PATCH] remove doc on the deprecated '-p' option --- doc/openocd.texi |2 -- 1 files changed, 0 insertions(+), 2 deletio

[Openocd-development] [PATCH] Update doc about Jim

2011-07-21 Thread Jie Zhang
The commit log explains this patch. Jie From 00597ea44a60e70a86ef989acfb8193c15de811a Mon Sep 17 00:00:00 2001 From: Jie Zhang Date: Thu, 21 Jul 2011 11:16:50 -0400 Subject: [PATCH] Update doc about Jim since it's not a single .C file and a single .H file any more --- doc/openocd.texi |2

Re: [Openocd-development] Adding commands for GDB remote accesses

2011-07-21 Thread Julius Baxter
Hi Igor, > JB> However, I'd really like something which would allow custom RSP > JB> commands (which can write back to the socket) to be handled. > JB> The problems I see are that, even though the gdb_put_packet() function > JB> is declared and could be used by target code, I can't, for the life o

Re: [Openocd-development] Adding commands for GDB remote accesses

2011-07-21 Thread Spencer Oliver
On 21 July 2011 11:18, Igor Skochinsky wrote: > Hello Julius, > > Thursday, July 21, 2011, 11:48:17 AM, you wrote: > > JB> I'm looking at adding OpenRISC 1000 support to OpenOCD. > [skip] > JB> One solution is we make our GDB port not use these remote query > JB> commands and instead rely on the r

Re: [Openocd-development] Adding commands for GDB remote accesses

2011-07-21 Thread Igor Skochinsky
Hello Julius, Thursday, July 21, 2011, 11:48:17 AM, you wrote: JB> I'm looking at adding OpenRISC 1000 support to OpenOCD. [skip] JB> One solution is we make our GDB port not use these remote query JB> commands and instead rely on the register cache fetched with the "g" JB> RSP command. You can

[Openocd-development] Adding commands for GDB remote accesses

2011-07-21 Thread Julius Baxter
Hi all, I'm looking at adding OpenRISC 1000 support to OpenOCD. At present, the OpenRISC GDB port implements reading and writing to individual CPU registers by an "spr" command within GDB. This sends out CPU register access requests as remote commands, and they are handled in by the RSP server as