**** BEGIN LOGGING AT Thu Feb 25 02:59:58 2010 Feb 25 11:58:27 Hi, I'm pretty much new to OpenOCD (and JTAG), trying to get it to work with a JTAGkey2 and OMAP3430 target Feb 25 11:59:20 Even when I run openocd with just the jtagkey2 config file (no target/board config) it's spewing errors at me, especially "ft2232_read(): couldn't read enough bytes from FT2232 device (0 < 81)" Feb 25 12:00:29 ..makes me wonder whether it's perhaps not my target or the connection being wrong, but something on the host side Feb 25 12:00:55 (http://www.mail-archive.com/openocd-development@lists.berlios.de/msg09792.html seems related, though dmesg tells me it's running at high speed) Feb 25 12:01:06 Any idea/tips/hints? Feb 25 12:32:57 which version of openocd are you using? Feb 25 12:36:19 Latest stable Feb 25 12:36:56 Right I forgot to paste my debug log url, oops Feb 25 12:37:07 Log: http://pastie.org/842093 Feb 25 14:26:29 tried urjtag, which complains TDO is stuck at 0 Feb 25 14:29:52 which adaptor are you using? Feb 25 14:30:11 jtagtiny of amontec has problems with voltage detection Feb 25 14:30:23 jtagkeytiny Feb 25 14:30:39 JTAGkey2 Feb 25 14:30:52 what is v2? Feb 25 14:31:07 this one: Feb 25 14:31:16 http://www.zoobab.com/jtagkey-tiny Feb 25 14:31:17 ? Feb 25 14:31:20 A newer version of JTAGkey-1 Feb 25 14:31:20 No Feb 25 14:31:22 http://www.amontec.com/jtagkey2.shtml Feb 25 14:32:00 ah Feb 25 14:32:30 do you have another jtag adaptor? Feb 25 14:33:47 No, sadly not. But thomasg (in here as well) has had no succes with his turtelizer2 either. Same target (a Samsung phone). So it might be with the target - although we're both new to JTAG, so maybe we're simply doing something wrong. Feb 25 14:35:19 are you sure the pinout is correct? Feb 25 14:35:34 the best is to try to with simple JTAG adaptor on // port Feb 25 14:35:43 It was taken from a service manual, assuming it's correct.. Feb 25 14:39:37 http://i50.tinypic.com/mj9zjd.png that's what we have (OMAP is the target) Feb 25 14:54:11 zoobab: Do you know of any problems with openocd-0.4.0 and http://olimex.com/dev/arm-usb-ocd.html Feb 25 14:54:14 ? Feb 25 14:56:39 in particular, something that would cause "Error: unable to open ftdi device: unable to fetch product description" Feb 25 15:15:32 nope Feb 25 15:15:38 I use onyl urjtag Feb 25 15:15:45 openocd is too complex to configure Feb 25 15:15:54 I used it once Feb 25 15:16:04 It worked on windows and linux Feb 25 16:01:34 ius: it that running bada? Feb 25 16:02:37 ali1234: nope, limo Feb 25 16:03:04 and it needs to begone, hence jtag (and to recover a phone with a hosed bootloader) ;) Feb 25 16:03:18 but it's not _really_ working out yet, sadly Feb 25 16:04:04 I've got a new log, tthe other might have been a bad connection. It should be fine now, though Feb 25 16:04:08 http://pastie.org/842409 Feb 25 16:04:23 indeed, that does look like a bad connection to me Feb 25 16:04:36 if it's totally borked you generally would get nothing but zeros Feb 25 16:04:49 at least that's the result i used to get on openwince-jtag Feb 25 16:05:34 i just happened across the jtag pins for my omap850 phone, hoping to get debugging going one day, and to replace windows mobile :) Feb 25 16:39:00 :) Feb 25 16:39:17 ali1234: Was the bad connection remark regarding my first or the log I just pased? Feb 25 16:59:57 hm seems it found a TAP now, might be a bad connection Feb 25 17:00:07 Info : JTAG tap: auto0.tap tap/device found: 0x17f4c05f (mfg: 0x02f, part: 0x7f4c, ver: 0x1) Feb 25 17:00:22 Is there a list of mfgs/parts somewhere? Feb 25 17:03:39 should the turtelizer work with the free libftdl? Feb 25 17:04:07 same target here, only openocd doesn't even see a jtag device behind the turtelizer Feb 25 17:15:13 ius: the first log Feb 25 17:16:03 ius: i know that linux low level stuff uses the jtag IDs to identify cpus Feb 25 17:33:23 Well, confirmed my adapter is making bad contact Feb 25 21:01:47 Got something to work (finds some TAPs?) although it's still throwing errors at me: http://pastie.org/843038 **** ENDING LOGGING AT Fri Feb 26 02:59:57 2010