diff options
| author | David Brownell <dbrownell@users.sourceforge.net> | 2010-10-10 14:41:11 -0700 |
|---|---|---|
| committer | David Brownell <db@helium.(none)> | 2010-10-10 14:41:11 -0700 |
| commit | e3773e3e3d1f1ee0dbb0b69e8babe8419784d1c1 (patch) | |
| tree | 5e9482cf112afba4fc9ca093bdf2f7c2a141ce99 /tcl/cpld | |
| parent | 3864da1ab817acab24c41366d627da9337a7993d (diff) | |
| download | openocd_libswd-e3773e3e3d1f1ee0dbb0b69e8babe8419784d1c1.tar.gz openocd_libswd-e3773e3e3d1f1ee0dbb0b69e8babe8419784d1c1.tar.bz2 openocd_libswd-e3773e3e3d1f1ee0dbb0b69e8babe8419784d1c1.tar.xz openocd_libswd-e3773e3e3d1f1ee0dbb0b69e8babe8419784d1c1.zip | |
swj-dp.tcl (SWD infrastructure #1)
Provide new helper proc that can set up either an SWD or JTAG DAP
based on the transport which is in use -- mostly for SWJ-DP.
Also update some SWJ-DP based chips/targets to use it. The goal
is making SWD-vs-JTAG transparent in most places. SWJ-DP based chips
really need this flexible configuration to cope with debug adapters
that support different transports, without needing new target configs
for each transport or adapter.
For JTAG-DP, callers will use "jtag newtap" directly, as today; only
one chip-level transport option exists.
For SW-DP (e.g. LPC1[13]xx or EFM32, they'll use "swd newdap" directly
(part of an upcoming SWD transport patch). Again, only one transport
option exists, so hard-wiring is appropriate there.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Diffstat (limited to 'tcl/cpld')
0 files changed, 0 insertions, 0 deletions