[OpenOCD-devel] [PATCH]: abeb522 top .gitignore: ignore .dirstamp files

2014-01-24 Thread gerrit
This is an automated email from Gerrit. Antony Pavlov (antonynpav...@gmail.com) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/1898 -- gerrit commit abeb522eb2be2bd4fc3a8e882a7410ac96d2f97a Author: Antony Pavlov Date: Sat Jan 25 11:07:53 2014 +0400

Re: [OpenOCD-devel] ftdi/xds100v2 connection issues

2014-01-24 Thread Paul Fertser
On Fri, Jan 24, 2014 at 03:27:39PM +0100, Alex Züpke wrote: > Am 18.01.2014 17:32, schrieb Paul Fertser: >> Does http://openocd.zylin.com/1884 help with this? >> > > It's getting better, but putting > init; ftdi_set_signal PWR_RST 1 > at the end of my config file doesn't help. > I need to restart

Re: [OpenOCD-devel] ftdi/xds100v2 connection issues

2014-01-24 Thread Andreas Fritiofson
On Fri, Jan 24, 2014 at 3:27 PM, Alex Züpke wrote: > Hi Paul, > > Am 18.01.2014 17:32, schrieb Paul Fertser: > > Hi, >> >> Does http://openocd.zylin.com/1884 help with this? >> >> > It's getting better, but putting > init; ftdi_set_signal PWR_RST 1 > at the end of my config file doesn't help. >

Re: [OpenOCD-devel] ftdi/xds100v2 connection issues

2014-01-24 Thread Alex Züpke
Hi Paul, Am 18.01.2014 17:32, schrieb Paul Fertser: Hi, Does http://openocd.zylin.com/1884 help with this? It's getting better, but putting init; ftdi_set_signal PWR_RST 1 at the end of my config file doesn't help. I need to restart openocd to get a connection on 2nd try. I'm using GIT He

[OpenOCD-devel] [PATCH]: 3470ec9 doc: add missing reg command argument 'force'

2014-01-24 Thread gerrit
This is an automated email from Gerrit. Spencer Oliver (s...@spen-soft.co.uk) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/1897 -- gerrit commit 3470ec93b9907d5dbce858de76e8f9d389d8562b Author: Spencer Oliver Date: Fri Jan 24 12:43:41 2014 +

Re: [OpenOCD-devel] reg command with no arguments - can it be forced to read from hardware

2014-01-24 Thread Spencer Oliver
On 22 January 2014 18:29, Adrian Burns wrote: > hi, > > I see the 'reg' command by itself reads from the targets reg_cache buffer > without calling into target hardware. > Is there any hook to force the 'reg' command to call into the target > specific code and read the registers from actual hardwa