![]() ![]() 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). We recommend to install stlink-tools from the package repository of the used distribution: ![]() 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).Īlternatively one may compile and install from source as described in our compiling manual. The archive file can be unzipped to any desired location as it does not contain any hardcoded paths. Please ensure to select the correct version for your system (i686 or x86_64). stlink-gui - a GUI-Interface Īs of Release v1.6.1 stand-alone Windows binaries are made available (again) on the release page of the project.st-util - a GDB server (supported in Visual Studio Code / VSCodium via the Cortex-Debug plugin).st-trace - a logging tool to record information on execution.st-info - a programmer and chip information tool.On the user level there is no difference in handling or operation between these different revisions. on-board on some STM32 Nucleo boards (STLINK-V3E).stand-alone programmer (STLINK-V3SET, STLINK-V3MINI, STLINK-V3MODS).on-board on STM32L Discovery and STM32 Nucleo boards. ![]() transport layer: SCSI passthru commands over USB. ![]() There are four generations available on the market which are all supported by this toolset: It supports several so called STLINK programmer boards (and clones thereof) which use a microcontroller chip to translate commands from USB to JTAG/SWD. General question: any question that is not technicalĪfter your question is answered, please change the flair to "Resolved".Stlink is an open source toolset to program and debug STM32 devices and boards manufactured by STMicroelectronics.(*) At mods' discretion, certain self-promotion submissions from people who contribute to this sub in other ways may be allowed and tagged with the "Self-promo" flairĬomplete rules: /r/embedded/about/rules/ Link flairsĪfter posting a submission, please select a flair: No memes (pictures with superimposed text), shit posts.No spam no commercial posts, links to commercial pages (including crowd funding sites), no employment ads (job offers and requests go to the weekly thread), no self-promotion (*).If asking a question, ask the actual question, fully yet concisely, right in the title.Be civil: do not insult no all-caps, no excessive "!" and "?", please.Questions on employment (career, internship), education (major, certificates), how to start in embedded.Job announcements (outside the monthly job thread).High level software (e.g., C#, Javascript): r/softwaredevelopment, r/software.Single Board computers: r/Raspberry_pi, r/Arduino, r/linux_devices, r/linuxboards.Hardware design that does not include a micro for electronic circuits: /r/AskElectronics.Homework help but make it clear it's homework.This sub is dedicated to discussion and questions about embedded systems: "a controller programmed and controlled by a real-time operating system (RTOS) with a dedicated function within a larger mechanical or electrical system, often with real-time computing constraints." FAQ ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |