**** BEGIN LOGGING AT Mon Feb 08 02:59:57 2010
Feb 08 17:34:38 <prpplague> anyone doing pxa3xx jtag ?
Feb 08 17:46:21 <prpplague> themammal: i assume you are following the info http://www.elinux.org/BeagleBoardJTAG
Feb 08 17:47:49 <themammal> prpplague: I've found a few sources on elinux I've been following this: http://elinux.org/BeagleBoardOpenOCD
Feb 08 17:49:11 <themammal> so I guess as of last month the svn is down: http://openocd.berlios.de/web/
Feb 08 17:49:20 <themammal> so I've been using the git
Feb 08 17:49:50 <themammal> I went through the output pretty thoroughly and it seems like the only errors I'm getting are doc related
Feb 08 17:50:41 <themammal> still the install is incomplete... openocd is there but all the scripts and support is missing
Feb 08 18:53:31 <themammal> prpplague: when I run openocd -f <interface.cfg> -f <board.cfg> I get this:
Feb 08 18:53:34 <themammal> Info:    openocd.c:92 main(): Open On-Chip Debugger (2007-08-21 18:30 CEST)
Feb 08 18:53:34 <themammal> Info:    configuration.c:50 configuration_output_handler(): Command jtag_rclk not found
Feb 08 18:53:34 <themammal> Info:    configuration.c:50 configuration_output_handler(): Command source not found
Feb 08 18:53:35 <themammal> Error:   jtag.c:1461 jtag_init(): No valid jtag interface found ((null))
Feb 08 18:53:35 <themammal> Error:   jtag.c:1462 jtag_init(): compiled-in jtag interfaces:
Feb 08 18:53:35 <themammal> Error:   jtag.c:1465 jtag_init(): 0: ft2232
Feb 08 18:53:37 <themammal> any ideas?
Feb 08 18:54:08 <prpplague> themammal: well what interface.cfg did you specify?
Feb 08 18:54:36 <themammal> flyswatter.cfg
Feb 08 18:55:43 <prpplague> themammal: so you  issued the openocd command using the flyswatter.cfg and specified the path where the file is?
Feb 08 18:55:51 <themammal> right
Feb 08 18:56:01 <themammal> and the same for the beagle board cfg
Feb 08 18:56:14 <prpplague> themammal: what was the actual command you used?
Feb 08 18:57:43 <themammal> prpplague: openocd -f /home/user/flyswatter.cfg -f /home/user/ti_beagleboard.cfg
Feb 08 18:58:13 <prpplague> themammal: did you make some changes to the flyswatter.cfg file?
Feb 08 18:58:42 <themammal> prpplague: no I didn't make any changes
Feb 08 18:59:01 <prpplague> themammal: sounds like something isn't right though
Feb 08 18:59:23 <prpplague> themammal: where did you get the flyswatter.cfg file?
Feb 08 19:00:38 <themammal> prpplague: a couple months ago I successfully installed openocd on a virtualization of ubuntu and all of the cfg's showed up in the install directory under scripts
Feb 08 19:00:46 <themammal> so I grabbed them from there
Feb 08 19:01:36 <prpplague> themammal: can you pastebin your flyswatter.cfg file? http://www.pastebin.ca 
Feb 08 19:04:10 <themammal> prpplague: pastebin.com/d72d867d5
Feb 08 19:05:01 <prpplague> themammal: that looks correct
Feb 08 19:05:10 <prpplague> themammal: might want to check a few things first
Feb 08 19:05:18 <prpplague> themammal: cat /proc/bus/usb/devices
Feb 08 19:05:24 <prpplague> themammal: does the flyswatter show up there?
Feb 08 19:06:55 <themammal> prpplague: yea it shows up
Feb 08 19:07:48 <prpplague> themammal: are you running the command as root?
Feb 08 19:08:08 <themammal> prpplague: http://pastebin.com/d2101c6b6
Feb 08 19:08:30 <prpplague> themammal: yep that looks good
Feb 08 19:08:32 <themammal> prpplague: the openocd command?
Feb 08 19:08:35 <prpplague> themammal: yes
Feb 08 19:08:49 <themammal> prpplague: I think I tried that I'll see if I get a different output
Feb 08 19:09:10 <prpplague> themammal: run it as root with just: openocd -f /home/user/flyswatter.cfg
Feb 08 19:10:23 <themammal> prpplague:  looks like my cable is possibly the culprit ... one sec I'll pastebin
Feb 08 19:10:48 <prpplague> which cable?
Feb 08 19:11:07 <themammal> prpplague: http://pastebin.com/d570df242
Feb 08 19:11:37 <themammal> I don't have the beagle adapter for the flyswatter so I made a cable
Feb 08 19:12:10 <prpplague> themammal: ok that is different that the previous errors you posted
Feb 08 19:12:15 <themammal> yea
Feb 08 19:12:59 <prpplague> themammal: you should be able to try it with the ti_beagleboard.cfg file now
Feb 08 19:13:12 <prpplague> themammal: why didn't you order the adapter kit?
Feb 08 19:13:56 <themammal> prpplague: I didn't order the flyswatter - I just found it lying around the office
Feb 08 19:14:07 * prpplague wonders what office
Feb 08 19:14:17 <prpplague> OH
Feb 08 19:14:22 <prpplague> themammal: hehe you are with buglabs
Feb 08 19:14:31 <themammal> prpplague: yup
Feb 08 19:14:42 * prpplague sent the flyswatter to buglabs
Feb 08 19:14:52 <prpplague> you should a bunch of our other stuff too
Feb 08 19:14:56 <themammal> hah! nice
Feb 08 19:15:21 <themammal> prpplague: well thanks for the hardware and for the help
Feb 08 19:15:37 <prpplague> np
Feb 08 19:15:59 <prpplague> i thought we sent you guys an adapter kit as well for the beagle
Feb 08 19:16:11 <themammal> prpplague: the error with only the ti_beagleboard.cfg is the same as the one I pasted in the channel
Feb 08 19:16:16 <themammal> the first one
Feb 08 19:16:37 <prpplague> themammal: ahh ok, sounds like there is something incorrect in your ti_beagleboard.cfg file
Feb 08 19:17:13 <themammal> prpplague: I looked pretty thoroughly, but it's possible that I missed it 
Feb 08 19:17:34 <prpplague> themammal: can you pastebin the ti_beagleboard.cfg file?
Feb 08 19:17:39 <themammal> prpplague: I'll pastebin that as well
Feb 08 19:18:02 * prpplague has a conference call shortly
Feb 08 19:18:46 <themammal> prpplague: http://pastebin.com/d20e9e23
Feb 08 19:23:23 <prpplague> themammal: yea, something doesn't look correct since openocd complained about both commands you have listed
Feb 08 19:24:43 <themammal> hmm
Feb 08 19:25:18 <themammal> prpplague: well I can double check my cable ... that error from the flyswatter cfg makes me think that it's talking to the flyswatter ok
Feb 08 19:25:26 <themammal> prpplague: is that reasonable assumption?
Feb 08 19:25:53 <prpplague> themammal: yes, sounds like possibly you have a mismatch on the openocd
Feb 08 19:26:11 <prpplague> themammal: might want to check and make sure you don't have multiple copies of openocd installed on your system
Feb 08 19:26:31 <themammal> I'll do a locate and see what I get
Feb 08 19:26:39 <prpplague> themammal: it might be better to use a direct path to your openocd binary
Feb 08 19:27:06 <themammal> I can try that
Feb 08 19:28:04 <themammal> nice
Feb 08 19:28:21 <prpplague> results?
Feb 08 19:28:27 <themammal> looks promising
Feb 08 19:36:42 <themammal> prpplague: http://pastebin.com/d1f51120f
Feb 08 19:37:23 <prpplague> themammal: yea looks like you have a problem with your jtag wiring
Feb 08 19:37:48 <prpplague> themammal: did you use the schematic on the tincantools web site?
Feb 08 19:37:53 <themammal> yea
Feb 08 19:38:22 <themammal> I thought it was strange that on the JTAG adapter board one side of the EMU jumper was grounded but the other side was no connect
Feb 08 19:38:38 <themammal> prpplague: the EMU0 and EMU1 should be pulled high right?
Feb 08 19:39:46 <themammal> I remember looking into this in the OMAP docs, but it's here as well: http://elinux.org/BeagleBoardOpenOCD#Hardware
Feb 08 19:41:09 <prpplague> themammal: emu0 and emu1 are normally pulled high, so you just need to have the jumpers off or on 2-3
Feb 08 19:41:23 <themammal> ah ok
Feb 08 19:42:10 <themammal> prpplague: *classic* problem .... beagle not powered up
Feb 08 19:53:13 <themammal> prpplague: ugh so if I run omap3_dbginit it wants a target argument
Feb 08 19:53:21 <themammal> prpplague: would that be omap3530?
Feb 08 19:54:20 <prpplague> themammal: that's something new , i've never had to use an argument
Feb 08 19:54:35 <themammal> ok Ill look into it
Feb 08 19:56:19 <themammal> prpplague: sorry to keep bothering.. thoughts on these errors? http://pastebin.com/d1a7364ed
Feb 08 19:56:29 * prpplague looks
Feb 08 19:57:21 <prpplague> themammal: yea seems to be getting zeros for the tap id
Feb 08 19:57:34 <prpplague> themammal: i'd double check your jtag adapter 
Feb 08 19:58:02 <themammal> ok thx
Feb 08 19:58:18 <prpplague> np
**** ENDING LOGGING AT Tue Feb 09 02:59:56 2010