Recent new features and bugfixes can be found in the Changelog of this software project.
The stlink library and tools are licensed under the BSD-3 License.
STLink is an open source toolset to program and debug STM32 devices and boards manufactured by STMicroelectronics. It supports several so called STLINK programmer boards (and clones thereof) which use a microcontroller chip to translate commands from USB to JTAG/SWD. There are four generations available on the market which are all supported by this toolset:
- STLINK/v1 (obsolete as of 21-11-2019, continued support by this toolset)
- transport layer: SCSI passthru commands over USB
- stand-alone programmer and present on STM32VL Discovery boards
- STLINK/v2
- transport layer: raw USB commands
- stand-alone programmer and present on STM32L Discovery and Nucleo boards
- STLINK/v2-1
- transport layer: raw USB commands
- present on some STM32 Nucleo boards
- STLINK/v3
- transport layer: raw USB commands
- stand-alone programmer
On the user level there is no difference in handling or operation between these different revisions.
The STlink toolset includes:
- a communication library (libstlink.a),
- a programmer and chip information tool (st-info),
- a flash manipulation tool (st-flash),
- a GDB server (st-util) and
- a GUI-Interface (stlink-gui) [optional]
Currently known working combinations of programmers and targets are listed in devices_boards.md.
Supported operating systems are listed in version_support.md.
The stlink toolset continues to maintain backwards compatibility with the STLINK/v1 programmer.
Please note that on macOS this support is limited to versions 10.13 - 10.15.
Our tutorial may help you along with some advanced tasks and additional info.
Windows:
As of Release v1.6.1 stand-alone Windows binaries are made available (again) on the release page of the project.
Please ensure to select the correct version for your system (i686 or x86_64). The archive file can be unzipped to any desired location as it does not contain any hardcoded paths. However we suggest to move the unzipped application folder to C:\Program Files\ on 32-bit systems and to C:\Program Files (x86)\ on 64-bit systems (the toolset is a 32-bit).
Alternatively one may compile and install from source as described in our compiling manual.
macOS:
We recommend to install from:
Alternatively one can compile and install from source as described in our compiling manual.
Linux:
We recommend to install stlink-tools from the package repository of the used distribution:
Note: As packages distributed via the Debian and Ubuntu repositories differ from our self-maintained deb-package, we recommend to use the latter instead (see link below). It provides the opportunity to handle and fix user-reported package issues directly within the project and is not redundant to any limitations deriving from external maintenance guidelines.
- Debian Linux: (Link)
- Ubuntu Linux: (Link)
- Arch Linux: (Link)
- Alpine Linux: (Link)
- Fedora: (Link)
- Gentoo Linux: (Link)
Other Operating Systems:
- RedHat/CentOS 8: Users can install from EPEL repository
- FreeBSD: Users can install from freshports
When there is no executable available for your platform or you need the latest (possible unstable) version you need to compile the toolset yourself. This procedure is explained in the compiling manual.
- The semantic versioning scheme is used. Read more at semver.org
- Before creating a pull request, please ALWAYS open a new issue for the discussion of the intended new features. Bugfixes don't require a discussion via a ticket-issue. However they should always be described in a few words as soon as they appear to help others as well.
- Contributors and/or maintainers may submit comments or request changes to patch-proposals and/or pull-requests.
- ATTENTION: NEVER EVER use the '#' character to count-up single points within a listing as '#' is exclusively reserved for referencing GitHub issues and pull-requests. Otherwise you accidentally introduce false cross references within the project.
- Please start new forks from the develop branch, as pull requests will go into this branch as well.
Please also refer to our Contribution Guidelines.
Some features are currently missing from the stlink-org/stlink toolset.
Here we would appreciate any help and would love to welcome new contributors who want to get involved:
- Instrumentation Trace Macro (ITM) Cell (#136)
- OTP & EEPROM area programming (#202, #333, #686)
- Protection bits area reading (#346)
- Writing external memory connected to an STM32 controller (e.g Quad SPI NOR flash) (#412)
- MCU hotplug (#449)
- Writing options bytes (region) (#458)
- Enhanced support for STLINKv3 programmer (#820)