On Mar 17, 2009, at 6:13 AM, Dirk Behme wrote:
Rick Altherr wrote:On Mar 14, 2009, at 12:01 AM, Dirk Behme wrote:With recent SVN at OMAP3 based Beagle we get: -- cut --scan_chainTapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr ---| --------------------| ---------|------------|------------|------|------|------|--------- 0 | omap3.cpu | n | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x00 | 0x0f 1 | omap3.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 | 0x01 | 0x0f | 0x3fjtag tapenable omap3.cpuEnabling Cortex-A8 @ OMAP3 Cortex-A8 @ OMAP3 enabled 1scan_chainTapName | Enabled | IdCode Expected IrLen IrCap IrMask Instr ---| --------------------| ---------|------------|------------|------|------|------|--------- 0 | omap3.cpu | Y | 0x00000000 | 0x0b6d602f | 0x04 | 0x01 | 0x00 | 0x0f 1 | omap3.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 | 0x01 | 0x0f | 0x3f -- cut -- Looking at this, I wonder a) if we should add "jtag tapenable omap3.cpu" command toconfiguration script omap3530.cfg? I think our goal is to access/ debug the ARM, so we should enable access to it by default not needing to doany manual steps?Yes, it should do this automaticallyAny hint where and how to do this in config files? I tried something like $_CHIPNAME configure -event examine-end { jtag tapenable omap3.cpu } in omap3530.cfg but this fails with invalid command name "omap3_configure" with svn:1415. Dirk
The first part would need to be $_CHIPNAME.cpu. That said, I'm not sure if examine-end is an event.
-- Rick Altherr [email protected]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
