335bafbb25
I looked through all the target configs after stripping comments and such from them with sed to see what jtag-specific commands can appear first, and it looks like all the meaningful combinations should be covered. Change-Id: I8d543407b7f4ac8aca7354ecd50e841c8a04d5f3 Signed-off-by: Paul Fertser <fercerpav@gmail.com> Reviewed-on: http://openocd.zylin.com/2179 Tested-by: jenkins Reviewed-by: Andreas Fritiofson <andreas.fritiofson@gmail.com>
31 lines
1.1 KiB
Tcl
31 lines
1.1 KiB
Tcl
# ARM Debug Interface V5 (ADI_V5) utility
|
|
# ... Mostly for SWJ-DP (not SW-DP or JTAG-DP, since
|
|
# SW-DP and JTAG-DP targets don't need to switch based
|
|
# on which transport is active.
|
|
#
|
|
# declare a JTAG or SWD Debug Access Point (DAP)
|
|
# based on the transport in use with this session.
|
|
# You can't access JTAG ops when SWD is active, etc.
|
|
|
|
# params are currently what "jtag newtap" uses
|
|
# because OpenOCD internals are still strongly biased
|
|
# to JTAG .... but for SWD, "irlen" etc are ignored,
|
|
# and the internals work differently
|
|
|
|
# for now, ignore non-JTAG and non-SWD transports
|
|
# (e.g. initial flash programming via SPI or UART)
|
|
|
|
# split out "chip" and "tag" so we can someday handle
|
|
# them more uniformly irlen too...)
|
|
|
|
if [catch {transport select}] {
|
|
echo "Info : session transport was not selected, defaulting to JTAG"
|
|
transport select jtag
|
|
}
|
|
|
|
proc swj_newdap {chip tag args} {
|
|
if {[using_jtag]} { eval jtag newtap $chip $tag $args }
|
|
if {[using_swd]} { eval swd newdap $chip $tag $args }
|
|
if {[string equal [transport select] "cmsis-dap"]} { eval cmsis-dap newdap $chip $tag $args }
|
|
}
|