STM32CubeProgrammer cannot connect to MCU using j-link

[UniverGao]

Version: v2.16.0

I`ve downloaded and installed the latest application and was told that the CubeProgrammer could support J-Link now.

the GUI shows that JLink device can be selected:

I clicked the connect bottom, the chip select window of JLink was popped out:

after correct chip was selected, the error window showed below:

the error logs like this:

  15:30:23 : UR connection mode is defined with the HWrst reset mode
  15:30:23 : 20730746
  15:30:23 : Error: J-Link - Connection to target failed
  15:30:23 : Error: J-Link - Reading CPUID failed
  15:30:23 : Voltage     : 3.30V
  15:31:20 : Error: Database cannot be found. DatabasePath = D:\ProgramFiles\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/../Data_Base/STM32_Prog_DB_0xFFF.xml
  15:31:20 : Error: flash loader cannot be loaded. FlashLoaderPath = D:\ProgramFiles\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/FlashLoader/0xFFF.stldr
  15:31:20 : Error: Database cannot be found. DatabasePath = D:\ProgramFiles\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin/../Data_Base/STM32_Prog_DB_0xFFF.xml

 I wander if the app support jlink probe, if not, why I can select it?

[Andrew Neil]

and you're sure it's a genuine J-Link - not a fake/clone?

[Meganita]

Yes, it was bought on Segger's site.

[Meganita]

I didn't solve the issue with the J-Link, but I can now program the STM32. I actually found a Nucleo-L433RC and have been able to program the STM32(L052K8) via ST-Link. 

[Andrew Neil]

So there is something wrong with your J-link and/or its setup and/or connections.

Probably best to take that up with Segger:

https://forum.segger.com/index.php/Board/3-J-Link-Flasher-related/ 

[baron]

This can happen if the board is not being powered. It wont be by the j-link.

[lro]

I have the same problem as the original post, there is definitely a bug with the H7S3/programmer/JLink combination.

Windows 11 23H2
STM32CubeProgrammer v2.17.0
J-Link software V8.10f
J-Link V9.40 firmware 2021 May 7 16:26
Board 1: NUCLEO-H755ZI-Q / chip STM32H755ZIT6
Board 2: NUCLEO-H7S3L8    / chip STM32H7S3L8H6

On the H755 board, my J-Link works great. It recognizes the Device ID 0x450:

And on the NUCLEO-H7S3L8 (Device ID 0x485) the onboard ST-LINK also connects:

Then, I can change the power supply to leave the ST-LINK unpowered and power on only the H7S3 and connect the J-Link by cable (I double checked the pinout, it's all correct!). The software shows me the same errors as the original post:

Apparently it fails to read the Device ID and looks for Device ID 0xFFF which does not exist. Connecting to Access Port 1 instead returns 0xAAA which also does not exist.
Connecting with J-Link Commander software is fine. Reading DBGMCU_IDCODE (@ 0x5C001000) returns the expected Device ID 0x485.

[Andrew Neil]

---

@baron wrote:

This can happen if the board is not being powered.

---

In this case, the target does have power:

---

@UniverGao wrote:

---

[TS5]

I'm having a similar issue with one of the chip.  It seems to be working fine with the second chip.