Doh! Working now.  I had the beagle board adapter plugged into the
beagle instead of the flyswatter.

On Tue, Dec 1, 2009 at 1:49 PM, John Rigby <jcri...@gmail.com> wrote:
> I already tried that:
>
> $ telnet localhost 4444
> Trying ::1...
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> Open On-Chip Debugger
>> reset halt
> RCLK not supported - fallback to 1000 kHz
> JTAG scan chain interrogation failed: all ones
> Check JTAG interface, timings, target power, etc.
> error: -100
> Command handler execution failed
> in procedure 'reset' called at file "command.c", line 637
> called at file "command.c", line 352
>>
>
> Its like I've got the jtag connector connected wrong.  I'm using the
> beagle board adapter that I got from tincantools.  And I have all the
> pin 1s matched up.
>
> On Tue, Dec 1, 2009 at 1:41 PM, David Brownell <davi...@pacbell.net> wrote:
>> On Tuesday 01 December 2009, John Rigby wrote:
>>> I'm trying to use OpenOCD with a Flyswatter and a beagleboard and I get 
>>> this:
>>>
>>> # openocd -f ./tcl/interface/flyswatter.cfg -f 
>>> ./tcl/board/ti_beagleboard.cfg
>>> Open On-Chip Debugger 0.4.0-dev-00740-ga65e75e (2009-12-01-12:05)
>>> For bug reports, read
>>>         http://openocd.berlios.de/doc/doxygen/bugs.html
>>> RCLK - adaptive
>>> Warn : omap3530.dsp: huge IR length 38
>>> RCLK - adaptive
>>> trst_only separate trst_push_pull
>>> Info : RCLK (adaptive clock speed) not supported - fallback to 1000 kHz
>>> Error: JTAG scan chain interrogation failed: all ones
>>> Error: Check JTAG interface, timings, target power, etc.
>>> Error: JTAG scan chain interrogation failed: all ones
>>> Error: Check JTAG interface, timings, target power, etc.
>>>
>>> Any ideas?
>>
>> "reset halt" should make things work OK.
>>
>> I don't know what causes that startup glitch, but things seem to
>> behave OK after an explicit reset.
>>
>>
>>
>
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to