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 <dbrownell@users.sourceforge.net>
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user