On Thu, Oct 02, 2008 at 08:50:32AM +0200, ?yvind Harboe wrote: > On Wed, Oct 1, 2008 at 11:08 PM, Ben Dooks <[EMAIL PROTECTED]> wrote: > > Has openocd been tested recently with ARM1176? I'm running r1013 > > and it is repsonding as so: > > > > Info: JTAG device found: 0x2b900f0f (Manufacturer: 0x787, Part: 0xb900, > > Version: 0x2) > > Info: JTAG device found: 0x07b76f0f (Manufacturer: 0x787, Part: 0x7b76, > > Version: 0x0) > > Error: Error validating JTAG scan chain, IR mismatch, scan returned 0x0e11 > > Error: Could not validate JTAG chain, continuing anyway... > > Warning:value captured during scan didn't pass the requested check: > > captured: 0x11 check_value: 0x01 check_mask: 0x1f > > Warning:in_handler reported a failed check > > Warning:value captured during scan didn't pass the requested check: > > captured: 0x11 check_value: 0x01 check_mask: 0x1f > > Warning:in_handler reported a failed check > > Error: 'arm11 target' JTAG communication error SCREG SCAN OUT 0x00 > > (expected 0x10) > > I'm not convinced that your JTAG chain is configured correctly or that > your JTAG interface is able to communicate with the device. ARM11 is finicky > w.r.t. the JTAG communication in my experience.
I've just had another look at this, and it seems the SMDK6410 was shipped with XDBGSEL=1 (link 1 on cpu module) which selects the external pins of the device. Settign XDBGSEL=0 changed the chain layout, but still is not producing an valid ARM11. Info: JTAG device found: 0x00eb509d (Manufacturer: 0x04e, Part: 0x0eb5, Version: 0x0) Error: 'arm11 target' JTAG communication error SCREG SCAN OUT 0x00 (expected 0x10) Does anyone have any ideas on what is going wrong? -- Ben Q: What's a light-year? A: One-third less calories than a regular year. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
