Re: [OpenOCD-devel] mem2array script command double read issue

2013-08-02 Thread Paul Fertser
Hi, On Fri, Aug 02, 2013 at 12:59:50PM -0700, Kenneth Lee wrote: > Thanks for the Response, my apologies for the HTML, it was not > intentional. No problem. If you avoided top-posting too, and didn't omit the mailing list from Cc, that would be even nicer ;) > I just went ahead followed your GDB

Re: [OpenOCD-devel] mem2array script command double read issue

2013-08-02 Thread Paul Fertser
On Fri, Aug 02, 2013 at 10:12:59AM +0200, Andreas Fritiofson wrote: > On Fri, Aug 2, 2013 at 9:40 AM, Paul Fertser <[1][email protected]> wrote: > > On Thu, Aug 01, 2013 at 06:34:42PM -0700, Kenneth Lee wrote: > > mem2array 32 1** <-- Reads 32-bit data but > decrements > > FIFO by 2 wo

Re: [OpenOCD-devel] mem2array script command double read issue

2013-08-02 Thread Andreas Fritiofson
On Fri, Aug 2, 2013 at 9:40 AM, Paul Fertser wrote: > On Thu, Aug 01, 2013 at 06:34:42PM -0700, Kenneth Lee wrote: > > mem2array 32 1** <-- Reads 32-bit data but > decrements > > FIFO by 2 words (should be 1) > > Strange. > So this is the only unexpected case, considering the shortcomings of S

Re: [OpenOCD-devel] mem2array script command double read issue

2013-08-02 Thread Paul Fertser
Hi, Please do not send HTML to the mailing list, plain text is much easier and consistent. On Thu, Aug 01, 2013 at 06:34:42PM -0700, Kenneth Lee wrote: > I am using the ST Link V2 integrated on the STM32F4 Discovery Board and > OpenOCD > 0.8.0. Yep, that's a very important detail. > mem2array

[OpenOCD-devel] mem2array script command double read issue

2013-08-01 Thread Kenneth Lee
Hi all, I am using the ST Link V2 integrated on the STM32F4 Discovery Board and OpenOCD 0.8.0. When using *mem2array 32 1* from tcl script, I am observing behavior that suggest the command is reading the memory location twice. I am reading a 32-bit wide memory mapped FIFO where every FIF