(recieved by mail, did not see the version sent to list)
Kees Jongenburger wrote:
,
|
| Hello John
|
| On Thu, Nov 20, 2008 at 2:56 PM, John Devereux <[EMAIL PROTECTED]> wrote:
| > > I am using the Amontec JTAGkey with openocd. On windows it works
| > > great. But on linux I am finding that
On Nov 23, 2008, at 10:10 AM, Carlos Antunes wrote:
Rick Altherr wrote:
Debug: 298 216881 target.c:1787 target_wait_state(): waiting for
target debug-running...
This _appears_ to be coming from arm7_9_dcc_completion(). That
method is specified to be called at the end of an arm7_9 wri
On Nov 23, 2008, at 9:27 AM, Øyvind Harboe wrote:
On Sat, Nov 22, 2008 at 12:54 PM, Spen <[EMAIL PROTECTED]> wrote:
Hi,
I think its about time openocd made a release 1.0.
I propose we create a openocd_rel_1_0 branch that will be frozen
(except for
major bugs) after a month we make a releas
Rick Altherr wrote:
>
>> Debug: 298 216881 target.c:1787 target_wait_state(): waiting for
>> target debug-running...
>
> This _appears_ to be coming from arm7_9_dcc_completion(). That method
> is specified to be called at the end of an arm7_9 write memory block.
> It is the only place in the
Lots of stuff to read here... :-) I'm going to read more carefully
through this once the dust settles
My main concern at this point is that *simple* things should
remain simple.
A target configuration script for a PCB with three tap's shouldn't
be any more difficult today. Especially in terms
On Sat, Nov 22, 2008 at 12:54 PM, Spen <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I think its about time openocd made a release 1.0.
> I propose we create a openocd_rel_1_0 branch that will be frozen (except for
> major bugs) after a month we make a release.
>
> Any objections/comments?
Instead of tryin
