Skip to main content
S
Stag
Associate
April 30, 2026
Solved

Vscode converter Error 35 and Error 41

  • April 30, 2026
  • 3 replies
  • 182 views

Hello, 

I'm trying to convert a project to vscode the first error I incurred to was this one:

 

I'm trying to convert to cmake using the extension a project for the STM32U585OIYXQ, when I load the source folder and set the output folder then i push on convert and this is the output that I get :   

[Error] [ide-project-convert]:Generating project...
[Error] [ide-project-convert]:The specified 'STM32U585OIYxQ' device is unknown
[Error] [ide-project-convert]: Project conversion failed with exit code: 35.

 

Which has been solved with this work around: "you can enable the stm32cube-ide-project-manager.conversion.ignoreMissingDevice VS Code setting".

That went through and I have the following new error:

 

[Info] [project-manager] STM32CubeIDE project manager activation....
[Info] [ide-project-convert] Starting project conversion...
[Info] [ide-project-convert] cube wrapper version: 0.10.2
[Info] [ide-project-convert] Invoking STM32CubeIDE Eclipse exporter...
[Info] [ide-project-convert] Generating project...
[Error] [ide-project-convert] Multiple output names found across project configurations is not supported.
[Error] [ide-project-convert]: Project conversion failed with exit code: 41.

 

Any suggestion?

 

Thanks

 

 

 
Best answer by Julien D

Hi @Stag,

Apologies for late reply, the issue has been understood and fixed in our mainstream. The fix will be part of the next delivery.

3 replies

Julien D
Julien D
ST Employee
April 30, 2026

Hi @Stag,

Thanks for joining us on the Community Forum. It is definitely a better place to discuss details than the Marketplace Q&A.

About:

[Error] [ide-project-convert] Multiple output names found across project configurations is not supported.

I don’t know how your STM32CubeIDE project is set up, but I guess it has multiple build configurations, likely Debug and Release, and both declare different output filenames. That is not supported at the moment.

Could you try to align them across your build configurations? Then try to convert again the project.

JulienD_0-1777562374780.png

JulienD_1-1777562416275.png

Note: the same applies to source files as well. All build configurations must use the same set of source files.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
S
StagAuthor
Associate
May 4, 2026

Hi Julien, 

thank for the answer, indeed as you were saying I have multiple build configurations. 

I changed the settings in the original Repository, as you said, but now i cannot go ahead with the converter on vscode since when I select the source project to convert in the plugin I get this error in vscode: "Entity expansion limit exceeded: 1002 > 1000". The error is in a small box on the bottom right.  This happens only when I select the projet source and not for the destination. 

Julien D
Julien D
ST Employee
May 4, 2026

Could you share with me the .project and .cproject files of this project?

Either here or by PM.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
Julien D
Julien D
ST Employee
May 5, 2026

@Stag I got your files, thanks for sharing them.

I can already reproduce the issue, it is something dev team has never faced until then. I'll get back to you once analyzed/understood.

To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
    Julien D
    Julien DAnswer
    ST Employee
    May 20, 2026

    Hi @Stag,

    Apologies for late reply, the issue has been understood and fixed in our mainstream. The fix will be part of the next delivery.

    To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
    Terms & ConditionsAccessibility statement