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/imx25.cfg | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'tcl/target/imx25.cfg') diff --git a/tcl/target/imx25.cfg b/tcl/target/imx25.cfg index 8f8fa05..6474a85 100644 --- a/tcl/target/imx25.cfg +++ b/tcl/target/imx25.cfg @@ -14,12 +14,12 @@ if { [info exists ENDIAN] } { set _ENDIAN little } -if { [info exists SJCTAPID ] } { - set _SJCTAPID $SJCTAPID +if { [info exists ETBTAPID ] } { + set _ETBTAPID $ETBTAPID } else { - set _SJCTAPID 0x1b900f0f + set _ETBTAPID 0x1b900f0f } -jtag newtap $_CHIPNAME sjc -irlen 4 -expected-id $_SJCTAPID +jtag newtap $_CHIPNAME etb -irlen 4 -irmask 0x0f -expected-id $_ETBTAPID if { [info exists CPUTAPID ] } { set _CPUTAPID $CPUTAPID -- cgit v1.1