David, Thanks for the info. I'm slowly making progress.
On Fri, Oct 2, 2009 at 4:58 AM, David Brownell <[email protected]> wrote: ...... > > I'm not sure why that diagnostic > > Error: imx25.cpu: IR capture error; saw 0x3E1011 not 0x..1 > > is there; it looks bizarre, that *is* an LSB of b0001, it's > the next bits that are odd. > This diagnostic is misleading. It does not give the position where it was expecting the 01. The string is the entire captured data. The right most 1 is the first tap. The next is the second tap and the 0 is the funky whatchamacallit tap. Your patch on 9/29 removed code that ignored bad capture codes for taps with no idcodes: - Remove the oddball limitation that invalid capture LSBs trigger errors only for TAPs that support IDCODE. The i.mx31 has the same issue so I guess this should be reverted or some different way of ignoring this should be added. John > - Dave >
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
