On 4 July 2011 08:12, Andrew Leech <coronasen...@gmail.com> wrote:
> On 1/07/2011 8:47 PM, Spencer Oliver wrote:
>>
>> On 1 July 2011 00:41, Andrew Leech<coronasen...@gmail.com>  wrote:
>>>
>>> Only problem is, it's incredibly slow, unusably slow. A single step can
>>> take
>>> 5 seconds, where on a normal tcp connection with same configs feels close
>>> to
>>> instant, so maybe about 1/4 of a second. Did your windows one behave
>>> better?
>>> If so, do you know what version/release of gdb you used?
>>
>> used Sourcery G++ Lite 2011.03-42
>> Have not noticed any speed issues, most of my testing was under linux
>> however.
>> I am running winxp, that has always proved fairly nippy compared to
>> vista anyway.
>>
>
> Thanks, I was on 2010q3. Tried the newer one, and it initially didn't work,
> just locked up like yagarto. I eventually found reducing the
> jtag_nsrst_delay and jtag_ntrst_delay in my config and that got the newer
> Sourcery going (although this doesn't get yagarto going, it still doesn't
> work for me).
>
> Stepping is still slow though. I'm wondering if this is related to my cygwin
> on this machine, I've noticed that configure scripts on anything run
> incredibly slowly, never found out why. I decided to cross compile openocd
> from linux to rule out any issues from compiling with my cygwin (even though
> I used the mno-cygwin flag) but this also didn't make any difference. I'm
> not sure, maybe cygwin is stuffing up port's still or something.
>
> Delving into openocd logs, taking a -d3 on both pipe and tcp usage, I get
> exactly the same commands being run for both when stepping over the first
> line of my program, but in pipe usage lots of them take 100ms longer:
>

That 100ms may well be caused by the win32 version of select - win32
select does not support pipes so had to create a special version.
Check out the MsgWaitForMultipleObjects and you see your 100ms delay.

Perhaps this function needs tweaking.

Cheers
Spen
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to