Author Topic: jlink question  (Read 1504 times)

0 Members and 1 Guest are viewing this topic.

Offline bigendianTopic starter

  • Regular Contributor
  • *
  • Posts: 82
  • Country: it
  • shutdown -h now
jlink question
« on: September 04, 2025, 12:18:27 pm »
Hi,
i have here a jlink clone i bought several years ago on ebay, when i was a newby on such pods and thought it was a regular jlink. So i was in total good faith.
Of course at every fw upgrade it get blocked by Segger. I can re-flash it by jtag and have it working again, but it is somtehing i don't like/want to do.

So i have some job boards with cortex-M "jlink" connector. Do you think i can use some other cheaper programmer ? Or, better to get a regular jlink ?

Regards,
angelo
 

Offline GromBeestje

  • Frequent Contributor
  • **
  • Posts: 310
  • Country: nl
Re: jlink question
« Reply #1 on: September 04, 2025, 08:41:58 pm »
When you re-flash, make sure you match the serial number and licenses. If they mismatch it will pop up a clone detected message.
 

Offline thm_w

  • Super Contributor
  • ***
  • Posts: 9890
  • Country: ca
  • Non-expert
Re: jlink question
« Reply #2 on: September 04, 2025, 11:55:15 pm »
You can:
- Do whats suggested above
- Buy a newer clone
- Buy a real jlink $500
- Buy jlink mini $50
- Build/buy any generic programmer that will work with your mcu (blackmagic probe, stlink, etc.)

https://www.eevblog.com/forum/microcontrollers/sts-gdb-server-probe-rs-jlink-etc-what-are-the-differences-between-them/
Profile -> Modify profile -> Look and Layout ->  Don't show users' signatures
 

Offline GromBeestje

  • Frequent Contributor
  • **
  • Posts: 310
  • Country: nl
Re: jlink question
« Reply #3 on: September 05, 2025, 07:45:04 am »
If your MCU is supported by OpenOCD, it will work with a JLink clone without issues.
 

Online hans

  • Super Contributor
  • ***
  • Posts: 2000
  • Country: 00
Re: jlink question
« Reply #4 on: September 05, 2025, 11:18:29 am »
If you just need basic program/debug functionality, use OpenOCD instead of JLink instead.

OpenOCD can talk through various USB dongles, including JLink at a low-level (more like bitbanging), but it will not use JLink's APIs. Those APIs contain accelerated routines for certain targets, which is faster, but also means support is limited. E.g. the DLLs for JLink v8 doesn't support Cortex-M7 or the M23/M33 cores, while OpenOCD does (if your MCU family has support, which may lack behind a bit).
A second benefit is that you're not using JLink's software outside of the TOS, don't get hammered by firmware updates, etc.
 

Offline bigendianTopic starter

  • Regular Contributor
  • *
  • Posts: 82
  • Country: it
  • shutdown -h now
Re: jlink question
« Reply #5 on: September 05, 2025, 02:01:37 pm »
Hi friends, thansk a lot.

issue is that some sw (maybe jlink tools only ?) see the old fw version and update it, this is what happend.
Yestyerday, an umbrella python tool used from the customer called jlink tools probably, that upgdraded/blocked the jlink.

Would do as suggested
- will reflash the clone to be working back-
- ordered a blackmagic probe

Thanks a lot
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf

 

- - -
-->