You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-7Lines changed: 10 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,6 +8,8 @@ This project transform VS Code to a great IDE that can be used with STM32CubeMX
8
8
9
9
Debug capabilities are somehow limited, but can be good enough for most simple projects - see below.
10
10
11
+
[](https://www.youtube.com/watch?v=rWjb43kLHdQ)
12
+
11
13
## How does it work?
12
14
Scripts generate all necessary VS Code workspace files ('c_cpp_properties.json', 'tasks.json' and 'launch.json') that IDE needs for autocomplete and compile/build/debug/download actions. New 'Makefile' is generated from CubeMX and user data on each update. All user settings are stored and can be changed in one file: 'c_cpp_properties.json'.
13
15
@@ -34,7 +36,8 @@ This is needed for debug purposes and workspace file generation scripts.
34
36
This file is (recommended by ST) downloaded from [Keil official page](https://www.keil.com/dd2/pack/). Just search for your chosen STM32 CPU family (ex.: STM32F0...), download and unpack with any archive software.
35
37
I recommend to unpack it in the same directory as other GNU Eclipse tools (eg: *%userprofile%\AppData\Roaming\GNU MCU Eclipse*) so everything is neatly organised in one place and files can be reused in other projects (this files will not be changed).
36
38
37
-
At the end, folder structure should look like this: TODO IMAGE
39
+
At the end, folder structure should look like this:
0 commit comments