On Sat, Feb 21, 2009 at 8:57 PM, Dirk Behme <[email protected]> wrote: > Hi Kees, > > do you kindly like to have a look to urjtag patch in attachment? I'm not > sure about it and like to hear your expertise! > > The patch applies against an already configured urjtag (it patches the > Makefiles created by configure) and introduces an additional 'omap3' > command. Executing it, output is: > > -- cut -- > jtag> cable Flyswatter > Connected to libftdi driver. > jtag> omap3 > Running OMAP3 init ... > OMAP3 ICEPICK IDCODE: 00001011011110101110000000101111 (0x0B7AE02F) > OMAP3 ICEPICK IDCODE: 00010110111101011100000001011110 (0x16F5C05E) > jtag> > -- cut -- > > If you look at the code in src/tap/omap3.c in omap3() function the first > IDCODE is output _before_ and the second _after_ my understanding of TI's > ICEPICK sequence is done. > > As you can see second IDCODE is shifted by one bit! This might mean that > additional DR with bit length 1 is inserted (?). What do you think? Yes, This is interesting. specialy because you did not issue the add_part command. issuing the add_part command without configuring the icepick might have the same kind of behavior.
> > Next test would be to try to read ARM's IDCODE, but I don't know at what DR > to look for this (assuming that ARM TAP is really inserted). From Strictly speaking it's not the ARM TAP. The DAP is an interface to the ARM AHB bus and therefore allows direct access to the device memory and peripherals. googling fo "dap ahb" gives some usefull links (I am reading into that ATM). Thanks for the code I will try it out Greetings _______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
