Hi Magnus, Magnus Lundin wrote: > Hi Dirk > > Very good, I think we can commit this immediatleay as a place to collect > the info about A8.
Wow, that was fast :) > I now have a BeagleBoard :), Great! > so testing can be made more efficient, > JTAG solution will be working at the end of the week, strange pinout and > low voltage. I do use http://www.tincantools.com/images/D/Fly%2BBeagle-800x391.JPG?1229714946602 > The magic sequence for unlocking debug registers in the core power domain is > > # Unlock debug register modification access > mww 0x54011FB0 0xC5ACCE55 > # Clear Sticky Power Down status Bit > mdw 0x54011314 > # Check that it is cleared > mdw 0x54011314 > # Now we can read Core Debug Registers at offset 0x080 > mdw 0x54011080 4 > > This works for me with UBoot running, perhaps the Linux kernel will > change some settings, we will see .. Great! Yes, I can confirm that this works! See [1] below. Btw.: Is there an option or a possibility to run a script when I connect e.g. by telnet? I'm a little tired to always type the commands jtag tapenable omap3.cpu target create omap3.cpu cortex_a8 -endian little -chain-position omap3.cpu dap apsel 1 omap3.cpu mww 0x54011FB0 0xC5ACCE55 4 omap3.cpu mdw 0x54011314 omap3.cpu mdw 0x54011314 manually. Many thanks and best regards Dirk [1] Unlock sequence: -- cut -- > jtag tapenable omap3.cpu Enabling Cortex-A8 @ OMAP3 Cortex-A8 @ OMAP3 enabled 1 > target create omap3.cpu cortex_a8 -endian little -chain-position omap3.cpu > dap apsel 1 ap 1 selected, identification register 0x04770002 > omap3.cpu mww 0x54011FB0 0xC5ACCE55 4 > omap3.cpu mdw 0x54011314 0x54011314 00000003 .... > omap3.cpu mdw 0x54011314 0x54011314 00000001 .... -- cut -- _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
