**** BEGIN LOGGING AT Mon Aug 03 02:59:57 2009
Aug 03 22:56:19 <Circuitsoft> Hello - Where can I lookup ARM product ID codes to see if my JTAG interface is properly reading my chip?
Aug 03 22:56:46 <Circuitsoft> JTAG device found: 0x0000b2fb (Manufacturer: 0x17d, Part: 0x000b, Version: 0x0)
Aug 03 22:56:57 <Circuitsoft> Target is NetSilicon ns9215
Aug 03 22:58:06 <roxfan> too many zeroes i think
Aug 03 22:58:19 <Circuitsoft> Yeah. Followed by 
Aug 03 22:58:24 <Circuitsoft> Error validating JTAG scan chain, IR mismatch, scan returned 0x01
Aug 03 23:00:40 <Circuitsoft> Unfortunately, that indicates problems with the config that I'm not sure how to deal with.
Aug 03 23:01:35 <Circuitsoft> roxfan: Know anything about getting scan chains figured out?
Aug 03 23:01:55 <roxfan> barely
Aug 03 23:02:54 <Circuitsoft> Well, Openocd is only finding one device on the scan chain, but the standard ARM9 jtag_device line gives me a scan chain validation error.
Aug 03 23:03:49 <roxfan> you have any other tools?
Aug 03 23:04:03 <Circuitsoft> You mean Hardware or Software?
Aug 03 23:04:26 <roxfan> sw
Aug 03 23:04:39 <Circuitsoft> Well, I intend to eventually use GDB...
Aug 03 23:04:50 <Circuitsoft> But I figured I needed to get OpenOCD working first.
Aug 03 23:05:19 <Circuitsoft> I'm on Debian Lenny
Aug 03 23:05:28 <roxfan> well looks like you need something low-level to figure out the chain
Aug 03 23:05:34 <roxfan> maybe try urjtag
Aug 03 23:10:05 <Circuitsoft> urjtag sees an IR length of 23.
Aug 03 23:10:09 <Circuitsoft> Is that reasonable?
Aug 03 23:13:36 <roxfan> hmm kinda long...
Aug 03 23:13:40 <roxfan> what's the id?
Aug 03 23:13:53 <Circuitsoft> 0x000000000000B2FB
Aug 03 23:14:38 <roxfan> hmm so it sees the same
Aug 03 23:15:13 <roxfan> i'm afraid i'm out of ideas :/
Aug 03 23:18:57 <Circuitsoft> Well, Thanks.
Aug 03 23:19:11 <Circuitsoft> You gave me more avenues to pursue.
Aug 03 23:24:57 <Circuitsoft> Now, I feel dumb.
Aug 03 23:25:05 <Circuitsoft> I just found a switch on the board labeled "Enable OCD"
Aug 03 23:25:09 <Circuitsoft> Turned it on.
Aug 03 23:25:19 <Circuitsoft> Now, I get "Warning: TDO seems to be stuck at 1"
Aug 03 23:26:01 <Circuitsoft> Any ideas, roxfan?
Aug 03 23:26:33 <roxfan> could be wrong wiring
Aug 03 23:27:04 <Circuitsoft> Can't imagine. The board has a 20-pin jtag header, and this dev board has been in use for years.
Aug 03 23:27:42 <Circuitsoft> I just measured VRef, got 3.2v, which is quite within the 2.0-5.0v range supported by my adapter.
Aug 03 23:27:45 <roxfan> what adapter are you using?
Aug 03 23:27:57 <Circuitsoft> Olimex ARM-USB-OCD
Aug 03 23:28:17 <roxfan> hmm that should be supported pretty well...
Aug 03 23:28:33 <roxfan> maybe try older or newer version of ocd....
Aug 03 23:29:10 <Circuitsoft> It's urjtag that's reporting TDO being stuck.
Aug 03 23:29:13 <Circuitsoft> Haven't tried OCD yet.
Aug 03 23:30:36 <Circuitsoft> OpenOCD finds a "0x27926031 (Manufacturer: 0x018, Part: 0x7926, Version: 0x2)"
Aug 03 23:30:47 <Circuitsoft> then repeats that line, then seems to freeze
Aug 03 23:32:13 <Circuitsoft> Actually, it seems to be working.
Aug 03 23:32:28 <roxfan> this is looking better... i think 7926 is an arm926
Aug 03 23:33:04 <Circuitsoft> And, I think the target is an arm926ejs, so...
Aug 03 23:37:05 <roxfan> http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.faqs/3843.html
**** ENDING LOGGING AT Tue Aug 04 02:59:57 2009