| 01:09.13 | *** join/#openjtag Openfree` (~Openfreer@116.228.88.98) |
| 02:57.25 | *** join/#openjtag _julian (~quassel@dslc-082-083-145-107.pools.arcor-ip.net) |
| 06:11.41 | *** join/#openjtag Weaselweb (~quassel@2001:6f8:9e4:123:21a:92ff:fe5a:1409) |
| 10:36.30 | *** join/#openjtag roxfan (dunno@81.78-241-81.adsl-dyn.isp.belgacom.be) |
| 10:46.54 | *** join/#openjtag ali1234 (~al@robotfuzz.co.uk) |
| 11:58.27 | ius | Hi, I'm pretty much new to OpenOCD (and JTAG), trying to get it to work with a JTAGkey2 and OMAP3430 target |
| 11:59.21 | ius | 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)" |
| 12:00.29 | ius | ..makes me wonder whether it's perhaps not my target or the connection being wrong, but something on the host side |
| 12:00.55 | ius | (http://www.mail-archive.com/openocd-development@lists.berlios.de/msg09792.html seems related, though dmesg tells me it's running at high speed) |
| 12:01.06 | ius | Any idea/tips/hints? |
| 12:32.57 | Spida | which version of openocd are you using? |
| 12:36.19 | ius | Latest stable |
| 12:36.56 | ius | Right I forgot to paste my debug log url, oops |
| 12:37.07 | ius | Log: http://pastie.org/842093 |
| 14:26.29 | ius | tried urjtag, which complains TDO is stuck at 0 |
| 14:29.52 | zoobab | which adaptor are you using? |
| 14:30.10 | zoobab | jtagtiny of amontec has problems with voltage detection |
| 14:30.23 | zoobab | jtagkeytiny |
| 14:30.39 | ius | JTAGkey2 |
| 14:30.52 | zoobab | what is v2? |
| 14:31.07 | zoobab | this one: |
| 14:31.16 | zoobab | http://www.zoobab.com/jtagkey-tiny |
| 14:31.17 | zoobab | ? |
| 14:31.20 | ius | A newer version of JTAGkey-1 |
| 14:31.20 | ius | No |
| 14:31.22 | ius | http://www.amontec.com/jtagkey2.shtml |
| 14:32.00 | zoobab | ah |
| 14:32.29 | zoobab | do you have another jtag adaptor? |
| 14:33.47 | ius | 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. |
| 14:35.19 | zoobab | are you sure the pinout is correct? |
| 14:35.33 | zoobab | the best is to try to with simple JTAG adaptor on // port |
| 14:35.43 | ius | It was taken from a service manual, assuming it's correct.. |
| 14:39.37 | ius | http://i50.tinypic.com/mj9zjd.png that's what we have (OMAP is the target) |
| 14:54.11 | Spida | zoobab: Do you know of any problems with openocd-0.4.0 and http://olimex.com/dev/arm-usb-ocd.html |
| 14:54.15 | Spida | ? |
| 14:56.40 | Spida | in particular, something that would cause "Error: unable to open ftdi device: unable to fetch product description" |
| 15:15.32 | zoobab | nope |
| 15:15.38 | zoobab | I use onyl urjtag |
| 15:15.45 | zoobab | openocd is too complex to configure |
| 15:15.54 | zoobab | I used it once |
| 15:16.04 | zoobab | It worked on windows and linux |
| 16:01.34 | ali1234 | ius: it that running bada? |
| 16:02.37 | ius | ali1234: nope, limo |
| 16:03.04 | ius | and it needs to begone, hence jtag (and to recover a phone with a hosed bootloader) ;) |
| 16:03.18 | ius | but it's not _really_ working out yet, sadly |
| 16:04.04 | ius | I've got a new log, tthe other might have been a bad connection. It should be fine now, though |
| 16:04.08 | ius | http://pastie.org/842409 |
| 16:04.23 | ali1234 | indeed, that does look like a bad connection to me |
| 16:04.36 | ali1234 | if it's totally borked you generally would get nothing but zeros |
| 16:04.49 | ali1234 | at least that's the result i used to get on openwince-jtag |
| 16:05.34 | ali1234 | i just happened across the jtag pins for my omap850 phone, hoping to get debugging going one day, and to replace windows mobile :) |
| 16:39.00 | ius | :) |
| 16:39.17 | ius | ali1234: Was the bad connection remark regarding my first or the log I just pased? |
| 16:59.57 | ius | hm seems it found a TAP now, might be a bad connection |
| 17:00.07 | ius | Info : JTAG tap: auto0.tap tap/device found: 0x17f4c05f (mfg: 0x02f, part: 0x7f4c, ver: 0x1) |
| 17:00.22 | ius | Is there a list of mfgs/parts somewhere? |
| 17:03.39 | thomasg | should the turtelizer work with the free libftdl? |
| 17:04.07 | thomasg | same target here, only openocd doesn't even see a jtag device behind the turtelizer |
| 17:15.13 | ali1234 | ius: the first log |
| 17:16.04 | ali1234 | ius: i know that linux low level stuff uses the jtag IDs to identify cpus |
| 17:33.23 | ius | Well, confirmed my adapter is making bad contact |
| 17:51.04 | *** join/#openjtag toi (~toi@d54C2A96D.access.telenet.be) |
| 19:27.21 | *** join/#openjtag Weaselweb_ (~quassel@2001:6f8:9e4:123:21a:92ff:fe5a:1409) |
| 21:01.47 | ius | Got something to work (finds some TAPs?) although it's still throwing errors at me: http://pastie.org/843038 |
