VS-Code-STM32-IDE | Use VS Code as STM32 IDE with CubeMX

by damogranlabs C Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | VS-Code-STM32-IDE Summary

VS-Code-STM32-IDE is a C library typically used in Plugin, Visual Studio Code applications. VS-Code-STM32-IDE has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

This project transform VS Code to a great IDE that can be used with STM32CubeMX tool to create a projects without any limitations and code size restrictions, without any bloatware and fast user setup (once all prerequisites are installed). Project is based on python scripts and is therefore fully customizable. OpenOCD tool and Cortex-Debug VS Code plugin is used for debug purposes. Debug capabilities are somehow limited, but can be good enough for most simple projects - see below. Keil project import script available. See README_KEIL_IMPORTER.

Support

Quality

Security

License

Reuse

Support

VS-Code-STM32-IDE has a low active ecosystem.

It has 209 star(s) with 48 fork(s). There are 20 watchers for this library.

It had no major release in the last 6 months.

There are 7 open issues and 33 have been closed. On average issues are closed in 35 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of VS-Code-STM32-IDE is current.

Quality

VS-Code-STM32-IDE has 0 bugs and 0 code smells.

Security

VS-Code-STM32-IDE has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

VS-Code-STM32-IDE code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

VS-Code-STM32-IDE is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

VS-Code-STM32-IDE releases are not available. You will need to build from source code and install.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of VS-Code-STM32-IDE

Get all kandi verified functions for this library.

VS-Code-STM32-IDE Key Features

No Key Features are available at this moment for VS-Code-STM32-IDE.

VS-Code-STM32-IDE Examples and Code Snippets

No Code Snippets are available at this moment for VS-Code-STM32-IDE.

Community Discussions

Trending Discussions on VS-Code-STM32-IDE

Is there a way on VS Code to import Makefile projects?

QUESTION

Is there a way on VS Code to import Makefile projects?

Asked 2020-Feb-06 at 14:55

As the title said, can I populate automatically c_cpp_properties.json from an existing Makefile?

Edit:

For others trying to import makefiles, I have found a set of scripts that perform exactly what I wanted to achieve, the management of STM32 embedded projects through VS Code. If you dig into the scripts folder you can find the make parser and the VSCode project files populator.

Here the repo, enjoy!

...

ANSWER

Answered 2018-Dec-08 at 22:11

This answer may not entirely give you what you want, but hopefully it helps you setting up your VS Code environment.

In your question title, you mention "Makefile projects", which is an indication that you have the wrong impression that (GNU) Makefiles capture project settings in a way similar to Visual Studio project files do. Makefiles do not work like that and the short answer to your question is No, there does not seem to be a way to "import" Makefiles into VS Code and have it automatically set values in your c_cpp_properties.json file.

Having said that, there are some other mechanisms that may help you getting started with VS Code in your situation, depending on the other elements you have in your toolchain.

VS Code works with the premise that it opens one or more directories in your file system. When you do so, it will automatically scan all its subdirectories, display the tree and do linting (if enabled) to detect problems. Indeed, include directories need to be added manually to your c_cpp_properties.json file but to add all your subdirectories recursively to the list of include directories, you can use the expression

Source https://stackoverflow.com/questions/53674529

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install VS-Code-STM32-IDE

Install procedure is simple since all needed files can be downloaded online and setup shouldn't take no more than 5 minutes. It is strongly advised use the default recommended paths while installing the following tools and to use non-spaced paths - avoiding unwanted problems. See this issue. Python There are many posts how to install python. This project needs a valid python or python3 terminal command to execute tasks and set up files. Python version 3 or later is required. STM32CubeMX Download and install STM32CubeMX for your system from ST's website. Note that you will need to create an account (it's free) to access the download. Setup is as easy as running the installation executable for your system and following the prompts. Running CubeMX requires java on your system. Enter java -version in your terminal to check it's installed. Important: Latest version of STM32CubeMX has some bugs which (at least some of them) were already reported. Consider using older version until this issues are fixed. Install Cortex-Debug and Python plugin from VS Code extension marketplace This is needed for debug purposes and workspace file generation scripts. Download CPU specific SVD file (System Viewer Description) This file is (recommended by ST) downloaded from Keil official page. Just search for your chosen STM32 CPU family (ex.: STM32F0...), download and unpack with any archive software. I recommend to unpack it in the same directory as the other tools (eg: %userprofile%\AppData\Roaming\GNU MCU Eclipse on windows, or somewhere like the home directory on linux) so everything is neatly organized in one place and files can be reused in other projects (these files will not be changed).

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: