From 38e8d60f79fd51424c556e07653713254c2d9b4e Mon Sep 17 00:00:00 2001 From: David Brownell Date: Fri, 13 Nov 2009 13:44:50 -0800 Subject: target.cfg: label ETBs correctly Various cores with an ETB have its TAP misnamed ... either as a boundary scan TAP or as the iMX "Secure JTAG Controller" (which is, among other things, a JRC that could be used to shorten scan chains). Use the correct name for these TAPs, which we can recognize since their IDs were assigned by ARM and these chips all document the presence of an ETB. The 0x2b900f0f is ETB11; the 0x1b900f0f is an older module, just called "ETB". Also shrink the ETB's IR configuration; the default IR-Capture value is fine, and the mask can specify that all four bits are safe to check (per ARM documentation). Signed-off-by: David Brownell --- tcl/target/imx31.cfg | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'tcl/target/imx31.cfg') diff --git a/tcl/target/imx31.cfg b/tcl/target/imx31.cfg index 61a29259..9a2aed32 100644 --- a/tcl/target/imx31.cfg +++ b/tcl/target/imx31.cfg @@ -27,15 +27,15 @@ if { [info exists SDMATAPID ] } { set _SDMATAPID 0x2190101d } -#======================================== -# The "system jtag controller" -# IMX31 reference manual, page 6-28 - figure 6-14 -if { [info exists SJCTAPID ] } { - set _SJCTAPID $SJCTAPID +if { [info exists ETBTAPID ] } { + set _ETBTAPID $ETBTAPID } else { - set _SJCTAPID 0x2b900f0f + set _ETBTAPID 0x2b900f0f } -jtag newtap $_CHIPNAME sjc -irlen 4 -ircapture 0x0 -irmask 0x0 -expected-id $_SJCTAPID + +#======================================== + +jtag newtap $_CHIPNAME etb -irlen 4 -irmask 0xf -expected-id $_ETBTAPID # The "SDMA" - mart controller debug tap # Based on some IO pins - this can be disabled & removed -- cgit v1.2.3