transport: allow transport name jtag/swd for hla and dapdirect
The transport used on adapter's wires is either 'jtag' or 'swd' but, depending on the adapter, in the command 'transport select' we have to use either 'jtag' or 'swd' or the similar 'hla_jtag', 'hla_swd', 'dapdirect_jtag' or 'dapdirect_swd'. This becomes cumbersome when we just want to change adapter and we get forced to modify the 'transport select' command too. There is no reason for an adapter driver to support two of the similar transports. In fact 'dapdirect' one is a superset of the 'hla', and the native 'jtag' or 'swd' is a superset of the 'dapdirect' one. While the adapter could support more than one similar transports, its adapter driver should only support the most complete of these similar transports. Modify the 'transport select' code to accept 'jtag' or 'swd' for the 'dapdirect' and the 'hla' adapters too. Issue a deprecated message for the old 'dapdirect' and 'hla' transport names. In command 'transport list', print only the transport names that can be selected through 'transport select' skipping information about 'dapdirect' and 'hla' versions and avoid duplicated entries. This improvement was listed in the TODO file. Update it! Change-Id: I626b50e7a94c141c042eab388cd1ffe77eb864c2 Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com> Reviewed-on: https://review.openocd.org/c/openocd/+/8677 Tested-by: jenkins
This commit is contained in:
@@ -3783,10 +3783,8 @@ JTAG supports both debugging and boundary scan testing.
|
||||
Flash programming support is built on top of debug support.
|
||||
|
||||
JTAG transport is selected with the command @command{transport select
|
||||
jtag}. Unless your adapter uses either @ref{hla_interface,the hla interface
|
||||
driver} (in which case the command is @command{transport select hla_jtag})
|
||||
or @ref{st_link_dap_interface,the st-link interface driver} (in which case
|
||||
the command is @command{transport select dapdirect_jtag}).
|
||||
jtag}. This command has to be used also for @ref{hla_interface,the hla interface
|
||||
driver} and @ref{st_link_dap_interface,the st-link interface driver}.
|
||||
|
||||
@subsection SWD Transport
|
||||
@cindex SWD
|
||||
@@ -3799,10 +3797,8 @@ Flash programming support is built on top of debug support.
|
||||
(Some processors support both JTAG and SWD.)
|
||||
|
||||
SWD transport is selected with the command @command{transport select
|
||||
swd}. Unless your adapter uses either @ref{hla_interface,the hla interface
|
||||
driver} (in which case the command is @command{transport select hla_swd})
|
||||
or @ref{st_link_dap_interface,the st-link interface driver} (in which case
|
||||
the command is @command{transport select dapdirect_swd}).
|
||||
swd}. This command has to be used also for @ref{hla_interface,the hla interface
|
||||
driver} and @ref{st_link_dap_interface,the st-link interface driver}.
|
||||
|
||||
@deffn {Config Command} {swd newdap} ...
|
||||
Declares a single DAP which uses SWD transport.
|
||||
@@ -10889,7 +10885,7 @@ baud with our custom divisor to get 12MHz)
|
||||
@item OpenOCD invocation line:
|
||||
@example
|
||||
openocd -f interface/stlink.cfg \
|
||||
-c "transport select dapdirect_swd" \
|
||||
-c "transport select swd" \
|
||||
-f target/stm32l1.cfg \
|
||||
-c "stm32l1.tpiu configure -protocol uart" \
|
||||
-c "stm32l1.tpiu configure -traceclk 24000000 -pin-freq 12000000" \
|
||||
|
||||
Reference in New Issue
Block a user