Error when I try to program my custom board

[AZube.2]

Hello,

I made my custom board with a STM32WLE5CC micro and I am trying to program it using the SW interface. I have a ST-LINK/V2 where I connect the SWDIO, SWCLK, TRACE_SWO, NRST, VCC and GND pins from my board.

When I try to program it using STM32CubeIDE, an error jumps when the programing is at 92% (almost completed) . This is the error:

 When I try to connect to the device using STM32CubeProgrammer two things happen. First thing is what we can see in the following picture:

 When I try to connect in Normal mode an error jumps saying: "Cannot connect to access port. If you are trying to connect to a device with TrustZone enabled please try to connect with HotPlug mode" (which is weird because I never programmed this chip before, never touched the TrustZone)

So, then I try to connect in HotPlug mode and works:

  

However I still cannot debug my program trough STMCubeIDE because the first error persists. Besides, I guess that I should be able to connect using the normal mode.

Any help is appreciated, I am a bit lost here.

Thanks,

Asier

[MM..1]

You config CubeIDE debug wth some error. try show screen or check it.

[AZube.2]

I created a new project specific for my micro and used the default debug configuration:

I also tried enabling and disabling the SWV (Serial Wire Viewer), but the result is exactly the same. I also tried using OpenOCD, but many more errors jump...

[MM..1]

Getting started with projects based on dual-core STM32WL microcontrollers ​​in STM32CubeIDE - Application note

page 10

[AZube.2]

@MM..1​ Thanks for the reply. I followed the steps in the document, but I am getting the same behavior

[MM..1]

Realy you set connection under reset and enable low power mode debug ?

[AZube.2 · Accepted solution]

Thanks a lot for the support @MM..1​. I finally found the problem and it was hardware. The reset line was connected to ground by mistake (there was an erroneous switch that made this connection). Once I unsoldered this component from the board, the programing/debugging started to work as usual!