irclog2html for #openjtag on 20061122

`01:42.54`	`*** join/#openjtag ka6sox-office (n=ka6sox@nslu2-linux/ka6sox)`
`02:02.10`	`*** join/#openjtag bullet (n=bullet@19.217.62.81.cust.bluewin.ch)`
`02:49.35`	`*** join/#openjtag ka6sox-laptop (n=tom@nslu2-linux/ka6sox)`
`04:18.36`	`*** join/#openjtag ka6sox-laptop (n=tom@nslu2-linux/ka6sox)`
`04:43.06`	`*** join/#openjtag rwhitby (n=rwhitby@nslu2-linux/rwhitby)`
`09:55.32`	`*** join/#openjtag ka6sox (n=ka6sox@nslu2-linux/ka6sox)`
`12:05.26`	`*** join/#openjtag [g2] (n=g2@nslu2-linux/g2)`
`12:06.51`	`vmaster`	`hey [g2]`
`12:07.06`	`vmaster`	`00:12 < [g2]> vmaster I'm guessing flashing works right ?`
`12:07.12`	`vmaster`	`yes, flashing works fine`
`12:07.33`	`[g2]`	`s-w-e-e-t !`
`12:07.34`	`vmaster`	`I've soldered a new 14->20 pin adapter, and this time I could connect to the EP93xx ok`
`12:08.03`	`[g2]`	`vmaster is such a S-T-U-D !`
`12:08.07`	`vmaster`	`but it still behaves weird - it wont find the flash most of the time, with the GW dongle connected`
`12:08.26`	`vmaster`	`but that might be the boards fault`
`12:08.29`	`[g2]`	`I wonder if the timing is a little too tight`
`12:08.54`	`vmaster`	`the EP93xx specifies a TCK-low minimum time of 50ns, the GW dongle pulses it low for 60ns`
`12:09.58`	`[g2]`	`I'm guessing the TCK going low is based on a DPLL`
`12:10.01`	`vmaster`	`don't think that's the problem, though, cause even if the dongle is just connected, with no debugger running, it will blink the Green LED, signaling that it didn't find a valid signature in none of the flash banks`
`12:10.39`	`vmaster`	`more like a problem with Vcc and/or GND`
`12:11.22`	`[g2]`	`GND whould be fine, but pins 2 and 13 may need to bridged to GND`
`12:11.52`	`[g2]`	`could be a voltage issue on VCC`
`12:12.28`	`[g2]`	`what is the EP93XX supplying for VCC ?`
`12:13.34`	`vmaster`	`3.3V`
`12:13.48`	`[g2]`	`hmm... that should be ok`
`12:15.59`	`vmaster`	`hmm, pin2 might be a problem`
`12:16.06`	`vmaster`	`or /the/ problem`
`12:16.21`	`[g2]`	`nod that's why I mentioned them`
`12:22.24`	`[g2]`	`vmaster did you connect a resistor for the LPC test ?`
`12:22.57`	`[g2]`	`or maybe your LPC board doesn't need it`
`12:24.26`	`vmaster`	`resistor?`
`12:24.30`	`vmaster`	`you mean to RTCK?`
`12:24.35`	`vmaster`	`that's already fitted on the board`
`12:26.02`	`[g2]`	`ok`
`12:26.59`	`[g2]`	`vmaster I'd like to try flashing and debugging on the XScale`
`12:28.02`	`vmaster`	`i have to get rid of one last problem with the reset lines`
`12:28.08`	`vmaster`	`these are crucial for the XScale`
`12:28.19`	`[g2]`	`Ok. that's super`
`12:28.27`	`nbd`	`vmaster: hi`
`12:28.29`	`vmaster`	`well, I'm not completely sure if they are problems - could be the STR7, either`
`12:28.31`	`vmaster`	`nbd: hey`
`12:28.35`	`nbd`	`vmaster: still want that hw porn of the wrv54g board?`
`12:28.43`	`vmaster`	`nbd: yeah, sure`
`12:28.50`	`nbd`	`ok, i'll upload it now`
`12:28.53`	`[g2]`	`vmaster you've made tremendous progress :)`
`12:28.56`	`vmaster`	`nbd: cool, thanks`
`12:30.48`	`vmaster`	`ok, resets work fine when connected to the EP93xx, so I guess the reset problems i was seeing were related to the STR7 - many of the small arms deny debugging out of reset`
`12:31.48`	`[g2]`	`ah... so ppl can't just get control of the processor and pull out the code from flash ?`
`12:32.09`	`vmaster`	`yeah`
`12:33.06`	`[g2]`	`does the XScale have hw breakpoints ?`
`12:33.14`	`vmaster`	`two`
`12:33.26`	`[g2]`	`double the pleasure double the fun :)`
`12:33.29`	`vmaster`	`and one or two hw watchpoints, depending on how you use them`
`12:33.49`	`[g2]`	`and is there a tracebuffer ?`
`12:34.42`	`p2-mate`	`I don't think so`
`12:34.45`	`nbd`	`http://nbd.name/wrv/ - first one's up, second one still uploading...`
`12:35.07`	`[g2]`	`p2-mate there the performance monitor block`
`12:35.09`	`nbd`	`i hope they're clear enough`
`12:35.18`	`nbd`	`took me a few tries with my camera`
`12:35.51`	`vmaster`	`there is a tracebuffer`
`12:36.01`	`vmaster`	`256-byte deep`
`12:36.08`	`vmaster`	`not much, but definitely fun`
`12:38.15`	`nbd`	`ok, second picture up`
`12:42.23`	`vmaster`	`great, thanks`
`13:03.04`	`*** join/#openjtag prpplague^2 (n=billybob@72.22.158.17)`
`13:07.48`	`*** join/#openjtag prpplague^2 (n=dave@69.73.251.136)`
`13:58.46`	`*** join/#openjtag dwery (n=dwery@nslu2-linux/dwery)`
`14:02.37`	`*** join/#openjtag bullet (n=bullet@91-70.1-85.cust.bluewin.ch)`
`16:09.15`	`*** join/#openjtag nslu2-log_ (n=nslu2-lo@nslu2-linux/dyoung)`
`16:38.50`	`*** join/#openjtag dwery (n=dwery@nslu2-linux/dwery)`
`16:59.28`	`*** join/#openjtag vmaster_ (i=vmaster@p549B5C79.dip.t-dialin.net)`
`17:12.01`	`vmaster`	`[g2]: i've just committed a new version to the XScale branch, including the GW16012 support`
`17:12.28`	`vmaster`	`let me know when you're ready to give it a try`
`17:14.26`	`[g2]`	`vmaster is ready :)`
`17:14.52`	`[g2]`	`vmaster I'll pull and build`
`17:19.58`	`vmaster`	`./configure --enable-gw16012 (--enable-parport_ppdev if you want to use /dev/parportN instead of direct I/O w/ root privs)`
`17:22.26`	`[g2]`	`vmaster I've got -r 118 for xscale`
`17:22.35`	`vmaster`	`ok`
`17:22.55`	`vmaster`	`ah, you have to ./bootstrap before`
`17:25.24`	`*** join/#openjtag [g2-build] (n=tom@cpe-066-057-008-035.nc.res.rr.com)`
`17:26.58`	`[g2-build]`	`vmaster: Ok I've got r 118 of the xscale and I'm attempting to boostrap`
`17:27.10`	`[g2-build]`	`bootstrap`
`17:30.14`	`[g2-build]`	`src/jtag/Makefile.am:64: warning: automake does not support conditional definition of FT2232FILES in libjtag_a_SOURCES`
`17:30.36`	`[g2-build]`	`is there a specific version of automake ?`
`17:31.17`	`vmaster`	`mhh, not really, but it seems that i have to change the jtag/Makefile.am - so far, only some windoze boxes failed, but it seems this is a more general problem`
`17:32.38`	`[g2-build]`	`I'm not building for FT2232 so can i comment that out ?`
`17:33.10`	`vmaster`	`http://mmd.ath.cx/openocd/XScale_Makefile_am.patch`
`17:33.13`	`[g2-build]`	`but it is a "warning" and there's no "./configure"`
`17:33.23`	`vmaster`	`the wonders of autotools...`
`17:35.31`	`[g2-build]`	`vmaster: that completes`
`17:35.47`	`[g2-build]`	`so now ./configure --enable-gw01612 ?`
`17:35.54`	`[g2-build]`	`or gw16012`
`17:36.43`	`vmaster`	`gw16012`
`17:37.19`	`[g2-build]`	`Ok it built on the mac mini`
`17:37.48`	`vmaster`	`mhh, a Big-Endian mac-mini?`
`17:38.08`	`[g2-build]`	`little endian x86`
`17:38.11`	`vmaster`	`ah, ok`
`17:38.35`	`[g2-build]`	`I've got to boot the celery that's got the parallel port`
`17:39.16`	`[g2-build]`	`brb back`
`17:44.07`	`*** join/#openjtag tibal (n=tibal@tibal.ath.cx)`
`17:50.45`	`*** join/#openjtag [g2-jtag] (n=music@cpe-066-057-008-035.nc.res.rr.com)`
`17:52.08`	`[g2]`	`http://mmd.ath.cx/openocd/XScale_Makefile_am.patch`
`17:55.37`	`[g2-jtag]`	`vmaster, Ok all built on the jtag machine`
`17:58.21`	`[g2-jtag]`	`vmaster, Ok hw all connected`
`17:58.31`	`vmaster`	`[g2-jtag]: http://mmd.ath.cx/openocd/ixp42x_gw.cfg`
`17:58.37`	`vmaster`	`that should work for your board`
`17:58.44`	`vmaster`	`you only have the IXP in the JTAG chain, right?`
`17:58.51`	`[g2-jtag]`	`vmaster, nod`
`17:58.56`	`vmaster`	`you'll have to adjust the "flash bank cfi" line to suit your flash`
`17:59.07`	`vmaster`	`ah, and what type of flash do you use?`
`18:00.48`	`[g2-jtag]`	`It's an Intel TE28F128`
`18:01.02`	`[g2-jtag]`	`JC3120`
`18:01.16`	`vmaster`	`ok, that should work`
`18:01.20`	`[g2-jtag]`	`that's just the chip rev / speed grade`
`18:01.27`	`[g2-jtag]`	`ok`
`18:02.48`	`vmaster`	`there could be all kinds of problems with your bigendian IXP, but nothing that can't be fixed with a few changes`
`18:03.10`	`[g2-jtag]`	`vmaster nod. I'm not worried :)`
`18:03.23`	`[g2-jtag]`	`this is a work-in-progres`
`18:03.24`	`[g2-jtag]`	`s`
`18:03.29`	`vmaster`	`./openocd -f ixp42x_gw.cfg -d (-l <logfile>)`
`18:04.25`	`[g2-jtag]`	`Info: openocd.c:83 main(): Open On-Chip Debugger (XScale branch, 2006-11-22 14:00 CEST)`
`18:04.37`	`vmaster`	`did you run with -d?`
`18:05.29`	`[g2-jtag]`	`<PROTECTED>`
`18:05.29`	`[g2-jtag]`	`Info: openocd.c:83 main(): Open On-Chip Debugger (XScale branch, 2006-11-22 14:00 CEST)`
`18:05.33`	`vmaster`	`ah, ok`
`18:05.40`	`vmaster`	`did it exit?`
`18:05.43`	`[g2-jtag]`	`yeah`
`18:05.43`	`vmaster`	`or is it still running?`
`18:05.49`	`vmaster`	`can you send me the log.txt?`
`18:05.57`	`[g2-jtag]`	`absolutely`
`18:06.37`	`[g2-jtag]`	`Error: configuration.c:121 parse_config_file(): couldn't open config file`
`18:06.51`	`vmaster`	`ah, hehehe`
`18:07.01`	`[g2-jtag]`	`I guess I need it in the doc dir`
`18:07.03`	`vmaster`	`the OpenOCD expects the .cfg in the current working directory`
`18:07.46`	`[g2-jtag]`	`ooh... blinky lights`
`18:09.13`	`vmaster`	`uhm, continously blinking?`
`18:09.15`	`[g2-jtag]`	`vmaster, do you care if I pastebin the log.txt file ?`
`18:09.20`	`[g2-jtag]`	`no stopped`
`18:09.20`	`vmaster`	`that's fine`
`18:09.36`	`[g2-jtag]`	`http://pastebin.ca/255147`
`18:12.28`	`vmaster`	`could you try a few times to see if it stops at the same point?`
`18:12.34`	`[g2-jtag]`	`sure`
`18:14.07`	`[g2-jtag]`	`Ok I ran it 5 more times and 3 are the same but 2 are not`
`18:14.49`	`[g2-jtag]`	`> Debug: jtag.c:1032 jtag_read_buffer(): fields[0].in_value: 0x01ff`
`18:14.49`	`[g2-jtag]`	`> Error: jtag.c:1185 jtag_validate_chain(): Error validating JTAG scan chain, IR mismatch, scan returned 0x01ff`
`18:15.04`	`[g2-jtag]`	`the two that fail don't seem to get started`
`18:16.28`	`vmaster`	`ok, there's a very low-level communication problem`
`18:17.13`	`[g2-jtag]`	`ok`
`18:17.39`	`prpplague`	`[g2-jtag]: what jtag speed are you running at?`
`18:17.52`	`prpplague`	`[g2-jtag]: this a ft2232 based?`
`18:17.56`	`vmaster`	`prpplague: there's only one jtag_speed for the GW16012`
`18:18.08`	`prpplague`	`ahh`
`18:18.16`	`[g2-jtag]`	`prpplague, it runs around 4Mhz`
`18:18.47`	`[g2-jtag]`	`but there are really two modes`
`18:19.15`	`vmaster`	`mhh, i measured 8.3MHz`
`18:20.07`	`[g2-jtag]`	`vmaster ok`
`18:20.31`	`vmaster`	`the chain validation uses single-bit accesses`
`18:20.58`	`vmaster`	`lennert's identify works fine with this device and your board?`
`18:21.06`	`[g2-jtag]`	`vmaster, yeah`
`18:21.59`	`[g2-jtag]`	`./identify_devices`
`18:21.59`	`[g2-jtag]`	`found intel ixp4xx 533 MHz [IR = 7, TCK < 16000000 Hz]`
`18:22.11`	`[g2-jtag]`	`vmaster, that was just run`
`18:22.24`	`vmaster`	`does it work repeatedly?`
`18:22.38`	`[g2-jtag]`	`the identify devices ?`
`18:22.43`	`vmaster`	`yeah`
`18:23.25`	`[g2-jtag]`	`pretty repeatable`
`18:23.36`	`[g2-jtag]`	`I got like 1 or 2 errors in like 25 tries`
`18:23.48`	`[g2-jtag]`	`I think I'm using some older sw too`
`18:23.54`	`[g2-jtag]`	`it's at r 41`
`18:24.48`	`vmaster`	`the dongle you sent me came with a rather long cable - 10 inches or so - do you happen to have a shorter one to test with?`
`18:26.13`	`vmaster`	`jtag_ntrst_delay 500`
`18:26.13`	`vmaster`	`jtag_nsrst_delay 500`
`18:26.38`	`vmaster`	`try adding these two lines to the .cfg - they allow the target to settle after a reset, just in case the reset lines remain asserted too long`
`18:27.30`	`[g2-jtag]`	`vmaster, ok`
`18:28.13`	`[g2-jtag]`	`vmaster, btw identify_devices works like about 98/99 out of 102 times in a row`
`18:29.31`	`vmaster`	`i'll grab something for dinner, be back in 10 minutes`
`18:31.51`	`[g2-jtag]`	`vmaster, ok. THX`
`18:32.21`	`[g2-jtag]`	`with the delays it's slightly different, but same ending result (I can tell the md5sum on log file is different)`
`18:32.34`	`[g2-jtag]`	`but the text initially looks the same`
`18:32.45`	`[g2-jtag]`	`even though I _know_ it's not :)`
`18:33.27`	`[g2-jtag]`	`ok may just a space`
`18:34.01`	`[g2-jtag]`	`31a32`
`18:34.01`	`[g2-jtag]`	`> Debug: gw16012.c:363 gw16012_execute_queue(): sleep`
`18:34.01`	`[g2-jtag]`	`34a36`
`18:34.01`	`[g2-jtag]`	`> Debug: gw16012.c:363 gw16012_execute_queue(): sleep`
`18:34.07`	`[g2-jtag]`	`two extra sleeps`
`18:36.53`	`vmaster`	`heh, yeah, these are for the two delays`
`18:47.05`	`vmaster`	`ok, there really isn't a lot that's happening up to this point:`
`18:47.10`	`vmaster`	`- both reset lines are pulled low`
`18:47.16`	`vmaster`	`s/low/high/`
`18:47.44`	`vmaster`	`<PROTECTED>`
`18:48.03`	`vmaster`	`- the TAP is moved to Shift-IR`
`18:48.59`	`vmaster`	`- nine 1s are scanned in, expecting to see b110000001`
`18:49.07`	`vmaster`	`- the TAP is moved back to TLR`
`18:49.33`	`vmaster`	`- both resets are asserted`
`18:49.37`	`vmaster`	`- nTRST is released`
`18:50.05`	`vmaster`	`- a new instruction is scanned in`
`18:50.09`	`vmaster`	`- a DR scan is executed`
`18:50.42`	`vmaster`	`if the validate chain fails you're not getting to the "both resets are asserted"`
`18:51.02`	`vmaster`	`all of these accesses are done with single-bit accesses`
`18:52.41`	`[g2-jtag]`	`vmaster, Ok`
`18:54.06`	`[g2-jtag]`	`vmaster, it sounds like the first TAP Shift-IR isn't working properly`
`18:54.31`	`vmaster`	`when the chain validate fails, yeah`
`18:55.46`	`[g2-jtag]`	`vmaster, so you expect the first Shift-IR to fail ?`
`18:56.00`	`[g2-jtag]`	`or it's ok that it fails ?`
`18:56.19`	`vmaster`	`no, it must not fail`
`18:56.39`	`vmaster`	`19:17 < [g2-jtag]> > Error: jtag.c:1185 jtag_validate_chain(): Error validating JTAG scan chain, IR mismatch, scan returned 0x01ff`
`18:56.40`	`[g2-jtag]`	`right it shouldn't be failing`
`18:57.11`	`vmaster`	`scanning in all 1s means that the TAP didn't reach Shift-IR`
`18:57.22`	`[g2-jtag]`	`ok`
`18:57.40`	`vmaster`	`TDO is High-Z unless the TAP is in Shift-I/DR, the external pull-up gets you all ones`
`19:09.01`	`vmaster`	`http://mmd.ath.cx/openocd/gw16012_debug.patch`
`19:09.33`	`vmaster`	`this adds debug output of every byte sent or received from the dongle`
`19:13.28`	`[g2]`	`Ok patched, built and executed... e-mail on the way`
`19:14.06`	`vmaster`	`thanks`
`19:16.22`	`[g2]`	`vmaster you're the one that needs the thanking :)`
`19:16.27`	`[g2]`	`you're doing all the work`
`19:28.31`	`vmaster`	`ok, everything looks perfectly fine`
`19:29.13`	`vmaster`	`this seems to be an electrical problem`
`19:29.22`	`vmaster`	`you don't happen to have a scope to look at the lines?`
`19:32.54`	`[g2-jtag]`	`unfortunately no :(`
`19:33.26`	`*** join/#openjtag JMunakra (n=JMunakra@adsl-71-146-126-132.dsl.pltn13.sbcglobal.net)`
`19:33.51`	`[g2-jtag]`	`there could be some kind of timing issue`
`19:34.08`	`[g2-jtag]`	`as I'm curios how lennerts identify works`
`19:34.15`	`[g2-jtag]`	`lennert's`
`19:38.54`	`vmaster`	`it scans tck with tms high five times (this moves the TAP to TLR no matter what state it was in)`
`19:38.54`	`vmaster`	`then moves to Shift-DR`
`19:39.09`	`vmaster`	`and continously shifts bits through`
`19:39.39`	`vmaster`	`it uses less cycles to move in the TAP, reducing the risk of a failure`
`19:40.35`	`JMunakra`	`hey`
`19:40.53`	`JMunakra`	`what are you discussing right now? sorry to crash in like that :)`
`19:41.31`	`JMunakra`	`any new JTAG TAP developments?`
`19:44.27`	`[g2-jtag]`	`vmaster, Ok so there could be some low-level issues that aren't fully worked out`
`19:44.56`	`[g2-jtag]`	`what lennert is doing is forcing the tap back to a known state and operating from there, correct ?`
`19:45.33`	`[g2-jtag]`	`JMunakra, it's a JTAG dongle for an IXP4xx board`
`19:46.14`	`vmaster`	`[g2-jtag]: yeah, but the OpenOCD does exactly the same`
`19:46.47`	`[g2]`	`vmaster well something is different then :)`
`19:47.44`	`[g2]`	`vmaster the code all looks pretty straight forward`
`20:02.34`	`key2`	`I know am off topic but someone has an idea of if it possible ot compile a .exe with gcc (line mingw) but for pocketpc ?`
`20:05.49`	`vmaster`	`http://mmd.ath.cx/openocd/seven_bit_tck_tdi.png`
`20:06.08`	`vmaster`	`that's a capture of a 7-bit transfer using a 100MHz logic analyzer`
`20:06.19`	`vmaster`	`period is exactly 120ns`
`20:06.29`	`vmaster`	`with a 50/50 duty cycle`
`20:07.12`	`vmaster`	`the IXP422 specifies:`
`20:07.20`	`vmaster`	`Tbscl JTAG_TCK low time 50 ns`
`20:07.31`	`vmaster`	`Tbsch JTAG_TCK high time 50 ns`
`20:07.43`	`vmaster`	`Tbsis JTAG_TDI, JTAG_TMS setup time to rising edge of JTAG_TCK 10 ns`
`20:08.23`	`vmaster`	`Tbsih JTAG_TDI, JTAG_TMS hold time from rising edge of JTAG_TCK 10 ns`
`20:08.47`	`vmaster`	`the GW dongle might be pusing this to the limits`
`20:16.35`	`[g2-jtag]`	`vmaster nice capture!`
`20:16.45`	`[g2-jtag]`	`so you'd like to see a shorter cable ?`
`20:17.39`	`vmaster`	`that could help`
`20:17.47`	`vmaster`	`it did improve things here`
`20:18.12`	`vmaster`	`moving from 10 inches to about 4-5`
`20:32.19`	`[g2]`	`vmaster I don't have any other 14-pin cables`
`20:52.52`	`[g2]`	`vmaster THX for all the help. I'll have to play around with the SW a little and look for a shorter cable or maybe buy one`
`20:55.03`	`vmaster`	`[g2]: I just noticed that even if you get past the comms problems you'll run into a bug. For XScale, I have to add support for the "pathmove" jtag command to the GW16012 - that's only a matter of a few minutes, but i completely forgot about it`
`20:55.37`	`vmaster`	`you'll get an "ERROR("BUG: unknown JTAG command type encountered");" when you hit this problem`
`20:55.53`	`[g2]`	`vmaster ok. thx for the heads-up`
`20:56.08`	`vmaster`	`i'm about to leave, but i'll add this first thing tomorrow`
`20:56.34`	`[g2]`	`that'll probably be before I get my cable/comms sorted out :)`
`20:56.47`	`[g2]`	`but THX for all the help and work!`
`20:57.17`	`vmaster`	`thanks for being patient enough to test thist stuff`
`20:57.27`	`vmaster`	`s/thist/this/`
`20:58.59`	`[g2]`	`well I guess one needs to be careful what we ask for :) I wanted a high-speed JTAG device and now I've got one :)`
`21:00.30`	`*** join/#openjtag tibal (n=tibal@tibal.ath.cx)`
`21:06.19`	`[g2]`	`nbd JTAG ?`
`21:06.29`	`nbd`	`yes, and having decent free software to use it :)`
`21:17.43`	`[g2-build]`	`nod :)`
`21:17.50`	`[g2-build]`	`~praise vmaster`
`21:17.58`	`purl`	`All hail vmaster!`
`23:03.51`	`*** join/#openjtag rwhitby (n=rwhitby@nslu2-linux/rwhitby)`
`23:43.07`	`*** join/#openjtag bullet (n=bullet@91-70.1-85.cust.bluewin.ch)`

Generated by irclog2html.pl by Jeff Waugh - find it at freshmeat.net! Modified by Tim Riker to work with blootbot logs, split per channel, etc.