Re: [Openocd-development] load_image trouble

2011-10-09 Thread Dmitry E. Oboukhov
I cant upload an image into internal SRAM (AT91SAM9). it can really write only 20 bytes. load_image into internal flash area works fine. >>> But why it doesn't fail if it writes the other regions? >>> It crashes only if it writes into internal SRAM. >> Could it be that the load_im

Re: [Openocd-development] gerrit hosting

2011-10-09 Thread Øyvind Harboe
> Anyway you can check this site to find any hoster with a code review > ability: > > http://en.wikipedia.org/wiki/Comparison_of_open_source_software_hosting_facilities No gerrit listed. I've asked sourceforge if they can install it, but I'm not holding my breath. -- Øyvind Harboe - Can Zylin Co

[Openocd-development] Clock setup script for STM32F107

2011-10-09 Thread Simon Barner
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

Re: [Openocd-development] Clock setup script for STM32F107

2011-10-09 Thread Michael Schwingen
Am 10/09/2011 12:37 PM, schrieb Simon Barner: > 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

Re: [Openocd-development] Clock setup script for STM32F107

2011-10-09 Thread Andreas Fritiofson
On Sun, Oct 9, 2011 at 12:37 PM, Simon Barner wrote: > 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

Re: [Openocd-development] What's up? Why so slow?

2011-10-09 Thread Akos Vandra
(At least) in SWD mode with an FTDI programmer openocd is sending data bit by bit. I am planning to send in a patch to fix that, but I am currently unable to test it, because I am waiting for my SWD-capable programmer. Regards, Ákos Vandra On 9 October 2011 08:21, Øyvind Harboe wrote: > USB rou

Re: [Openocd-development] What's up? Why so slow?

2011-10-09 Thread Peter Stuge
Øyvind Harboe wrote: > On Sun, Oct 9, 2011 at 3:40 AM, Peter Stuge wrote: > > Transfer rate: 3 KB/sec, 13848 bytes/write. > > USB roundtrips? Ḯ'll have a look with usbmon soon. Akos Vandra wrote: > (At least) in SWD mode with an FTDI programmer openocd is sending > data bit by bit. I am plann

Re: [Openocd-development] What's up? Why so slow?

2011-10-09 Thread Andreas Fritiofson
On Sun, Oct 9, 2011 at 10:43 PM, Peter Stuge wrote: > Øyvind Harboe wrote: > > On Sun, Oct 9, 2011 at 3:40 AM, Peter Stuge wrote: > > > Transfer rate: 3 KB/sec, 13848 bytes/write. > > > > USB roundtrips? > > Ḯ'll have a look with usbmon soon. > U+0618 LATIN CAPITAL LETTER I WITH DIRT ON TOP? I

Re: [Openocd-development] What's up? Why so slow?

2011-10-09 Thread Akos Vandra
P.S. Is it just me, or the default reply address is the sender himself, and not the list? Regards, Ákos On 9 October 2011 23:28, Akos Vandra wrote: > I am using the libswd fork, but I don't know how functional it is as > of yet, because I don't have any hardware to test it. > I just joined the

Re: [Openocd-development] What's up? Why so slow?

2011-10-09 Thread Peter Stuge
Akos Vandra wrote: > default reply address is the sender himself, and not the list? Please see http://woozle.org/~neale/papers/reply-to-still-harmful.html Mailing lists are a third form of email communication pattern. (The first two are person-to-person, and person-to-many-persons.) Using an ema

Re: [Openocd-development] What's up? Why so slow?

2011-10-09 Thread Andreas Fritiofson
On Sun, Oct 9, 2011 at 11:28 PM, Akos Vandra wrote: > P.S. Is it just me, or the default reply address is the sender > himself, and not the list? > The list server doesn't set Reply-To to the list address, for some very good reason which I have forgotten now. Easiest fix is to set reply-to-all a