| 01:51.01 | *** join/#openjtag _julian_ (~quassel@dslb-088-070-164-051.pools.arcor-ip.net) |
| 02:10.56 | *** join/#openjtag steve|m1 (~steve@p4FD46D5A.dip.t-dialin.net) |
| 03:59.48 | *** join/#openjtag Rangasamee_ (~mjampala@c-98-247-244-55.hsd1.wa.comcast.net) |
| 04:03.19 | *** join/#openjtag Rangasamee (~mjampala@c-98-247-244-55.hsd1.wa.comcast.net) |
| 05:23.22 | *** join/#openjtag Weaselweb (~quassel@2001:6f8:9e4:123:21a:92ff:fe5a:1409) |
| 06:29.07 | *** join/#openjtag matthsu (~matt@61-30-10-70.static.tfn.net.tw) |
| 09:03.34 | *** join/#openjtag lilalinux (znc@80.69.39.131) |
| 09:03.42 | lilalinux | Aloha |
| 09:03.45 | lilalinux | does anyone know the jtag instruction register length of ftdi2232d |
| 09:31.43 | *** join/#openjtag nslu2-log_ (~nslu2-log@limax.nslu2-linux.org) |
| 10:10.51 | *** join/#openjtag pirho (debian-tor@gateway/tor-sasl/pirho) |
| 10:11.27 | *** part/#openjtag pirho (debian-tor@gateway/tor-sasl/pirho) |
| 11:39.21 | *** part/#openjtag lilalinux (znc@80.69.39.131) |
| 12:41.44 | *** join/#openjtag turboj (~turboj@brln-4db8696f.pool.mediaWays.net) |
| 15:18.26 | *** join/#openjtag mjk (~mjk@p54B149DC.dip.t-dialin.net) |
| 15:18.29 | mjk | Hi folks! |
| 15:19.55 | mjk | Oh jeez ... whenever I have a problem and I'm going to ask on IRC, I immediately find a solution. %-) |
| 16:11.24 | russell-- | where's the ... there it is! |
| 18:21.16 | mjk | :-) |
| 18:41.57 | *** join/#openjtag pupy (~pupy@22.Red-79-150-205.dynamicIP.rima-tde.net) |
| 18:42.01 | pupy | hello |
| 18:42.37 | pupy | can someone solve me a question? I'm doing a jtag adapter with an 8-bit microcontroller |
| 18:43.08 | pupy | I can read it's IDCODE and it matches what the datasheet says, but my problem arises with shifting data into the tap |
| 18:44.00 | pupy | initially, I'm trying to shift in the IDCODE instruction, to be read back again, so I know I have it working in both directions, but I'm never successfull with the shifting-in part |
| 18:45.01 | pupy | also, for example, when shifting out the IDCODE upon power up from the shift-dr register, though TDO, I get 0x1 on TDI, what I don't understand about that 0x1 is |
| 18:45.50 | pupy | whether I'm supossed to save it and feed it back later? I also get other bytes for other operations in the opposite regsiter I'm working with (TDI/TDO) |
| 18:48.33 | pupy | or if anybody could provide some sort of verbose log of a jtag device in operation it would be very helpful as well |
| 19:36.48 | *** join/#openjtag flyhorse|linux (~flyhorse|@183.22.238.26) |
| 20:18.37 | *** part/#openjtag pupy (~pupy@22.Red-79-150-205.dynamicIP.rima-tde.net) |
| 21:09.10 | ccole | .wc |
| 21:09.11 | *** part/#openjtag ccole (~cole@coledd.com) |