On Tuesday 27 October 2009, Robin Callender wrote:
> Do you have any suggestions on how to begin to debug this?
> I've been looking at this most of today and need some guidance as where to
> start investigating.
In your case, double check how you've hooked up the JTAG
wiring. That "all ones" tends to mean it's not hooked up
correctly ... did you get the connector orientation right??
Cross check your connector's wiring against the BeagleBoard.
> > I don't know what's up with that either, but what doesn't it start
> > acting fine as soon as you issue a command like "reset halt"?
Appended below is what I got about five minutes ago. When
it starts talking right ater hookup, rudeness (not the same
as what you showed, sorry I thought it was) ... then right
after "reset halt", it behaves normally.
- Dave
Open On-Chip Debugger 0.3.0-dev-00443-g76afa93-dirty (2009-10-27-19:35)
$URL$
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
Warn : TAP omap3530.jrc does not have IDCODE
Warn : JTAG tap: omap3530.jrc UNEXPECTED: 0x00000000 (mfg: 0x000, part:
0x0000, ver: 0x0)
Error: JTAG tap: omap3530.jrc expected 1 of 1: 0x0b7ae02f (mfg: 0x017, part:
0xb7ae, ver: 0x0)
Error: Trying to use configured scan chain anyway...
Warn : Bypassing JTAG setup events due to errors
Info : tcl port disabled
Info : accepting 'telnet' connection from 0
RCLK not supported - fallback to 1000 kHz
Info : JTAG tap: omap3530.jrc tap/device found: 0x0b7ae02f (mfg: 0x017, part:
0xb7ae, ver: 0x0)
Info : JTAG tap: omap3530.dap enabled
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
spsr_svc: 0x800001d3 pc: 0x40202778
MMU: disabled, D-Cache: disabled, I-Cache: enabled
Info : dropped 'telnet' connection - error -400
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
