Merged.
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@lists.berl
Here is the updated patch.
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
From 2d67bf6a0ffb36e293c4bdc2b65cb8867ba5534d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=98y
Øyvind Harboe wrote:
> You should see much more reasonable behavior with the patch for
> your case above.
Cool! I'll try to do some testing soon.
//Peter
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de
On Sun, Aug 8, 2010 at 9:30 PM, Peter Stuge wrote:
> Øyvind Harboe wrote:
>> I don't know of other "spam" sources
>
> Unplugging an FT2232 JTAG adapter makes OpenOCD unhappy; it
> repeatedly complains about failed transfers. This might be because
> of a bug in libftdi too of course.
You should s
> Having same message repeated tens or hundreds of
>times per second because the server goes bananas it
>is not useful to anyone, and can easily be automatically
>suppressed. Handling this in the logging system means
>it needs to be done only once instead of in every place
>it can happen. If you wa
Øyvind Harboe wrote:
> I don't know of other "spam" sources
Unplugging an FT2232 JTAG adapter makes OpenOCD unhappy; it
repeatedly complains about failed transfers. This might be because
of a bug in libftdi too of course.
//Peter
___
Openocd-developmen
On Aug 8, 2010, at 21:50, Øyvind Harboe wrote:
> On Sun, Aug 8, 2010 at 8:41 PM, Anders Montonen
> wrote:
>> On Aug 8, 2010, at 9:14, Øyvind Harboe wrote:
>>
>>> Currently OpenOCD will ignore failure to poll the target.
>>>
>>> This can result in a situation where errors are being spewed out.
>
On Sun, Aug 8, 2010 at 8:41 PM, Anders Montonen wrote:
> On Aug 8, 2010, at 9:14, Øyvind Harboe wrote:
>
>> Currently OpenOCD will ignore failure to poll the target.
>>
>> This can result in a situation where errors are being spewed out.
>>
>> I am considering making a change to OpenOCD where poll
On Aug 8, 2010, at 9:14, Øyvind Harboe wrote:
> Currently OpenOCD will ignore failure to poll the target.
>
> This can result in a situation where errors are being spewed out.
>
> I am considering making a change to OpenOCD where polling
> is automatically disabled when it fails. The user would
An objection of my own:
there are probably situations today when polling fail that we
don't think too much about. One situation I can think of is
power cycling the target.
It would be hard to map out these situations via testing and
add code to handle them.
Another "temporary" way to disable pol
Currently OpenOCD will ignore failure to poll the target.
This can result in a situation where errors are being spewed out.
I am considering making a change to OpenOCD where polling
is automatically disabled when it fails. The user would then have
to manually reenable polling.
A typical scenario
11 matches
Mail list logo
