|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Awesome Embedded||3,412||16 days ago||1||unlicense|
|A curated list of awesome embedded programming.|
|Pikapython||1,055||2 days ago||12||mit||C|
|An ultra-lightweight Python interpreter that runs with only 4KB of RAM, zero dependencies. It is ready to use out of the box without any configuration required and easy to extend with C. Similar project: MicroPython, JerryScript.|
|Home||743||23 days ago||81|
|:house: The landing page for .NET nanoFramework repositories.|
|Stm32 Bootloader||696||7 months ago||1||other||C|
|Customizable Bootloader for STM32 microcontrollers. This example demonstrates how to perform in-application-programming of a firmware located on an external SD card with FAT32 file system.|
|Libusb_stm32||591||2 days ago||19||apache-2.0||C|
|Lightweight USB device Stack for STM32 microcontrollers|
|Eide||384||4 days ago||mit||TypeScript|
|An embedded development environment for mcs51/stm8/avr/cortex-m/riscv on VsCode.|
|Stm32cube_mcu_overall_offer||344||a month ago||4|
|This repo describes all STM32 MCU related GitHub projects. The open source offer for the STM32 MCU products|
|Modbus Stm32 Hal Freertos||297||2 months ago||1||lgpl-2.1||C|
|Modbus TCP and RTU, Master and Slave for STM32 using Cube HAL and FreeRTOS|
|Nf Interpreter||263||8 hours ago||28||December 22, 2022||11||mit||C|
|:gear: nanoFramework Interpreter, CLR, HAL, PAL and reference target boards|
|Awesome Embedded Software||225||9 hours ago||cc0-1.0|
|:stars: List of software (HW interfaces, libs, protocols, etc) specifically suitable for resource-constrained Embedded Systems (low-memory and low-power) like 8-bit, 16-bit and 32-bit microcontrollers.|
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:
*) Note: Support for the STLINK/V1 on macOS is limited to 10.14 - 10.15. Due to the deprecation and removal of macOS Kernel Extensions (KEXT) there will be no support for this programmer on macOS 11 or any later version.
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]
Currently known working combinations of programmers and targets are listed in devices_boards.md.
Supported operating systems are listed in version_support.md.
Our tutorial may help you along with some advanced tasks and additional info.
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.
We recommend to install from:
Alternatively one can compile and install from source as described in our compiling manual.
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.
Other Operating Systems:
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.
Please also refer to our Contribution Guidelines.