On Sunday 29 November 2009, Zach Welch wrote:
Broken how? It's worked as advertised, as far as I know.
It was allowing all commands to run during CONFIG stage, regardless of
whether they were marked EXEC-only. Broken.
The key instant seems to be when JTAG starts. Once that starts,
On Thu, 2009-12-03 at 15:00 -0800, David Brownell wrote:
On Sunday 29 November 2009, Zach Welch wrote:
Broken how? It's worked as advertised, as far as I know.
It was allowing all commands to run during CONFIG stage, regardless of
whether they were marked EXEC-only. Broken.
The
Excellent. I came up with nearly the same patch before running out for
the evening. The difference being that I put _after_ the last possible
failure path, so it's possible to recover and try again.
On Sat, 2009-11-28 at 22:43 -0800, David Brownell wrote:
On Saturday 28 November 2009, David
On Sunday 29 November 2009, Zach Welch wrote:
Excellent. I came up with nearly the same patch before running out for
the evening. The difference being that I put _after_ the last possible
failure path, so it's possible to recover and try again.
It has to be before, because the initialization
On Sat, 2009-11-28 at 18:16 -0800, David Brownell wrote:
On Saturday 28 November 2009, Zach Welch wrote:
Yeah, I figure there are some scripts (or users) that have not been
sufficiently strict about CONFIG vs. EXEC modes, as that logic has been
broken for ages
Broken how? It's
I just pulled everything into a workspace and built it ... now it's
failing left and right.
It complains about using poll off and jtag_reset 1 1 after reset,
which is when they're supposed to be usable...
___
Openocd-development mailing list
On Saturday 28 November 2009, David Brownell wrote:
I just pulled everything into a workspace and built it ... now it's
failing left and right.
It complains about using poll off and jtag_reset 1 1 after reset,
which is when they're supposed to be usable...
And if I disable that error check,
On Sat, 2009-11-28 at 15:10 -0800, David Brownell wrote:
I just pulled everything into a workspace and built it ... now it's
failing left and right.
It complains about using poll off and jtag_reset 1 1 after reset,
which is when they're supposed to be usable...
I had tested that the patch
On Sat, 2009-11-28 at 15:21 -0800, David Brownell wrote:
On Saturday 28 November 2009, David Brownell wrote:
I just pulled everything into a workspace and built it ... now it's
failing left and right.
It complains about using poll off and jtag_reset 1 1 after reset,
which is when
On Saturday 28 November 2009, Zach Welch wrote:
I believe that the real problem is that the .mode initializer for those
commands' registration records have been marked incorrectly. There may
be others It's easy to discover which ones need to be fixed, but
that does not sound like the
On Sat, 2009-11-28 at 16:36 -0800, David Brownell wrote:
On Saturday 28 November 2009, Zach Welch wrote:
I believe that the real problem is that the .mode initializer for those
commands' registration records have been marked incorrectly. There may
be others It's easy to discover
On Saturday 28 November 2009, Zach Welch wrote:
Maybe part of the problem is that putting the init on the command line
with a bunch of other commands.
Confirmed: take a working command line and add
... -c init -c poll off
and it no longer works.
On Saturday 28 November 2009, Zach Welch wrote:
Yeah, I figure there are some scripts (or users) that have not been
sufficiently strict about CONFIG vs. EXEC modes, as that logic has been
broken for ages
Broken how? It's worked as advertised, as far as I know.
Nevertheless, the very
On Saturday 28 November 2009, David Brownell wrote:
I just pulled everything into a workspace and built it ... now it's
failing left and right.
This makes the worst of it go away. The context mode
is supposed to change when init runs ... which isn't
necessarily going to be when main() tries
14 matches
Mail list logo
