Hi Jon,
I really think it is not related to OS kernel nor to kernel driver nor
Virtual Machine. But really coming from something in the OpenOCD code
itself.
Also, it should be related to *HOW* OpenOCD is closing the Amontec
JTAGkey (and or the JTAGkey-2 ), specially regarding TRST and SRST.
Sounds reasonable to me. I haven't tested.
I'll let it cool off for a few days before merging.
--
Meet Zylin at ESC 2010 San Jose
April 26 - 30. 2010
http://www.zylin.com/events_esc2010.html
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
Laurent Gauch wrote:
Hi Jon,
I really think it is not related to OS kernel nor to kernel driver nor
Virtual Machine. But really coming from something in the OpenOCD code
itself.
Also, it should be related to *HOW* OpenOCD is closing the Amontec
JTAGkey (and or the JTAGkey-2 ), specially
After my earlier emails I have been trying to narrow things down a bit.
I have switched from running OpenOCD on Linux inside VirtualBox, to running it
natively on XP. I have not been able to reproduce the situation that needed the
JTAGKey-Tiny to be replugged, but I still get random
Hi folks,
A very useful thing for a debugger to do is to fill memory with some repeating
pattern (0xdeadbeef, 0xfeedface, 0x0badface, etc, are popular). I thought it
would be a simple thing to implement a tcl script to do this; one that uses
openocd's internal mww command. Then I found that
On 2010-04-20 09:46, Andreas Fritiofson wrote:
Freddie, have you checked if the patch resolves your problem?
I managed to check that today (sorry for delay). Current master (with
the merged patch) fixes the first gdb load issue completely for me.
Everything else regarding the stm32 chip
BTW - I've posted the compiled version on my website
(www.freddiechopin.info) for ppl to test.
Cheers!
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
help mww
The third argument is a count and not only that, mww uses an
*efficient* way to fill memory, so you can fill megabytes in seconds
(with a decent adapter, such as the ZY1000, ahem :-)
--
Meet Zylin at ESC 2010 San Jose
April 26 - 30. 2010
http://www.zylin.com/events_esc2010.html
help mww
The third argument is a count and not only that, mww uses an
*efficient* way to fill memory, so you can fill megabytes in seconds
(with a decent adapter, such as the ZY1000, ahem :-)
Ah, had a feeling I was missing the obvious. Thanks! I'll look into your
company's fine product.
On Thu, Apr 22, 2010 at 9:18 PM, miked...@newsguy.com wrote:
help mww
The third argument is a count and not only that, mww uses an
*efficient* way to fill memory, so you can fill megabytes in seconds
(with a decent adapter, such as the ZY1000, ahem :-)
Ah, had a feeling I was missing the
We use a parallel port debugger for X reference/testing purposes.
I think the speed difference is ca. 1:10 these days depending on operation
that is...
Was going to drop you a wisecracking note after ~15 minutes and still waiting
for approx 112Kb of memory to fill. Does the speed
On Thu, Apr 22, 2010 at 6:38 PM, Jon Povey jon.po...@racelogic.co.uk wrote:
After my earlier emails I have been trying to narrow things down a bit.
I have switched from running OpenOCD on Linux inside VirtualBox, to running it
natively on XP. I have not been able to reproduce the situation
12 matches
Mail list logo
