ARM9 cores with an ETB will have a matching ETM.
Hook them both up by default.
---
I couldn't test these -- no iMX2* board! But it's just
copied from a working setup, so I don't think it can
break very badly. To sanity test: get mainline,
start the imx board, "regs" should list a boatload
of registers, "etm info" should describe the module.
tcl/target/imx25.cfg | 7 ++++++-
tcl/target/imx27.cfg | 4 ++++
2 files changed, 10 insertions(+), 1 deletion(-)
--- a/tcl/target/imx25.cfg
+++ b/tcl/target/imx25.cfg
@@ -38,4 +38,9 @@ if { [info exists SDMATAPID ] } {
jtag newtap $_CHIPNAME sdma -irlen 5 -expected-id $_SDMATAPID
set _TARGETNAME $_CHIPNAME.cpu
-target create $_TARGETNAME arm926ejs -endian $_ENDIAN -chain-position
$_TARGETNAME
+target create $_TARGETNAME arm926ejs -endian $_ENDIAN \
+ -chain-position $_TARGETNAME
+
+# trace setup
+etm config $_TARGETNAME 16 normal full etb
+etb config $_TARGETNAME $_CHIPNAME.etb
--- a/tcl/target/imx27.cfg
+++ b/tcl/target/imx27.cfg
@@ -47,3 +47,7 @@ $_TARGETNAME configure -work-area-virt 0
#
arm7_9 dcc_downloads enable
+
+# trace setup
+etm config $_TARGETNAME 16 normal full etb
+etb config $_TARGETNAME $_CHIPNAME.etb
_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development
