I hope here is the right place to response to you lines. Because I find it not anyway I copy your answer.
>>Other Options -> -s -scriptfile C:/Scripts/myJLinkScript
if the script is located in the project, you can specify it with a relative name.
if the script is located outside Eclipse, define a substitution variable to the path and >>specify the relative name to it.
these aspects are very important if you set the debug configuration to be stored in the >>project, and you want to share the project with someone else.
OK, but if I try to use a path variable in Other Options like this:
-s -scriptfile ${jlink_path}/myJLinkScript
this will fail and I get a error message in the console later
Connecting to target...ERROR: Could not open script file [${jlink_path}/myJLinkScript]
I guess the variable will not supplemented in this line and send 1:1 to the jlinkGDBServer.
since this is a bug report, a better place would be the Bugs tracker.
I entered the bug there (#99) and will fix it soon.
fixed, please try the version from updates-test and let me know if it worked for you.
after installing the the version from the test directory I can no more debug at all.
I get a error message. I have deinstalled the plug-in and installed the old but it is the same problem. I hope there is no other reason, but mabye you have an idea.
Now it is working. After reinstall Eclipse and using the version from today it is working.
Many thanks for your work.