New STM32 VSCode extension V2.0.0 released

[Nawres GHARBI]

Changelog

Version 2.0.0

• V2.0.0 implies a breaking change: CMake project generation has been moved from VS Code to STM32CubeMX v6.11.0 (and later).
  • VS Code solution no longer has dependency on STM32CubeIDE (.cproject-files)
  • VS Code solution no longer relies on STM32CubeIDE provided toolchains and debugger tools
  • VS Code solution no longer has dependency on vcpkg,
• Added support to import STM32CubeMX v6.11.0 CMake projects and bootstrap edit/compile/debug in VS Code
• Added support to create empty projects
• Depends on STM32CubeCLT v1.15.0 for empty project creation, build and debug tools
• Documentation update: The User Guide has increased coverage
• Better OS platform support

 

https://marketplace.visualstudio.com/items?itemName=stmicroelectronics.stm32-vscode-extension

[Southbranch]

I like the VS Code extension a lot, but here here are a couple of things I miss from the STM32CubeIDE:

Run Without Debugging

In order to execute this from the VS Code top menu, I currently need to do these steps:

1. Stop the current MCU from running using Shift + F5 (if it is running)
2. After compiling and flashing with "Run Without Debugging, manually reset the device on the hardware in order to start executing.

It all works but is a bit irritating since both these two steps works seamless in CubeIDE.

Is this a bug or just some settings that needs to be fixed?

 

“Clean Build” on the Run menu

There is no such thing on the Run menu which is a bit annoying.

Also, a simple “Build” would be nice to have in the Run menu.

 

[mattias norlander]

---

@Southbranch wrote:

...

Run Without Debugging

...

It all works but is a bit irritating since both these two steps works seamless in CubeIDE.

Is this a bug or just some settings that needs to be fixed?

It is more of embracing a philosophical change. In VS Code you work more with keyboard shortcuts then with using your mouse to click on GUI buttons. Many developers would argue that this is more ergonomic / efficient. But the down-side is getting used to this and to learn the keyboard shortcuts... To make a complete answer on this topic for anyone reading this thread:

Today our VS Code extensions generates a tasks.json file (unless it already exist in your project, then we don't want to overwrite your stuff...) which provides a "task" labeled STM32: CubeProg: Flash project (SWD)

This is just a template we provide, feel free to modify to your needs!

To perform a "flash and reset" you can execute this task.
Executing this task can be done by "clicks" or by keyboard shortcuts.
If you choose the "click approach", then there will be several clicks since there is no dedicated button... 

• Option1: By "clicking": Terminal > Run Task... > CubeProg: Flash Project (SWD)
  

 

• Option2 via Run Task keyboard shortcut:
  • CTRL + P
  • Type: "Task CubePro..." <-- You will notice that the menu auto-suggests tasks matching your pattern.

 

• Option3: Pre-installed keyboard shortcut:
  • CTRL+ALT+F <-- This will immediately execute the same task

Also please notice that their are tasks named "Clean project" and "Build project". Option3 is the most efficient...
The other options require more than 1 user interactions.

[lexcibien]

Hi there!

Having some problems with the off box VS Code Extension,

i have to install ninja build, since the program won't compile, cant't say it's my case or the program doesn't install itself.

Next on my STM32F411CEUx_FLASH.ld i receive errors on this archive, which GPT help me notice where it says that it's missing RAM parameters, which i highlighted where it lacks.

The archive is annexed down.

Then it compiles and debug correctly.

[thealbertdev]

Can static library cmake-based projects be created?

[mattias norlander]

From MX or from VS Code itself? The answer is "no" regardless, just curious to hear more about the use case you are looking for. We have had internal discussions. Nothing planned. But let us know what you want to achieve and we have a better chance to do a proper solution! :)

[herbert]

I must say that I am very dissatisfied. At our university we have used STM32CubeIDE for many years now in lectures, seminars and practical exercises, partly because of the good usability for casual users like students. The actual changes have more or less ripped this apart and make using the STM32 ecosystem much more complicated for them. I am not at all happy with the new version. Seems we will be stuck now at V1.19.0 for quite some time to come... 

Herbert

[Cartu38 OpenDev]

@herbert for my own understanding what are you complaining about?
I're fully allowed to share your mind but I'm confused about your message.

Here this forum is about STM32CubeIDE VSCode solution while discussing about V1.19.0 I've feeling you're pointing to STM32CubeIDE Eclipse based solution. Are we comparing apples and peers or ? ... ok products naming is maybe confusing a bit but please could you confirm / add more details about your comment?:

• Confirm about what we are discussing
• Add more details to complain ... if none not sure will help to get answers

[herbert]

Sorry, I fell into the wrong thread. Actually I was complaining about STM32CubeIDE Eclipse based solution not automatically supporting CubeMX any more.

Herbert