On Wednesday 20 January 2010, Alexei Babich wrote: > > scan_chain > TapName Enabled IdCode Expected IrLen IrCap IrMask > -- ------------------- -------- ---------- ---------- ----- ----- ------ > 0 imx35.etb Y 0x2b900f0f 0x2b900f0f 4 0x01 0x0f > 1 imx35.cpu Y 0x07b3601d 0x07b3601d 5 0x01 0x1f > 2 imx35.whatchacallit Y 0x00000000 0x00000000 4 0x00 0x00 > 3 imx35.sdma Y 0x0882601d 0x0882601d 5 0x01 0x1f > --- > > Thus, the sequence of TAP-s: etb-> cpu-> whatchacallit-> sdma, if I > understand correctly. > But Freescale Support once sent him a letter stating the following: > --- > ... i.MX35 has 4 devices on it's JTAG scan chain as follows : > > TYPE IR length > ------------ ------------- > ETMBUF 4 > ARM11 5 > SDMA 4 > SJC 5 > --- > > Is there somewhere errors imx35.cfg?
Anything with a "whatchacallit" is buggy by definition. :) I suspect most of the i.MX scan chains have mislabeled the TAPs that weren't provided by ARM. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
