2024-09-25 01:28 PM
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
Solved! Go to Solution.
2024-10-02 07:34 AM
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.
2024-09-25 02:15 PM
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:
2024-09-26 01:25 AM
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
2024-09-26 04:05 AM
Pull down capacitor is 100 nF, as recommended...
2024-09-27 07:07 AM
@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
2024-09-30 01:58 AM
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.
2024-10-02 07:34 AM
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.
2024-10-02 10:18 AM
Thanks, I can confirm this worked for me. Now also the connection in the CubeIDE works as well.