rn0107 Stlink Server Stmicroelectronics
rn0107 Stlink Server Stmicroelectronics
Release note
ST-LINK server
Type Summary
Customer support
For more information or help concerning ST-LINK/V2, ST-LINK/V2-1, and STLINK-V3 boards, contact the nearest
STMicroelectronics sales office. For the complete list of STMicroelectronics offices and distributors, refer to the
www.st.com webpage.
Software updates
Software updates and all the latest documentation can be downloaded from the STMicroelectronics support
webpage at www.st.com/en/development-tools/st-link-server.
1 General information
1.1 Overview
The ST-LINK server is an application sharing the debug interface of a single ST-LINK board among several
host applications, typically a debugging tool and a monitoring tool. Of course, two debugging tools cannot
simultaneously control the same target, but both may have access to it if appropriate connection settings are
chosen.
The ST-LINK server also has access to several boards with one single tool to launch and control the debugging of
these boards.
The host application must be able to connect to the ST-LINK server instead of connecting directly to the ST-LINK
USB interface.
Other ST-LINK interfaces (such as Virtual COM port and mass storage, if provided) are not managed through the
ST-LINK server, but may be used simultaneously.
ST-LINK-SERVER interfaces with ST-LINK probes which run on dedicated STM32 microcontrollers based on the
Arm® Cortex®-M processor.
Note: Arm is a registered trademark of Arm Limited (or its subsidiaries) in the US and/or elsewhere.
1.3 Licensing
ST-LINK-SERVER is delivered under the Mix Ultimate Liberty+OSS+3rd-party V1 software license agreement
(SLA0048).
What is new
• Added support of miscellaneous commands for performance enhancement (API extended to version 3).
• Do not enumerate ST-LINK boards (v1, obsolete), as they are not supported.
1. The ST-LINK server provides simultaneous communication channels to a single ST-LINK board (and target
microcontroller behind) but does not manage priorities between client applications. As a consequence, a
new connection attempt might disturb or kill a previously established connection if, for instance, the second
client application drives the reset of the target or stops the core).
The typical use case for sharing target accesses is one application controlling the target (a debugger for
instance), and one application monitoring the target (and connecting without impacting the target state).
2. The SWV (Serial Wire Viewer) feature can not be shared between applications. Only one application is
allowed to control it. The behavior in the case of conflicting applications is not predictable.
In case of instabilities with SWV in shared mode, firstly try the same SWV configuration out of the shared
mode.
3. When connecting to an STM32 target, the protocol (SWD or JTAG) is selected by the first client application
connecting. In further connections, the protocol must be the same (if a JTAG connection is attempted while
an SWD is already set, the new connection fails).
Conversely, the protocol frequency is enforced by the last caller. Any attempt to modify the frequency of one
protocol has no impact on the other.
4. The default connection setting is localhost port 7184. The server only accepts sockets from the local host.
The port may be modified (implementation dependent), however, for correct behavior, all clients must use
the same port. Only one instance of the server must run.
5. On Windows® and Linux®, it is necessary to uninstall a previous version, if present, before installing the new
one.
6. Long commands may result in timeout when done on a target at a very low SWD frequency (5 kHz). Either
increase the SWD frequency or connect to the target in the direct (not shared) mode.
7. ST-LINK/V1 boards (now obsolete) are not supported by the ST-LINK server.
What is new
• Update from libusb 1.0.22 to libusb 1.0.23 to fix ST-LINK detection issue in some USB context
• Modified error messages, especially in case of several running instances
• Allowed commands with a payload greater than 1428 bytes (and up to 6144 bytes) after segmentation
• Partial fix of timeout issue at SWD frequency less than 1 MHz (50/200/500 kHz).
libSTLinkUSBDriver 6.0.0.0 at least is necessary for a full fix. The issue may remain at 5 kHz.
• Enhanced robustness against ST-LINK disconnection
• Updated standalone installer on Linux® for correct downgrade check and suppression of a wrong error
message
What is new
• Improved robustness in case of intensive client connection/disconnection sequences
• Fixed issue preventing installation on macOS® Catalina
• Added license information to the Linux® package
What is new
• Added support for STLINK-V3SET
Revision history
Table 2. Document revision history
Document
Date Changes
revision
Contents
1 General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Host PC system requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.4 Toolset first versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 ST-LINK server 2.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3 Known problems and limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4 Release information for previous releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.1 ST-LINK server 2.0.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2 ST-LINK server 1.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.3 ST-LINK server 1.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.4 ST-LINK server 1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8