cfg: Don't check BS TAP IDCODE in STM32 configs
Instead of updating these regularly we can just accept any IDCODE for the boundary scan TAP. The only downside might be that it's not immediately obvious if you source a config for the wrong type of STM32. Change-Id: I96d4d81699a491b3a46de3f0d3fd078ffddad4e4 Signed-off-by: Andreas Fritiofson <andreas.fritiofson@gmail.com> Reviewed-on: http://openocd.zylin.com/3385 Tested-by: jenkins
This commit is contained in:
committed by
Freddie Chopin
parent
058ed7a43f
commit
d3445cd146
@@ -37,39 +37,8 @@ if { [info exists CPUTAPID] } {
|
||||
|
||||
swj_newdap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID
|
||||
|
||||
if { [info exists BSTAPID] } {
|
||||
set _BSTAPID $BSTAPID
|
||||
} else {
|
||||
# See STM Document RM0090
|
||||
# Section 38.6.2
|
||||
# STM32F405xx/07xx and STM32F415xx/17xx
|
||||
set _BSTAPID1 0x06413041
|
||||
# STM32F42xxx and STM32F43xxx
|
||||
set _BSTAPID2 0x06419041
|
||||
# See STM Document RM0368 (Rev. 3)
|
||||
# STM32F401B/C
|
||||
set _BSTAPID3 0x06423041
|
||||
# STM32F401D/E
|
||||
set _BSTAPID4 0x06433041
|
||||
# See STM Document RM0383 (Rev 2)
|
||||
# STM32F411
|
||||
set _BSTAPID5 0x06431041
|
||||
# See STM Document RM0386
|
||||
# STM32F469
|
||||
set _BSTAPID6 0x06434041
|
||||
# See STM Document RM0401
|
||||
# STM32F410
|
||||
set _BSTAPID7 0x06458041
|
||||
# STM32F412
|
||||
set _BSTAPID8 0x06441041
|
||||
}
|
||||
|
||||
if {[using_jtag]} {
|
||||
swj_newdap $_CHIPNAME bs -irlen 5 -expected-id $_BSTAPID1 \
|
||||
-expected-id $_BSTAPID2 -expected-id $_BSTAPID3 \
|
||||
-expected-id $_BSTAPID4 -expected-id $_BSTAPID5 \
|
||||
-expected-id $_BSTAPID6 -expected-id $_BSTAPID7 \
|
||||
-expected-id $_BSTAPID8
|
||||
jtag newtap $_CHIPNAME bs -irlen 5
|
||||
}
|
||||
|
||||
set _TARGETNAME $_CHIPNAME.cpu
|
||||
|
||||
Reference in New Issue
Block a user