STM32CubeIDE: How to enter commands in the debug configuration as in TrueStudio?

[MB_Inv]

Hello,

I used the following "Target Software Startup Script" in the debug configuration in Atollic TrueStudio (this is necessary since we're using a bootloader and our application binary which I would like to debug is not placed at the beginning of the STM32 flash):

How to enter this in STM32CubeIDE?

I would really need to debug my firmware, but can't figure out how to do the required settings...

Any ideas?

Kind regards,

Markus

I am assuming your ST-Link works with Atollic?

[MB_Inv]

Yes, the ST-Link works with Atollic TrueStudio 9.2.0 - just rechecked it.

Will also try with another project in CubeIDE.

[MB_Inv]

Have now also tried with an STM32F4DISCOVERY board and example project using CubeIDE and debugging works without any problems using ST-Link (onboard of the eval board).

But I can't figure out what the difference is here (except from the fact that my own program is located at another flash position and thus needs the additional initialization commands)...

Using the following initialziation commands, the execution of the command is always trapped in the Default_Reset_Handler:

---

set host-charset CP1252

set target-charset CP1252

set *0xE000ED08 = 0x08020000

set $sp = *(unsigned int*)0x08020000

set $pc = *(unsigned int*)0x08020004

tbreak main

continue

---

So I thought that maybe there's some problem with my linker file, but in Atollic TrueStudio it worked without problems - likewise with the J-Link in CubeIDE...

Any ideas?

I wonder if it is a project settings issue...

If you make a copy of the example project that works, and replace the source code with the one that is having issues, does it work?

[MB_Inv]

I just tried that. I copied my sources and linker script to the working project and set the corresponding includes. However, the effect is the same - Debugging with J-Link works, but using the ST-Link execution hangs in the Default_Reset_Handler...

Maybe try testing with just your bootloader. Are you able to debug your bootloader with ST-Link?

[MB_Inv]

Unfortunately, I can't debug my bootloader with CubeIDE since it has been developed with another IDE and its (closed) library...

Are you able to test your application without the bootloader? Which means you can use the default settings without this linker script? Think that will at least allow you to verify that your application can work with ST-Link?

[MB_Inv]

Yes, debugging the non-shifted application works with ST-Link in CubeIDE.

So it's obviously a problem with the gdb commands needed for the shifted version...

Hmm, yea. Cause if the non-shifted version works, it means that your CubeIDE project is able to talk to ST-Link fine. I shall assume u updated the linker script accordingly for the shifted version from the non-shifted version?

I noticed your gdb commands have changed from your earlier posts? The offsets are different now?

Sorry, I just noticed your ST-Link execution hangs in Default_Reset_Handler? So it is different from your previous error? "Error! Failed to read target status"? So you are able to debug now but it get stuck in the Default_Reset_Handler?