[Openocd-development] Clock setup script for STM32F107

Dear list, I have already posted the attached script some weeks ago. It enables the PLL of the STM32F107 and thus configures the MCU to run at 72 MHz which allows for higher JTAG speeds. Since this should be useful for everybody, I would like to contribute it to OpenOCD. However, I am not sure h

[Openocd-development] arm-jtag-ew fixes: Rebased patches

the OpenOCD main branch. If the patches are not in the expected format, or if you have further suggestions, please don't hesitate to contact me. Best regards, Simon >From 990646d220fdd85fd59f2c86c20fc16c8fc8e825 Mon Sep 17 00:00:00 2001 From: Simon Barner Date: Fri, 16 Sep 2011 21:06:

Re: [Openocd-development] Bugfix release (was: FreeRTOS bug fixes)

Dear Jean-Christophe, On 24.08.2011 16:12, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 19:54 Tue 23 Aug , Øyvind Harboe wrote: >> Do we need a bugfix release? > yes I've a bug on the usb in cross comp when integrate openocd in buildroot > > so I'll prepare a bugfix release within 1 or 2weeks

Re: [Openocd-development] [PULL Request] Flash program speedup through asynchronous algorithms

On 16.08.2011 01:25, Andreas Fritiofson wrote: > > > On Wed, Aug 10, 2011 at 12:01 AM, Spencer Oliver > wrote: > > On 09/08/2011 22:15, Øyvind Harboe wrote: > > Any objections? > > > I would like to give this a test-run tomorrow. > > > Did you (

[Openocd-development] [patch] ARM-JTAG-EW verbose debugging fixes 2/2

- Send GDB keep_alive() messages when logging USB communication - Ticket: #35 --- src/jtag/drivers/arm-jtag-ew.c |3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/src/jtag/drivers/arm-jtag-ew.c b/src/jtag/drivers/arm-jtag-ew.c index 20f7c99..e511d71 100644 --- a/src/jtag

[Openocd-development] [patch] ARM-JTAG-EW fixes 1/2

- Fix setting interface speed: - CMD_SET_TCK_FREQUENCY message length is 5, not 4 - Interface expects speed in Hz, not kHz - Provide armjtagew_speed_div() in order to fix interactive use of `adapter_khz' - Declare interface as `jtag_only' - Emit a warning if interface firmware version != 1.6

Re: [Openocd-development] Clock setup for STM32F107

Hi, > Thanks for testing the patches. So, a significant speed-up (~50%) due to > the async patches, great. I believe the actual flashing is now mostly > limited by flash write speed of the STM32F1x (~39 KiB/s => about 1.2 > seconds for your file) and that there's not much more that can be done >

Re: [Openocd-development] Clock setup for STM32F107

Andreas, list, On 04.08.2011 09:46, Simon Barner wrote: > On 04.08.2011 09:30, Simon Barner wrote: >> Some further benchmarks (OpenOCD compiled without any additional logging): >> >> @ 32 KHz: 1.9 kb/s >> @ 64 KHz: 3.4 kb/s >> @ 125 KHz: 5.6 kb/s >> @ 25

Re: [Openocd-development] Clock setup for STM32F107

On 04.08.2011 09:30, Simon Barner wrote: > Some further benchmarks (OpenOCD compiled without any additional logging): > > @ 32 KHz: 1.9 kb/s > @ 64 KHz: 3.4 kb/s > @ 125 KHz: 5.6 kb/s > @ 250 KHz: 8.1 kb/s > @ 500 KHz: 10.2 kb/s > @ 1MHz: 11.8 kb/s > @ 2MHz: 12.9 kb/s &

[Openocd-development] Clock setup for STM32F107

Hi, inspired by this post, I created a reset-init script that initializes the system clock for the STM32F107 (connectivity line) and sets the JTAG speed to 6 MHz. Currently, I source it in my custom configuration s

Re: [Openocd-development] Last call before release / Olimex ARM-JTAG-EW patches

ase let me know if you need more feedback. I would really appreciate to get these fixes into 0.5.0. Btw. If the are some testers who also own this interface, just let me know and I can provide you with a build that includes my patches. Best regards, Simon >From 87b05f377b94c3ad5773a5909f92708fb

Re: [Openocd-development] OpenOCD ticket 34 / usb_bulk_read failed

On 20.07.2011 11:26, Spencer Oliver wrote: >> My suggestion is to commit the attached workaround for the 0.5.0 release >> in order to unbreak the ARM-JTAG-EW, and to investigate on the source of >> the problems in a second step. >> > > I am not keen on committing hacks unless it is the last resor

Re: [Openocd-development] ARM-JTAG-EW set JTAG speed (was: OpenOCD ticket 34 / usb_bulk_read failed)

Hi, > This shows that my commit only revealed an existing bug in the > ARM-JTAG-EW speed setting function. Yes. > > The bug was introduced in an earlier version or has been there > from the beginning. Do a bisect to find out. According to the Git history, the relevant code did not change since

Re: [Openocd-development] OpenOCD ticket 34 / usb_bulk_read failed

Hi, >> I can see one change that the referred commit introduced >> to the ARM-JTAG-EW driver. It is that a speed setting in >> the init script now actually is executed. Any such setting >> was previously silently ignored. > > Do you mean the following in jtag/core.c? > > + retval = jtag->s

Re: [Openocd-development] OpenOCD ticket 34 / usb_bulk_read failed

Hi Jonas, > I can see one change that the referred commit introduced > to the ARM-JTAG-EW driver. It is that a speed setting in > the init script now actually is executed. Any such setting > was previously silently ignored. Do you mean the following in jtag/core.c? + retval = jtag->speed(j

[Openocd-development] OpenOCD ticket 34 / usb_bulk_read failed

Hi, I just could track down the following OpenOCD bug to the following commit: Do you have any clue what could be