UM2502 Rev 1

15/27

UM2502

STLINK-V3MODS and STLINK-V3MINI functional description

26

8.4

STLINK-V3MODS and STLINK-V3MINI functions

All functions are designed for high performance: all signals are 3.3 V compatible. The

following description concerns STLINK-V3MODS and STLINK-V3MINI except some

mentioned sections and indicates where to find the functions on the boards and connectors.

8.4.1

SWD with SWV

SWD protocol is a Debug/Program protocol used for STM32 microcontrollers with SWV as a

trace. The signals are 3.3 V compatible and may perform up to 24 MHz. This function is

available on CN2 (STLINK-V3MODS) and CN5 (STLINK-V3MINI).

8.4.2

JTAG

JTAG protocol is a Debug/Program protocol used for STM32 microcontrollers. The signals

are 3.3 V compatible and may perform up to 21 MHz. This function is available on CN2

(STLINK-V3MODS) and CN5 (STLINK-V3MINI).

8.4.3

Virtual COM port (VCP)

The serial interface VCP is directly available as a Virtual COM port of the PC, connected to

STLINK-V3MODS and STLINK-V3MINI USB connector CN5. This function may be used for

STM32 microcontrollers. The signals are 3.3 V compatible and may perform from 720 bps to

15 Mbps. This function is available on CN2 (STLINK-V3MODS) and CN5 (STLINK-V3MINI).

8.4.4

Bridge functions (STLINK-V3MODS only)

The STLINK-V3MODS provides a proprietary USB interface allowing the communication

interface may be used to communicate with the target bootloader, but may also be used for

customized needs through its public software interface.All bridge signals are accessible on

CN2.

Bridge SPI

SPI signals are available on CN2 pins 7, 14, 23 and 25.

pull-up resistors on the host application board.

Bridge CAN

CAN logic signals (Rx/Tx) are available on CN2 pins 9 and 10, they may be used as input

for an external CAN transceiver.

Bridge UART

UART signals with hardware flow control (CTS/RTS) are available on CN2 pins 1 to 3 and

11. They need a dedicated firmware to be programmed on the main module before being

used. Without this firmware, the Virtual COM port function must be used instead (no

hardware flow control).