On Friday 04 December 2009, Zach Welch wrote:
> On Fri, 2009-12-04 at 02:31 -0800, David Brownell wrote:
> > On Friday 04 December 2009, Øyvind Harboe wrote:
> > > That's better.
> >
> > It's an ugly hack that's papering over some real bug.
> >
> > Why was the JTAG initialization bypassed? The s
On Fri, Dec 4, 2009 at 12:32 PM, Zach Welch wrote:
> On Fri, 2009-12-04 at 02:31 -0800, David Brownell wrote:
>> On Friday 04 December 2009, Øyvind Harboe wrote:
>> > That's better.
>>
>> It's an ugly hack that's papering over some real bug.
>>
>> Why was the JTAG initialization bypassed? The stu
On Fri, 2009-12-04 at 02:31 -0800, David Brownell wrote:
> On Friday 04 December 2009, Øyvind Harboe wrote:
> > That's better.
>
> It's an ugly hack that's papering over some real bug.
>
> Why was the JTAG initialization bypassed? The stuff
> that forces the equivalent of "jtag_reset 0 0" ?
I j
On Friday 04 December 2009, Øyvind Harboe wrote:
> That's better.
It's an ugly hack that's papering over some real bug.
Why was the JTAG initialization bypassed? The stuff
that forces the equivalent of "jtag_reset 0 0" ?
> I still get error messages on startup(it should have
> examined the JTA
That's better.
I still get error messages on startup(it should have
examined the JTAG chain), but it works.
Info : clock speed 16000 kHz
Error: The 'init' command must be used before 'init'.
Command handler execution failed
Warn : jtag initialization failed; try 'jtag init' again.
Init complete,
On Thursday 03 December 2009, Øyvind Harboe wrote:
> Error: The 'init' command must be used before 'init'.
> Command handler execution failed
> Warn : jtag initialization failed; try 'jtag init' again.
Yeah, everything seems to cause JTAG init to fail lately.
One issue seems to be:
=
On Fri, Dec 4, 2009 at 10:36 AM, Zach Welch wrote:
> This is actually expected; there was no warning previously, and the
> dummy driver always fails because it returns garbage.
The error message is nonsensical and offers no clues as to what
is wrong, or what needs to be fixed.
The error message
This is actually expected; there was no warning previously, and the
dummy driver always fails because it returns garbage.
It still starts up, right? The fact that it is telling you where
something failed is a good thing, if were talking about real hardware...
right?
--Z
On Fri, 2009-12-04 at 08
I thought a fix for this one was pushed yesterday?
Still happens... With dummy driver even.
oyv...@titan:~/workspace/build$ openocd -f interface/dummy.cfg -f
board/at91eb40a.cfg
Open On-Chip Debugger 0.4.0-dev-00845-g24551b7 (2009-12-04-08:26)
For bug reports, read
http://openocd.berlios
