The CMSIS-DAP driver automatically identifies the target CPU. It uses the default probe configuration file, if there is one. This works best if there is only one CPU present.

Specifies that the probe configuration file needs to be overridden, or that there are several target CPUs.

Specify how to find the target CPU.

Specify a probe configuration file to be used instead of the default probe configuration file that comes with the product package.

Specify how to find the target CPU.

Uses the JTAG interface.

Uses the SWD interface.

Automatically uses the highest possible frequency for reliable operation.

Synchronizes the clock to the processor clock outside the core. Works only with Arm devices that have the RTCK JTAG signal available.

Sets the JTAG and SWD communication speed to the selected frequency.

If there are JTAG communication problems or problems in writing to target memory (for example during program download), these problems might be resolved if the speed is set to a lower frequency.

Specifies that the debug system consists of more than one CPU.

If the debug system is a multi-drop SWD, specify the Multidrop ID (in hexadecimal notation) of the DAP where your CPU is located.

If the debug system is a JTAG scan chain, specify the Target number TAP (Test Access Port) position of the device you want to connect to. The TAP numbers start from zero. If there are several CPUs at the TAP position, you also need to specify the CPU number on target.

Specifies that the target has several CPUs.

If the debug system is a multicore SWD, specify the CPU number on the DAP.

If the debug system is a JTAG scan chain and there are several CPUs at the TAP position, specify the CPU number on the TAP.