JLink V8

[zelea2]

You don't need to patch the Jlink PC software. Just put the proper license strings in the probe and use a serial number which isn't banned.
You can read how to do this here: http://uglyduck.vajn.icu/ep/archive/2019/05/Unbricking_a_SEGGER_J_Link_v9_debug_probe.html

[yahoo]

I don't have yet V9 to experiment but from the upper link I see one huge problem. There is RSA signature of the cpu id (and maybe including the serial number) storred in the firmware which can be verified with a public key in the Segger software, and there is no way to recalculate a new one in the V9 device without knowing the private key used to calculate the signature. So, I prefer to patch the Segger software (taking me no more than 1-2 minutes) instead of trying to guess if the next version will verify this signature or not. Tnx for the link anyway. There is enough information what was done and options to avoid the traps.

[Kombinator]

For the latest JLink_Windows_V788a_x86_64.exe the file JLink_x64.dll fix is at offset 0xC81D4: 90 90 90 90 90.
I just ordered V9 clone from aliexpress to replace my old JLINK and it will arrive by the end of the month. Is there somebody using V9 and can confirm this patch is good for V9?

J-Link V9  HVersion: V9.60
Read OK

[pickit2]

lol software updated.
now V788b
offset : xx0c8444

[zelea2]

I don't have yet V9 to experiment but from the upper link I see one huge problem. There is RSA signature of the cpu id (and maybe including the serial number) storred in the firmware which can be verified with a public key in the Segger software, and there is no way to recalculate a new one in the V9 device without knowing the private key used to calculate the signature.

That is true but the only time the signature is verified is when you alter the license strings in the JLink probe via USB. When you just store them in the STM32 memory via SwD no check is performed and neither the code or the licenses are checksum-ed.

[pickit2]

That is true but the only time the signature is verified is when you alter the license strings in the JLink probe via USB. When you just store them in the STM32 memory via SwD no check is performed and neither the code or the licenses are checksum-ed.

I tried to update the Licence number via usb, on my clone but it failed. put on backburner till my feind returns my genuine Jlink

[HULK69]

Here is a mirror of the Jlink edu keygen

[ur63]

Jlink edu keygen

Is it correctly summarized, that this keygen enables functionalities normally not available with JLink EDU (RDI, FlashBP, Flashdownload, J-Flash)?

[HULK69]

Yes you can do all of that but i personnally only use it for Jflash

[Pegote]

Hi Guys,

I just got a Jlink v9 V9.4 ARM from Aliexpress for 23€ but I can not make it work with my target, a Nordic nrf53 CPU.

Jlink PCB is marked as v9.44, Jlink MCU is ARM 32F205

I installed Jlink v7.88a and patched the Jlink_x64.dll @000C81D4 with 90 90 90 90 90.

But after all I get the following error:

Code:

Connecting ...
 - Connecting via USB to probe/ programmer device 0
 - Probe/ Programmer firmware: J-Link V9 compiled May  7 2021 16:26:12
 - Probe/ Programmer S/N: 69------ (hidden on purpose)
 - Device "NRF5340_XXAA_APP" selected.
 - Target interface speed: 500 kHz (Fixed)
 - VTarget = 3.288V
 - ConfigTargetSettings() start
 - ConfigTargetSettings() end - Took 4us
 - InitTarget() start
 - InitTarget() end - Took 98.0ms
 - ConfigTargetSettings() start
 - ConfigTargetSettings() end - Took 5us
 - InitTarget() start
 - InitTarget() end - Took 10.2ms
 - ERROR: Failed to connect.
Could not establish a connection to target.

It is not a config or JTAG cable problem, because I have another original J-link EDU that works just fine.

Could you please help me to make this J-link clone to work?

Thanks in advance

[pickit2]

Why are you using V-788a when there is newer version. ?

[Pegote]

I found the solution to my problem, it was the jumper inside the jlink clone. I put it as the picture, leaving the 3 pins open, and now it works fine.

I just installed the latest jlink v792f and works all fine without patching the dll.

PS: Which are the newest jlink dll patch instructions?

As per this thread, newest is v788b, isn't?

JLink_x64.dll
V788b   0xC8444
V788a   0xC81D4    
v782c   0xB3D6D     e8 7e 85 ff ff  ->  90 90 90 90 90
v770    0xCC238     e8 53 87 ff ff  ->  90 90 90 90 90

[Ahmad_k]

Hi Guys,

I just got a Jlink v9 V9.4 ARM from Aliexpress for 23€ but I can not make it work with my target, a Nordic nrf53 CPU.

Jlink PCB is marked as v9.44, Jlink MCU is ARM 32F205

You can convert any v9 clone to genuine without patching jlink dll.

check this http://www.sonsivri.to/forum/index.php?topic=67554.msg206029#msg206029

[avrlover]

can any one patch  latest j-link  software ie patch  both JLink_x64.dll
JLinkARM.dll