Unable to connect to STM32H523

[WhoIsJohnGalt]

Hi,

I am trying to connect to a STM32H523RET MCU via SWD using a J-link Debugger (CubeProgrammer v2.17.0).
Reading the Product ID fails, so I get asked to select the MCU manually.

Unfortunately the list does not contain any STM32H52x MCU

 

But when I am trying to connect via Jlink - Commander I can find der MCU in the list and also connect to it:

Does anybody have an idea, why I can't find the MCU in the list when using the CubeProgrammer?

Thanks for any hints.

Regards

John

[Imen.D]

Hello @WhoIsJohnGalt ,

Try connecting with other MCU to check if the problem is reproduced with the tools used.

Try to “Connect Under Reset” mode.

Does your J-Link connect to any other STM32 targets?

Check these links that may help you:

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

 

[WhoIsJohnGalt]

Thanks for your quick response.

The first link I already checked and the connection with the jlink-commander does work fine (see first post screenshots). So therefore I assume the SWD lines are connected correctly.
(Unrelated side note: connecting via USB-DFU in CubeProgrammer also works fine)

 

CubeProgrammer:
Trying to connect with "Connect Under Reset" mode + "Software Reset" leads also to a failed PRODID read (as shown in first post".

 

I will check the value off the pull down capacitor on the NRST line of the MCU...

 

Regards,

John

 

 

 

[WhoIsJohnGalt]

Pull down capacitor is 100 nF, as recommended...

[WhoIsJohnGalt]

@Imen.D I have also tested to connect via J-Flash, which works fine.

Could it be that this is a CubeProgrammer issue?
(Connecting to a STM32U545 device works also with the CubeProgrammer)

Regards,

John

 

[Imen.D]

Hi @WhoIsJohnGalt ,

I escalated this issue internally to the appropriate team via ticket (ID 192398) in order to analyze this and take the necessary action.

PS: internal ticket ID 192398 is only for reference, not available outside of ST.

[Imen.D]

Hi @WhoIsJohnGalt ,

After check, this issue is related to the access port when connecting with J-Link and will be fixed in the upcoming release of STM32CubeProgrammer.

For now, you can manually change the access port from 0 to 1, which should resolve the issue with the current version.

[Imen.D]

Hello @WhoIsJohnGalt ,

I would inform you that this issue is fixed in the latest release of STM32CubeProgrammer (v2.18) available here on st.com.

Thank you for your patience and your kind understanding.