Skip to main content
TJack.2
Associate III
December 17, 2024
Solved

Can't build existing projects after upgrading Cube IDE

  • December 17, 2024
  • 4 replies
  • 1265 views

I've just upgraded from Cube IDE 1.15 to 1.17.0 under Ubuntu 22.04 using the 'check for updates' feature.

When I try to rebuild (right click in project explorer and click 'build project') any of my existing projects I just get a message such as below. It doesn't actually compile anything.

 

 

Best answer by TJack.2

I concluded that "check for upgrades" was broken, as suggested elsewhere, and 'revert' even more so, so I reinstalled 1.17.0 from a fresh download, which worked just fine.

I incidentally ran across an issue that made CubeIDE unstartable. I haven't checked it out, but what I think I did was to close the IDE with an .ioc file left open in the editor, and then went and deleted the actual project files including that .ioc.  So when I started IDE it tried to restore to the edit window the file that wasn't there, and crashed.  As I recall deleting the .metadata file in the active workspace solved it.  I think this happened with both 1.15 and 1.17.

The original issue with GFX01M2 was the software being incompatible with the $AZ2 version of the PCB compounded by the fact that I plugged it in the wrong way around.  With the help from this forum elsewhere, that is now working.

4 replies

Andrew Neil
Super User
December 17, 2024

Did you attach the right file?

The attached file seems to be from CubeProgrammer - not CubeIDE - and show problems with programming - not building?

A complex system that works is invariably found to have evolved from a simple system that worked.A complex system designed from scratch never works and cannot be patched up to make it work.
TJack.2
TJack.2Author
Associate III
December 17, 2024

Yes, wrong file, I've corrected it.

TJack.2
TJack.2Author
Associate III
December 17, 2024

I don't want to confuse things, only to deal with one problem at a time.  But here's the back story.

The plan was to upgrade an old PCB design from a 7-segment LCD to a graphics display.  So I bought a Nucleo STM32G071RB and a X_NUCLEAO-GFX01M2 display, and downloaded the demonstration software "GFX01M2_HelloWorld" which I imported into my working CubeIDE1.15.1 with a view to using that as the basis for experiment.  Simple, right?

Not so simple. It built OK, upgraded the ST-Link but wouldn't flash the board, giving an MI error erasing the second bank.  Am I doing something silly?  I read the comments here, tried various things, and ended up doing "check for upgrades" on the IDE.  That upgraded it to 1.17.0.  I know, that was a *** mistake, doing that on my production machine, but there it is.  So that went from bad to worse, it wouldn't build at all, on any existing project, as indicated above.  So to compound my mistake, I then clicked on 'revert' in the installation history.  That did its stuff but seems to have given me an invalid config.ini file and now the IDE won't even start.  Looks like a clean install is the order of the day.

I'll worry later about the fact that the demonstration system failed right out of the box.

TJack.2
TJack.2AuthorBest answer
Associate III
December 24, 2024

I concluded that "check for upgrades" was broken, as suggested elsewhere, and 'revert' even more so, so I reinstalled 1.17.0 from a fresh download, which worked just fine.

I incidentally ran across an issue that made CubeIDE unstartable. I haven't checked it out, but what I think I did was to close the IDE with an .ioc file left open in the editor, and then went and deleted the actual project files including that .ioc.  So when I started IDE it tried to restore to the edit window the file that wasn't there, and crashed.  As I recall deleting the .metadata file in the active workspace solved it.  I think this happened with both 1.15 and 1.17.

The original issue with GFX01M2 was the software being incompatible with the $AZ2 version of the PCB compounded by the fact that I plugged it in the wrong way around.  With the help from this forum elsewhere, that is now working.