Debuging fails after HAL_Init()

[KMill]

I am debugging an application for an STMF103RCTX Using STM32CubeIDE and an STLINK v2 debugger.

This is my usual combination of tools and my usual hookup.

I find that I can start a debug session and step into main() and even step over anything befoer HAL_Init(); but as soon as I hit that the begugger connection fails.

I've made a short video showing this issue:

 

My hookup from the STLINK to the device is as follows:

STLINK --->  DEVICE
Pin 2 VCC ---> VCC
Pin 4 GND ---> GND
Pin 7 TMS/SWDIO ---> PA13/TMS/SWDIO (46)
Pin 9 TCLK/SWCLK ---> PA14/TCLK/SWCLK (50)
Pin 15 --> RESET ---> nRST (7)

 Any ideas? (The app runs perfectly when not trying to debug it)

[mƎALLEm]

Hello,

What memset is doing here? The destination? the size?

if you remove that line, do you have the same behavior?

[KMill]

The memset is absolutely fine, destination and size are correct.

I only added it to gove me something to step-over beforr HAL init as as test.

I will try the things mentioned in the other post...

[Andrew Neil]

---

@KMill wrote:

I find that I can start a debug session and step into main() and even step over anything befoer HAL_Init(); but as soon as I hit that the begugger connection fails.

---

So what happens if you step into HAL_Init() ?

Where within HAL_Init() does it fail?

Does your  HAL_Init() disable the SWD pins, perhaps ... ?

https://community.st.com/t5/stm32-mcus/how-to-solve-debugger-connection-issues/ta-p/49693

 

[KMill]

@Andrew Neil Thanks for the suggestion.

If I step into HAL_Init() it stops at this line:

My IOC file has reserved the pins for debug:

[Andrew Neil]

---

@KMill wrote:

If I step into HAL_Init() it stops at this line:

---

Look at the comment immediately above that line: you are disabling the JTAG and SWD - so obviously the debug connection will fail!

[Karl Yamashita]

Start a new project with the bare minimum. Then see if you can debug and get past HAL_Init 

[Karl Yamashita]

Nevermind i found it. I started a new project with just serial debugging enabled, nothing else. I show the same code.