FAQs
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Is STM32CubeIDE having a deliver end date?

Go to solution
PScal
Associate III

‎2024-04-22 01:43 AM

Hi STM Team,

we heard at the embeddedWorld 2024 that ST would focus more on a development enviromend integration to VSCode for STM32 microcontrollers. How is that planned and what is the timeline for that? 

Is STM32CubeIDE going to be stopped then? 

best regards

Peer

0 Kudos
1 ACCEPTED SOLUTION

Accepted Solutions
Go to solution
mattias norlander
ST Employee

‎2024-04-22 02:58 AM

Hi PScal,

Valid question! Let's just re-cap for people who were not there, but who may read this thread tomorrow...

The week before EW2024 we release a new version (v2.0.x) of the VS Code extension set. This extension is a fresh start and a clear compatibility break vs the previous version.

  • In the previous version (v1.0.0) Microsoft extensions was in charge of translating CubeIDE .cproject files into CMake.
  • In the new version (v2.0.x), we instead have native support in CubeMX to generate projects targetting CMake.

This solution is less complex and much more maintainable since we now can transfer the full ownership of the solution from Msft to ST.

Sorry for the compatibility break, but it was a necessity. We have the clear intention to create a "project migration tool" helping users to translate CubeIDE projects to CMake. But it will take a while.
If you wish to migrate your project today, we would recommend reading the User Guide, bundled with the new VS Code extension which shows how to do the migration.

Now, let's move to your question...

It is a bit too early to communicate on the general roadmap on our VS Code related investment. But here are some pointers:

  • Our VS Code ambition is to close the feature-gap vs the existing CubeIDE. But that will take time!
  • In the VS Code track we will try to provide more "continuous updates", i.e., if a feature is ready, we will publish it for immediate access (opposed to the 3x annual releases of CubeIDE). We are trying to become a bit more agile.
  • We are looking into opening up a "locked forum section" where we can invite "beta users" with which we can exchange on new ideas, share mock-ups and beta versions for feedback.
    • Roadmap discussions could be discussed in this section with a slightly more limited audience.


With respect to your question about continued investment on STM32CubeIDE.
No plan to make any disruptive discontinuation of STM32CubeIDE.
CubeIDE is instrumental to sustain our running business. We will continue to maintain it.
That said, we have already moved a lot of resources from STM32CubeIDE to our VS Code investment.
This investment/transition requires learning new programming languages, IDE frameworks and also porting of a lot of code. All this takes time before any value is delivered to customer.

In conclusion: We will continue to maintain CubeIDE while investing more aggressively on feature-growth with VS Code.

 

Kind regards, Mattias

View solution in original post

1 REPLY 1
Go to solution
mattias norlander
ST Employee

‎2024-04-22 02:58 AM

Hi PScal,

Valid question! Let's just re-cap for people who were not there, but who may read this thread tomorrow...

The week before EW2024 we release a new version (v2.0.x) of the VS Code extension set. This extension is a fresh start and a clear compatibility break vs the previous version.

  • In the previous version (v1.0.0) Microsoft extensions was in charge of translating CubeIDE .cproject files into CMake.
  • In the new version (v2.0.x), we instead have native support in CubeMX to generate projects targetting CMake.

This solution is less complex and much more maintainable since we now can transfer the full ownership of the solution from Msft to ST.

Sorry for the compatibility break, but it was a necessity. We have the clear intention to create a "project migration tool" helping users to translate CubeIDE projects to CMake. But it will take a while.
If you wish to migrate your project today, we would recommend reading the User Guide, bundled with the new VS Code extension which shows how to do the migration.

Now, let's move to your question...

It is a bit too early to communicate on the general roadmap on our VS Code related investment. But here are some pointers:

  • Our VS Code ambition is to close the feature-gap vs the existing CubeIDE. But that will take time!
  • In the VS Code track we will try to provide more "continuous updates", i.e., if a feature is ready, we will publish it for immediate access (opposed to the 3x annual releases of CubeIDE). We are trying to become a bit more agile.
  • We are looking into opening up a "locked forum section" where we can invite "beta users" with which we can exchange on new ideas, share mock-ups and beta versions for feedback.
    • Roadmap discussions could be discussed in this section with a slightly more limited audience.


With respect to your question about continued investment on STM32CubeIDE.
No plan to make any disruptive discontinuation of STM32CubeIDE.
CubeIDE is instrumental to sustain our running business. We will continue to maintain it.
That said, we have already moved a lot of resources from STM32CubeIDE to our VS Code investment.
This investment/transition requires learning new programming languages, IDE frameworks and also porting of a lot of code. All this takes time before any value is delivered to customer.

In conclusion: We will continue to maintain CubeIDE while investing more aggressively on feature-growth with VS Code.

 

Kind regards, Mattias

Top