setting during Build & Debug

Domy_ST · ‎2026-03-25

hello ST Community,

where can I set it to avoid generating the file "startup_stm32l5...zetxq.s" during compilation and debugging in the stm32CubeIDE environment and also how to avoid that the space bar "|" when editing the line of code of 'main.c' is automatically moved to the last line of code of 'main.c' during compilation and debugging.

Where should I set it to avoid all this?
Thanks so much for your support

Andrew Neil · ‎2026-03-25

@Domy_ST wrote:
avoid generating the file "startup_stm32l5...zetxq.s" during compilation and debugging

This file is not generated during compilation or debug - it's only created when you first create the project.

Are you referring to CubeIDE 2.1.0: Still opening spurious files when starting a debug session ?

@Domy_ST wrote:
the space bar "|" when editing the line of code of 'main.c' is automatically moved to the last line of code of 'main.c' during compilation and debugging.

I don't understand - What do you mean by this ?

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.

TDK · ‎2026-03-25

This is an annoying STM32CubeIDE bug that ST hasn't addressed in years. Don't hold your breath.

If you feel a post has answered your question, please click "Accept as Solution".

Domy_ST · ‎2026-03-25

hello @Andrew Neil

I'm referring to CubeIDE version 2.0.0, which generates the debug every time I modify a single line of code.

In this case, for example, "main.c" has 104 lines of code. If I modify the code on line 42 of "main.c", the "|" will appear, like in the photo:

It stays on line 42, but when it compiles and automatically generates debug, that "|" will go to the last line, 104 (there's no breakpoint). Is it possible to prevent it from going to the last line and staying at line 42 where it was before? This thing going to the last line is annoying; I have to search for the code on line 42 again to make another change.

Is there a setting I can use to avoid this?

Domy_ST · ‎2026-03-25

Is there a bug that STM32CubeIDE generates and reports this unwanted file? That's a bad thing, so there's no way to avoid it?

Andrew Neil · ‎2026-03-25

@Domy_ST wrote:
Is there a bug that STM32CubeIDE generates and reports this unwanted file?

Again, it's not "generating" that file.

That file is always an essential part of the project - it contains the startup code.

The bug is just that CubeIDE opens it in the editor.

As noted, this is a long-standing issue and is unlikely to get fixed anytime soon (it appears that it's not even specific to CubeIDE).

If you read the linked thread, you will see some workarounds...

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.