CMSIS-DAP: DAP_Info

| CMSIS-DAP Version 2.0.0 Interface Firmware for CoreSight Debug Access Port

- Main Page
- Usage and Description
- Reference

All Functions Groups Pages
DAP_Info
General Commands

Get Information about CMSIS-DAP Debug Unit. More...

Get Information about CMSIS-DAP Debug Unit.

The DAP_Info Command provides configuration information about the Debug Unit itself and the capabilities.

DAP_Info Command:

| BYTE | BYTE |
> 0x00 | ID |
|******|******|

- ID: Request Identifier to obtain information in the Response:
  - 0x01 = Get the Vendor ID (string).
  - 0x02 = Get the Product ID (string).
  - 0x03 = Get the Serial Number (string).
  - 0x04 = Get the CMSIS-DAP Firmware Version (string).
  - 0x05 = Get the Target Device Vendor (string).
  - 0x06 = Get the Target Device Name (string).
  - 0xF0 = Get information about the Capabilities (BYTE) of the Debug Unit (see below for details).
  - 0xF1 = Get the Test Domain Timer parameter information (see below for details).
  - 0xFD = Get the SWO Trace Buffer Size (WORD).
  - 0xFE = Get the maximum Packet Count (BYTE).
  - 0xFF = Get the maximum Packet Size (SHORT).

DAP_Info Response:

| BYTE | BYTE | BYTE |
< 0x00 | Len | Info |
|******|******|++++++|

- Len: Info length in bytes.
- Info:
  - a string encoded in US ASCII. Len is the string length including the \x00 terminator. Len = 0 indicates no information.
  - a BYTE value (indicated with Len = 1).
  - a SHORT value (indicated with Len = 2).
  - a WORD value (indicated with Len = 4).

Note
  The ID for Vendor ID, Product ID, and Serial Number may return no string (indicated by Len = 0). In this case the USB Device Information is used to obtain Vendor, Product, and Serial Number.
  Target Device Vendor and Target Device Name are only available on Debug Units with known Target Device. Refer to TARGET_DEVICE_FIXED for more information. If the Target Device is not known no string is returned (indicated by Len = 0).

DAP_Info Response (for ID=0xF0):

The ID=0xF0 Capabilities obtains information about the available interface to the Device. The reply consists of one or two Info bytes with bits that indicate the features of the Debug Unit. The features indicate the command scope of the CMSIS-DAP firmware. If certain features are not available, the debugger should not call the related commands as the may not be implemented. Commands that are not implemented reply with 0xFF instead of repeating the command byte.

| BYTE | BYTE | BYTE *| BYTE |
< 0x00 | Len | Info0 | Info1 |
|******|******|*******|*******|

- Len: 1 = Info0 present, 2 = Info0, Info1 present.

Available transfer protocols to target:

- Info0 - Bit 0: 1 = SWD Serial Wire Debug communication is implemented (0 = SWD Commands not implemented).
- Info0 - Bit 1: 1 = JTAG communication is implemented (0 = JTAG Commands not implemented).

Serial Wire Trace (SWO) support:

- Info0 - Bit 2: 1 = SWO UART - UART Serial Wire Output is implemented (0 = not implemented).
- Info0 - Bit 3: 1 = SWO Manchester - Manchester Serial Wire Output is implemented (0 = not implemented).

Command extensions for transfer protocol:

- Info0 - Bit 4: 1 = Atomic Commands - Atomic Commands support is implemented (0 = Atomic Commands not implemented).

Time synchronisation via Test Domain Timer:

- Info0 - Bit 5: 1 = Test Domain Timer - debug unit support for Test Domain Timer is implemented (0 = not implemented).

SWO Streaming Trace support:

- Info0 - Bit 6: 1 = SWO Streaming Trace is implemented (0 = not implemented).

DAP_Info Response (for ID=0xF1):

The ID=0xF1 Test Domain Timer obtains the parameter information about an optional 32-bit Test Domain Timer that may be used for various time measurements.

| BYTE | BYTE | WORD *****|
< 0x00 | 0x08 | Frequency |
|******|******|***********|

- Frequency: Input frequency of the Test Domain Timer which indicates the resolution of the 32-bit TD_TimeStamp values.