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 <arrayname> 32 <FIFO_address> 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 ST-Link?
AFAICT, yes. And it'd be the same for ICDI. > So, to figure out what's happening, please start openocd in gdb and > then place a breakpoint on stlink_usb_read_mem32(), run, try your > mem2array call and see how many times it's actually gets called, and > from where and with what parameters. > > I think that information may be more easily extracted from a -d3 debug log. > Keep > the session short and to the point and post the log to the list. I was assuming once he had gdb started he'd gather more information than what the debug log gives. Aren't we all spoiled by OpenOCD so much that plain serial output seems insufficient by default? ;) -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
