Sunday, April 22nd 2018, 10:47am UTC+2

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

EmBlocks

Beginner

Date of registration: Jun 24th 2012

Posts: 32

1

Friday, March 15th 2013, 9:40am

Jlink installer doesn't update the Reg InstallPath

Hi,

I noticed that, every time when I install the newest JLink software, the regKey software\SEGGER\J-Link:InstallPath isn't updated.
Maybe this is with a purpose, I don't know. If not, it would be handy if this key was updated so that IDE's automatically invoke the latest version.

Regards.

SEGGER - Alex

Super Moderator

Date of registration: Dec 18th 2007

Posts: 1,516

2

Tuesday, March 19th 2013, 1:09pm

Hi,

Quoted

I noticed that, every time when I install the newest JLink software, the regKey software\SEGGER\J-Link:InstallPath isn't updated.

So far, we can not confirm this.
Could you please give us a bit more information about your environment?
What operating system do you use (e.g. Win7 x64)?
Are you working with administrator rights or standard user-rights?

Currently, the key "InstallPath" is updated each time a J-Link software package is installed. We are in progress of changing this since with the current implementation when installing V4.64 first and then V4.62, the registry key will point to the installation of V4.62 without giving the debugger a chance to locate the latest installed version.

We will change it like this (exact registry key structure is not finally decided yet and will be documented when released):
Each installation creates a key:
software\SEGGER\J-Link\Vx.xx
which contains the keys:
InstallPath
VersionNo (for example for V4.64a this would be 046401)

When uninstalling a package, the appropriate key + sub-key will also be deleted.

This will allow a debugger to always detect the latest installed version of the J-Link package with an option to also provide access to earlier version if necessary for some reason.


Best regards
Alex

EmBlocks

Beginner

Date of registration: Jun 24th 2012

Posts: 32

3

Wednesday, March 20th 2013, 8:35am

I work with win7-64 and not with admin rights. I always work as a normal user.
Now I update the reg. by hand (sometimes).

regards.

SEGGER - Alex

Super Moderator

Date of registration: Dec 18th 2007

Posts: 1,516

4

Wednesday, March 20th 2013, 8:39am

Hi,

Alright, we will check if we can reproduce any problem here and get back to you as soon as we have any results.


Best regards
Alex

EmBlocks

Beginner

Date of registration: Jun 24th 2012

Posts: 32

5

Friday, March 22nd 2013, 10:11am


We will change it like this (exact registry key structure is not finally decided yet and will be documented when released):
Each installation creates a key:
software\SEGGER\J-Link\Vx.xx
which contains the keys:
InstallPath
VersionNo (for example for V4.64a this would be 046401)



May I suggest something different?
Is it possible that the JLink installer is maintaining a regkey e.g. LatestVersionPath at the SEGGER root? If a 4.62 is installed after 4.66 then the installer won't update that regkey (perhaps checks its validity).

Pros:
- This will give a generic way to retrieve the path info. Otherwise the IDE needs to implement segger special code to keep supporting auto launch. For EmBlocks this will mean that I have to switch to a manual GDB server browsing at the debug settings pane for the JLink.
- Sustainable, if segger needs another structure in the future it wont effect us all.
- EmBlocks, for instance, works with generic references (absolute, emblocks macro or regkey) and to keep projects portable it is advisable to keep those references relative (macro or regkey). So the path is solved at every GDB launch. If first all Segger regkeys must be iterated this will give extra overhead.

Cons:
- There is a bit of extra code needed in the installer.

Regards

This post has been edited 2 times, last edit by "EmBlocks" (Mar 22nd 2013, 11:53am)