Open source version of the STMicroelectronics STLINK Tools

Recent new features and bugfixes can be found in the Changelog of this software project.

License

The stlink library and tools are licensed under the BSD-3 License.

Introduction

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
  • on-board on STM32VL Discovery boards
• STLINK/V2
  • transport layer: raw USB commands
  • stand-alone programmer
  • on-board on STM32L Discovery and STM32 Nucleo boards
• STLINK/V2-1
  • transport layer: raw USB commands
  • on-board on some STM32 Nucleo boards
• STLINK-V3
  • transport layer: raw USB commands
  • stand-alone programmer (STLINK-V3SET, STLINK-V3MINI, STLINK-V3MODS)
  • on-board on some STM32 Nucleo boards (STLINK-V3E)

On the user level there is no difference in handling or operation between these different revisions.

The STlink toolset includes:

• st-info - a programmer and chip information tool
• st-flash - a flash manipulation tool
• st-trace - a logging tool to record information on execution
• st-util - a GDB server (supported in Visual Studio Code / VSCodium via the Cortex-Debug plugin)
• stlink-lib - a communication library
• stlink-gui - a GUI-Interface [optional]

Supported operating systems and hardware combinations

Currently known working MCU targets are listed in devices_boards.md.

A list of supported operating can be found in version_support.md.

Tutorial & HOWTO

Our tutorial may help you along with some advanced tasks and additional info.

Installation

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 32-bit).

Alternatively one may 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

Installation from source (advanced users)

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.

Contributing and versioning

• 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.

User Reviews

I hope it's not to out of topic, but I've been so frustrated with AVR related things on OpenBSD, the fact that stlink built out of the box without needing to touch anything was so relieving. Literally made my whole weekend better! I take it's thanks to @Crest and also to the stlink-org team (@Nightwalker-87 and @xor-gate it seems) to have made a software that's not unfriendly to the "fringe" OSes. Thank you <3" - nbonfils, 11.12.2021