Kees Jongenburger wrote: > On Wed, Dec 17, 2008 at 6:49 PM, Rick Altherr <[email protected]> wrote: > >>On Dec 17, 2008, at 9:06 AM, Dirk Behme wrote: >> >> >>>Before I can think about further testing or help, I'd like to be on a >>>confirmed status level. >> >>I believe the best status anyone has encountered is: the BeagleBoard boots >>and OpenOCD sees the Flyswatter. There is no success in setting up the JTAG >>chain. > > I believe the current svn version simply has some problems with the > flyswatter.
Urrgh :( Any details? > but > the status is/was a follow. Great! This is exactly what I'm looking for. Sounds like the first step is now to be able to reproduce this with recent svn version. > We where able to at least connect to the jrc (using booth the > flyswatter and jtagkey-tiny). :) > Dave apparently has had more luck hacking and was able to enabled the > DAP as some point. Dave? > ke...@ijssijs:~/projects/beagle/openocd$ make > sudo openocd > Open On-Chip Debugger 1.0 (2008-07-04-09:01) svn:738M > $URL: http://svn.berlios.de/svnroot/repos/openocd/trunk/src/openocd.c $ > Info: options.c:50 configuration_output_handler(): jtag_speed: 1, 1 > Info: jtag.c:1389 jtag_examine_chain(): JTAG device found: > 0x0b7ae02f (Manufacturer: 0x017, Part: 0xb7ae, Version: 0x0) Any details how this was done? Unfortunately, there is "(2008-07-04-09:01) svn:738M". I think switching back to this version isn't an option. Kees, Dave, Jason: We haven't got the "OMAP3 scan chain document" yet. So I'd like to ask again if anybody likes to send us (Rick & me) this document? You are allowed to send it: http://www.beagleboard.org/irclogs/index.php?date=2008-12-17#T16:03:01 Many thanks Dirk _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
