Repository navigation
Packages Stlink Tools
Flash and debug STM32 targets through an ST-Link probe
- Version recorded: 1.8.0
-
Categories:
programmer - Upstream: https://github.com/stlink-org/stlink
Four programs for ST-Link probes: st-flash writes and reads flash, st- info identifies the probe and target, st-util provides a GDB server, and st-trace reads the SWO trace pin.
ST-Link probes are on the front of every Nucleo and Discovery board and cost a few pounds standalone, which makes them the default way onto an STM32. This is the lighter alternative to openocd for that one family — fewer configuration files and a faster path to a working flash command.
An ST-Link probe. Access comes from the programmer hardware class; the package ships rules for 11 identifiers covering the V1 through V3 probes.
- apt:
stlink-tools
A cloned ST-Link with mismatched firmware reports a target it cannot then talk to, which reads as a broken board rather than a broken probe. st-info --probe is the first thing to run and it distinguishes the two.
STM32 devices in DFU mode present `0483:df11`, the generic STM32
bootloader identifier this catalog refuses to treat as a device — that is dfu-util's job, not this package's.
- probe: apt policy
- strategy: apt_upgrade
Generated from docs/ at commit b2ea01255815. Canonical site: https://renegade-penguin.github.io/Hammunition/. Edit docs/ by pull request, not this wiki.
- Home
- Software by activity
- Activity hubs
- Installation
- Profiles
-
Guides
- Operating
- Modes
- Receiving
- In the field
- Troubleshooting
- Getting started
- Packages
-
Hardware
- Park and wake devices
- SDR receivers and transceivers
- Radios, GPS and mesh
- Security and research hardware
- Programmers
- Laptop radios and camera (parkable)
- LibreVNA (vector network analyser)
- RF security
-
Reference
- The engine
- Coverage
- Inventories
- Hardware measurements
- Verification
- Contributing