From 9f95ff5b6ba01db09552b84a0ab79607060a2666 Mon Sep 17 00:00:00 2001 From: Ali Labbene Date: Wed, 11 Dec 2019 08:59:21 +0100 Subject: Official ARM version: v5.4.0 Add CMSIS V5.4.0, please refer to index.html available under \docs folder. Note: content of \CMSIS\Core\Include has been copied under \Include to keep the same structure used in existing projects, and thus avoid projects mass update Note: the following components have been removed from ARM original delivery (as not used in ST packages) - CMSIS_EW2018.pdf - .gitattributes - .gitignore - \Device - \CMSIS - \CoreValidation - \DAP - \Documentation - \DoxyGen - \Driver - \Pack - \RTOS\CMSIS_RTOS_Tutorial.pdf - \RTOS\RTX - \RTOS\Template - \RTOS2\RTX - \Utilities - All ARM/GCC projects files are deleted from \DSP, \RTOS and \RTOS2 Change-Id: Ia026c3f0f0d016627a4fb5a9032852c33d24b4d3 --- docs/DAP/html/group__DAP__SWD__Sequence.html | 172 +++++++++++++++++++++++++++ 1 file changed, 172 insertions(+) create mode 100644 docs/DAP/html/group__DAP__SWD__Sequence.html (limited to 'docs/DAP/html/group__DAP__SWD__Sequence.html') diff --git a/docs/DAP/html/group__DAP__SWD__Sequence.html b/docs/DAP/html/group__DAP__SWD__Sequence.html new file mode 100644 index 0000000..6e2df91 --- /dev/null +++ b/docs/DAP/html/group__DAP__SWD__Sequence.html @@ -0,0 +1,172 @@ + + + + + +DAP_SWD_Sequence +CMSIS-DAP: DAP_SWD_Sequence + + + + + + + + + + + + + + +
+
+ + + + + + + +
+
CMSIS-DAP +  Version 2.0.0 +
+
Interface Firmware for CoreSight Debug Access Port
+
+
+ +
+
    + +
+
+ + + +
+
+ +
+
+
+ +
+ + + + +
+ +
+ +
+
+
DAP_SWD_Sequence
SWD Commands
+
+
+ +

Generate SWD sequence and output on SWDIO or capture input from SWDIO data. +More...

+

Generate SWD sequence and output on SWDIO or capture input from SWDIO data.

+
Note
The DAP_SWD_Sequence is available for CMSIS-DAP version 1.2 and higher. Refer to DAP_Info for more information on how to query the CMSIS-DAP version.
+

The DAP_SWD_Sequence Command is used to generate special sequences in SWD mode on the pins SWCLK and SWDIO. For example, for SWD multi-drop target selection (see picture) it is required to put the SWDIO pin to input mode (where it is not driven).

+
+SWD_Sequence.png +
+SWD sequence for multi-drop target selection
+
    +
  • For mode=0 (output: SWDIO is driven), the data for the SWDIO pin are part of the DAP_SWD_Sequence Command.
    • +
  • For mode=1 (input: SWDIO is not driven), the data from the SWDIO pin are captured and returned as part of the DAP_SWD_Sequence Response.
    • +
+

DAP_SWD_Sequence Command:

+
| BYTE | BYTE **********| BYTE *********| BYTE ******|
+
> 0x1D | Sequence Count | Sequence Info | SWDIO Data |
+
|******|****************|///////////////|++++++++++++|
+
    +
  • Sequence Count: Number of Sequences
    • +
  • Sequence Info: Contains number of SWCLK cycles and SWDIO mode
      +
    • Bit 5 .. 0: Number of TCK cycles: 1 .. 64 (64 encoded as 0)
      • +
    • Bit 6: reserved
      • +
    • Bit 7: mode: 0=output (SWDIO Data in command), 1=input (SWDIO Data in response)
      • +
    +
    • +
  • SWDIO Data (only for output mode): Data generated on SWDIO
      +
    • One bit for each TCK cycle
      • +
    • LSB transmitted first, padded to BYTE boundary
      • +
    +
    • +
+

DAP_SWD_Sequence Response:

+
| BYTE | BYTE **| BYTE ******|
+
< 0x1D | Status | SWDIO Data |
+
|******|********|++++++++++++|
+
    +
  • SWDIO Data (only for input mode): Data captured from SWDIO
      +
    • One bit for each SWCLK cycle for input mode
      • +
    • LSB received first, padded to BYTE boundary
      • +
    +
    • +
  • Status: Response Status
    • +
+
+
+ + + + -- cgit