Skip to main content
willcfj
willcfj
Associate III
June 12, 2019
Solved

STM32CubeIDE re-install fails

  • June 12, 2019
  • 8 replies
  • 5813 views

This is on a Windows platform. After some crashes (that wiped my code!), I removed and then re-installed STM32CubeIDE. After re-installing, builds don't work. Reason is there is no make executable in the IDEs search path. It is buried in the application directory, but no path to it. Quick and Dirty solution of copying the .exe to a place in the IDEs path didn't solve the issue, just got a different error.

I did delete the /ST directory too after un-installing, but still no luck getting make to work.

Potentially related, this was part of a big "get everything updated" push that included updating to latest Atollic tools (9.3.0), STM32CubeMX (5.2.1) and latest Java too.

Not very interesting, but here is the error message:

08:31:17 **** Clean-only build of configuration Debug for project CAN_Input ****
make clean 
Cannot run program "make": Launching failed
 
Error: Program "make" not found in PATH
PATH=[C:/ST/STM32CubeIDE_1.0.0/STM32CubeIDE/jre/bin/server;C:/ST/STM32CubeIDE_1.0.0/STM32CubeIDE/jre/bin;C:/ST/STM32CubeIDE_1.0.0/STM32CubeIDE/jre/lib/amd64;C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\Program Files (x86)\NTP\bin;C:\Program Files (x86)\Skype\Phone\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Users\willc\AppData\Local\Microsoft\WindowsApps;;C:\ST\STM32CubeIDE_1.0.0\STM32CubeIDE;]
 
08:31:18 Build Failed. 1 errors, 0 warnings. (took 188ms)

The make.exe file in STs directory is in C:\ST\STM32CubeIDE_1.0.0\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.make.win32_1.0.0.201904231117\tools\bin\

The only thing I haven't tried from looking at posts here is deleting the STM32CubeIDE entry in the registry.

will

This topic has been closed for replies.
Best answer by willcfj

Markus:

I did an un-install again, looked and the suggested registry entry to delete was not there. I re-installed and still got the same error (no surprize). After a few more experiments I was seeing some other errors that pointed to maybe something weird in the project configuration files (probably in .metadata). The fix that got things working was to completely delete the projects home directory with all the projects in it and re-start from scratch. That seems to have fixed it. My best guess is there is some path info there that got messed up and re-installing STM32CubeIDE was not fixing/replacing it.

will

8 replies

Markus GIRDLAND
Markus GIRDLAND
ST Employee
June 17, 2019

Did you try after deleting the STM32CubeIDE entry in the registry and if so, did anything change?

willcfj
willcfjAuthorAnswer
Associate III
June 17, 2019

Markus:

I did an un-install again, looked and the suggested registry entry to delete was not there. I re-installed and still got the same error (no surprize). After a few more experiments I was seeing some other errors that pointed to maybe something weird in the project configuration files (probably in .metadata). The fix that got things working was to completely delete the projects home directory with all the projects in it and re-start from scratch. That seems to have fixed it. My best guess is there is some path info there that got messed up and re-installing STM32CubeIDE was not fixing/replacing it.

will

willcfj
willcfjAuthor
Associate III
July 4, 2019

Markus (and all):

Ugh, while making a change in the CubeMX part of the STM32CubeIDE program of my project and doing the code regeneration, I got an error saying my library was not up to date. Only choice was to accept. Afterwards my entire project directory except for the .ioc file had been erased!

STM32CubeIDE is clearly not stable enough, or robust against internal problems. This is the second time some internal error with the CubeMX part of the IDE has just blown away my entire project directory. I do backups, but usually only weekly, so lost several days of work. This was version 1.0.1 and I've not been doing anything unusual about the install.

I restored the project files, but even with restored files the project still didn't show up in its entirety. This points again to something corrupted in the top level .metadata files.

With regret (and frustration) I'm going back to the now-obsolete final version of the Atollic tools and may try STM32CubeIDE after it gets to Rev 1.2 or so and seeing something in the notes about robustness against crashes. Now just need to figure out how to backport my changes under STM32CubeIDE to Atollic.

ALL: CONSIDER YOURSELF WARNED! IF USING THIS SOFTWARE CONSIDER BACKING UP MUCH MORE OFTEN AND AT LEAST EACH TIME RIGHT BEFORE USING THE CUBEMX PART OF THE IDE.

will

Dana Myers
Dana Myers
Senior
September 13, 2019

I've encountered the same exact issue. Any word if there's a work-around for this?

willcfj
willcfjAuthor
Associate III
September 13, 2019

Dana:

The release notes for the current version of STM32CubeIDE say they fixed this issue. I take that as a good sign, but still haven't gone back to it yet, still a bit nervous about trusting it. Hopefully you are still on the older 1.0.0 version and an upgrade to the latest fixes it. If you are still seeing the issue on 1.0.2, then maybe they haven't fixed it as robustly as they thought.

Back up often!!!

will

willcfj
willcfjAuthor
Associate III
September 14, 2019

Dana:

OK, maybe I don't need to be quite so paranoid then. Good on the re-install fixing things. Hopefully it will stay stable.

will

PHayw.1
PHayw.1
Associate II
December 27, 2021

I get this on Windoze with the very latest - 1.8.0 even if I add the install dir to the system path (so it shopuld be available to all users. I even created a dir in the root of C: (in case it couldn't cope with it being so long) to no avail. Nor would it work with that stub directory copied to the drive that Cube is installed on.

I don't suppose anyone has a fix or a workaround on this do they please?

willcfj
willcfjAuthor
Associate III
December 28, 2021

PHayw.1: The issues above were very much related to an earlier version STM32CubeIDE and resolved in Rev 1.2.0 at least for me. I've been keeping pretty current since then and never seen the issue (erasing your project on an MX compile). Not sure what changing the system path is doing.

will

PHayw.1
PHayw.1
Associate II
December 28, 2021

I uninstalled _all_ ST stuff, deleted all projects and had a trawl through the registry and deleted anything STM32 related. Then did a re-install of Cube IDE and it seems to work now. Not overly impressed that it failed - this was an experiment to see whether we should move to Cube. I _will_ persevere though.

BTW Adding to the system path was because Cube claimed it couldn't find the make.exe and I was giving it a hint but it didn't help :( Makes one wonder what it is doing internally to _not_ find it

Just starting the IDE is painfully slow (which is also not encouraging) and that is just a combo of an editor and a project loader at that point

Dana Myers
Dana Myers
Senior
December 28, 2021

I've since upgraded to 1.6 (now on 1.8) and STM32CubeIDE has been working well for me (Windows 10, Windows 11 boxes).

Start-up time is a little slow, but so is every Eclipse-based IDE I've used.

willcfj
willcfjAuthor
Associate III
December 29, 2021

Ooh, good point on SSD. I went that route 7-ish years ago when they were still small and expensive, but never regretted it. If your time is worth anything, SSDs are completely worth it--on any OS!

will

AAdam.2
AAdam.2
Visitor II
August 17, 2022

It's 2022 with version 1.9 STM32CubeIDE and there are still issues with jumping into the MXCUBE stuff (it's called Device Configuration Tool now). You add that with the touchGFX add on and let me tell you better back up everyday. I've never had a project any longer then a month that hasn't got corrupted with either this error or multiple others. Most you can fix after messing around, but some errors are a lost cause like this one

Terms & ConditionsAccessibility statement