Re: [Openocd-development] Improve OMAP3 configuration?

[Rick Altherr]

On Mar 17, 2009, at 10:19 AM, Dirk Behme wrote:

Rick Altherr wrote:

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_chain

   TapName            | Enabled |   IdCode      Expected    IrLen
IrCap  IrMask Instr
---|
--------------------|
---------|------------|------------|------|------|------|---------

0x01 | 0x00 | 0x0f

0x01 | 0x0f | 0x3f

0 | omap3.cpu | n | 0x00000000 | 0x0b6d602f | 0x04 | 1 | omap3.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 |

jtag tapenable omap3.cpu

Enabling Cortex-A8 @ OMAP3
Cortex-A8 @ OMAP3 enabled
1

scan_chain

   TapName            | Enabled |   IdCode      Expected    IrLen
IrCap  IrMask Instr
---|
--------------------|
---------|------------|------------|------|------|------|---------

0x01 | 0x00 | 0x0f

0x01 | 0x0f | 0x3f

-- cut --

Looking at this, I wonder

a) if we should add "jtag tapenable omap3.cpu" command to

any manual steps?

0 | omap3.cpu | Y | 0x00000000 | 0x0b6d602f | 0x04 | 1 | omap3.jrc | Y | 0x0b7ae02f | 0x0b7ae02f | 0x06 | configuration 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 do

Yes, it should do this automatically

Any 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.

Same error:

$_CHIPNAME.cpu configure -event examine-end {
   jtag tapenable omap3.cpu
}

results in

invalid command name "omap3.cpu_configure"

That said, I'm not sure if examine-end is an event.

Best regards

Dirk

As asked above: Which event would you use? Which event is the correct one to be executed after OpenOCD initialization is done and all scripts are executed? I.e. which event to use to get the same execution place as if we execute 'jtag tapenable omap3.cpu' manually after startup?

--
Rick Altherr
kc8...@kc8apf.net


 -- Unsigned

This doesn't necessarily need to be an event. You can put an explicit 'init' command in the config and put the tap enable after that. That said, that doesn't integrate well with other configs. I'd need to look into the options. As for the error you are getting, $_CHIPNAME.cpu is only valid after you create that target. The command won't exist until then. "He said he hadn't had a byte in three days. I had a short, so I split it with him."

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development