How to stop STM32CubeIDE from opening random files when debug is started?

[HTD]

Every time I debug my project for STM32H747 (created with TouchGFX), the debugger opens a bunch of random files, different each time.

It does that BEFORE even finishing uploading the project to the board. Before I even get "Verifying" on the console.

Then it stops at MPU_Config() in main.c.

It doesn't do that in projects created with STM32CubeIDE, just with a TouchGFX project.

It's super annoying, is there any way to stop that beavior?

[AnkhInnovationsLLC]

This is still the case in 2023 as of October 9th... Just absolutely terrible working in the STM32 IDE.

Press launch, it randomly switches to the open IOC, then to the xxx startup.S file. Super super annoying.

I'm finding the overall experience with ST to be quite poor, its taking us way way longer to do anything really because everything is in poor old inaccurate PDF's, the IDE is so slow (it takes about 3 seconds to switch tabs) and its so janky its ridiculous. I've never seen an IDE jump into TWO random files just running the program.

[KMill]

I agree - this simple bug is taking far too long to get fixed. It shows that STM32CubeIDE is a very low priority for ST, and therefore not one we can rely on for long term support. If I were cynical I'd say it's deliberate in order to push people towards paid-for IDE's by other suppliers. But I maintain my long-held belief that chip manufacturer's must porvide free, high quality tools to support their chips, as it drives confidence and therefore sales. Low quality tools and shockingly bad support like this example have me looking for other suppliers. 

[AnkhInnovationsLLC]

We abandoned using the STM32. The IDE is just too clunky, slow and makes development very difficult. To test a simple one line change takes > 20 seconds. It just isn't suitable for us.

Much happier developing for the ESP32 in VSCode.

[KMill]

I have to admit that I do like the STM32CubeIDE - especially the MX tool integration - it makes configuring the project much simpler. 

But I hate to say it, Eclipse is just so.... old looking. Like you say, it's clunky and slow. It does weird things. It does enough weird things that I have developed a love-hate relationship with it.

Like (just one more example) when you fire up the App and it spends the first two minutes checking for updates to the huge amount of plugins and extensions. Fine it does that in the background - but have you every tired selecting anything from a drop-down in a dialog while it's doing it? The drop-down closes and erases your input every second or so.

Eclipse is Java under the hood - but Java never really gave the cross-platform write-once-run-anywhere convenience it promised us. So (for example) you can get Motor Control Workbench on Windows but not macOS - and you get TouchGFX on windows, but not macOS. So why bother with a clunkly old, slow concept like Eclipse when there are much better solutions available and which are fit for the 21st century. 

I guess ST has made an investment of time and talent in the eclipse based stuff, and so they can't abandon it. But they could put a bit more effort into fixing LONG LONG LONG standing bugs and making it more suitable for cross-platform uses.

 

[Sakvoyage]

This is one of the most annoying "features" also the way code is introspected - you can only see mistakes after build - its never highlited in code until then. 

Also typing suggestions are inexistan, you have to know exact var or func names when typing - it does not autocomplete.

[BenETryHard]

It can open files from non-focussed projects (wtf!) resulting in me unknowingly editing a file in a different project as the file path is not immediately evident. I don't recall this happening last year so may be due to recent updates. Please someone fix it. My workaround if I don't need debugging, is to edit and compile in Cube IDE but program with Cube Programmer.