On Saturday 03 October 2009, John Rigby wrote: > > 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.
Ah, that needs to be fixed then. > 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. I'd not be so sure. Let's try fixing at least the known bad IR length in your config, and the bad message, first. We don't actually *know* that you've got a bad IR capture in the picture ... where we *do* know that some of your IR lengths are very wrong. > The i.mx31 has the same issue so I guess this should be reverted or some > different way of ignoring this should be added. Which issue is it that the iM31 has? _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
