On Tuesday 27 October 2009, Robin Callender wrote: > Hi all, > > I have built and am testing the lastest version of openocd using > a flyswatter connected to a beagleboard. > I have read this mail list for hints and reviewed all the directions > on the beagleboard JTAG pages, but I am still not able to get a good > JTAG connection.
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"? The flakiness is caused by JTAG acting rudely when things start; but later, it acts OK. At least for me. :) - Dave > My set up is identical to these shown in the flyswatter+beagleboard > photos: e.g. EMU0 and EMU1 set as shown in the photo. See the output > from my openocd below. > Note that this is on freshly checked out source from the archive (today). > > From the mail listings it seems that others have been able use this > combination. > So, I guess I must have something wrong. > Can someone give me a hint as to how to resolve this problem? > > Thanks much, > Robin > > > ==================== > ro...@ultraman:~/bin/openOCD$ sudo ./openocd -f interface/flyswatter.cfg -f > board/ti_beagleboard.cfg > Open On-Chip Debugger 0.3.0-dev-00441-g993fe4a (2009-10-27-16:20) > $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 : device: 4 "2232C" > Info : deviceID: 67330064 > Info : SerialNumber: FS000000 A > Info : Description: Flyswatter A > 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. > > _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
