J-link driver manual upgrade for STM32U5G9J-DK1.

[lhz412]

Hello, 

I tried to use a J-Trace to program an STM32U5G9J-DK1.  This J-Trace Pro works well on other projects.  I also tried a J-link and it shows the same issue. While, of course, STLink3 via the same connector works well. 

After I look into the J-link log file, the J-link driver in the latest 1.5.1 IDE is still V7.94h.  Even my PC has the latest j-link v7.96g, the IDE will not automatically upgrade.  The J-link release notes shows the STM32U5G9 was supported since v7.94m.  I feel that could be the reason why the IDE doesn't recognize the DK.   

I overwrote the bin folder (C:\ST\STM32CubeIDE_1.15.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.jlink.win32_2.2.200.202402092224\tools) by the the entire v7.96g J-link folder.  The the IDE showed the v7.96g was loaded, but it pops a different error.   

Is there a correct way I can manually upgrade the J-link driver embedded in the IDE?

Both j-link logs are posted below, 

Thank you very much!

The first J-link Log based on v7.94h:

----------------------------------------------------------------------------

SEGGER J-Link GDB Server V7.94h Command Line Version

JLinkARM.dll V7.94h (DLL compiled Feb 1 2024 11:04:36)

Command line: -port 2331 -s -device STM32U5G9NJ -endian little -speed 4000 -if swd -vd

-----GDB Server start settings-----

GDBInit file: none

GDB Server Listening port: 2331

SWO raw output listening port: 2332

Terminal I/O port: 2333

Accept remote connection: localhost only

Generate logfile: off

Verify download: on

Init regs on start: off

Silent mode: off

Single run mode: on

Target connection timeout: 0 ms

------J-Link related settings------

J-Link Host interface: USB

J-Link script: none

J-Link settings file: none

------Target related settings------

Target device: STM32U5G9NJ

Target device parameters: none

Target interface: SWD

Target interface speed: 4000kHz

Target endian: little

Connecting to J-Link...

J-Link is connected.

Failed to get index for device name 'STM32U5G9NJ'.GDBServer will be closed...

Shutting down...

Could not connect to target.

Please check power, connection and settings.

-----------------------------------------------------------

The second J-link Log by v7.96

----------------------------------------------------------

SEGGER J-Link GDB Server V7.96g Command Line Version

JLinkARM.dll V7.96g (DLL compiled May 8 2024 15:00:44)

Command line: -port 2331 -s -device STM32U5G9NJ -endian little -speed 4000 -if swd -vd

-----GDB Server start settings-----

GDBInit file: none

GDB Server Listening port: 2331

SWO raw output listening port: 2332

Terminal I/O port: 2333

Accept remote connection: localhost only

Generate logfile: off

Verify download: on

Init regs on start: off

Silent mode: off

Single run mode: on

Target connection timeout: 0 ms

------J-Link related settings------

J-Link Host interface: USB

J-Link script: none

J-Link settings file: none

------Target related settings------

Target device: STM32U5G9NJ

Target device parameters: none

Target interface: SWD

Target interface speed: 4000kHz

Target endian: little

Connecting to J-Link...

J-Link is connected.

Firmware: J-Trace PRO V3 Cortex-M compiled Apr 25 2024 09:13:57

Hardware: V3.00

S/N: 753002352

Feature(s): RDI, FlashBP, FlashDL, JFlash, GDB

Checking target voltage...

Target voltage: 1.75 V

Listening on TCP/IP port 2331

Connecting to target...

ERROR: Could not connect to target.

Target connection failed. GDBServer will be closed...Restoring target state and closing J-Link connection...

Shutting down...

Could not connect to target.

Please check power, connection and settings.

------------------------------------

[lhz412 · Accepted solution]

Well, after rebooting everything, suddenly the IDE + J-trace can program the DK.  

Yes, still need update the J-link to the latest version, but the way to update was correct. 

Request closed!