How to use the JLinkRemoteServer CL version

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • How to use the JLinkRemoteServer CL version

      I'm using successfully the JLinkRemoteServer GUI with the following configuration:(see attached file)


      I want my computer to launch Jlink server at startup.
      Therefore I want to use the headless version: JLinkRemoteServerCl.exe, but I'm not able to connect succesfully.

      My guess is that I'm not using the correct flag, but the ? help is not very detailed.
      How do I reproduce my config using command line flags?
      Regards,
      Gabriel
      Images

      • 2024-07-23 15_10_22-192.168.10.150 - Remote Desktop Connection.png

        14.18 kB, 383×297, viewed 88 times

    • Hello,

      It seems like you are using just the default settings of the remote server, so no additional command line options should be needed.

      Could you please provide one log of the failing scenario and one of the successful one?

      The log can be enabled with "-Log <LogFilePath>".

      Best regards,
      Simon
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.

    • Hi Simon, thanks for your support.

      Log when successful (using JLinkRemoteServer.exe -Log C:\dev\jl.log)

      Source Code

      1. T0D1C 000:000.820 SEGGER J-Link V7.96 Log File
      2. T0D1C 000:001.657 DLL Compiled: Mar 7 2024 16:49:04
      3. T0D1C 000:001.672 Logging started @ 2024-07-29 19:17
      4. T0D1C 000:001.685 Process: C:\Program Files\SEGGER\JLink_V796\JLinkRemoteServer.exe
      5. T0D1C 000:001.700 - 1.697ms
      6. T0D1C 000:001.976 JLINK_Open()
      7. T0D1C 000:007.198 Firmware: J-Link V12 compiled Mar 14 2024 13:16:19
      8. T0D1C 000:008.069 Firmware: J-Link V12 compiled Mar 14 2024 13:16:19
      9. T0D1C 000:010.311 Hardware: V12.00
      10. T0D1C 000:010.373 S/N: 822000298
      11. T0D1C 000:010.402 OEM: SEGGER
      12. T0D1C 000:010.428 Feature(s): GDB
      13. T0D1C 000:011.935 Bootloader: 2022 Oct 19
      14. T0D1C 000:015.727 USB speed mode: High speed (480 MBit/s)
      15. T0D1C 000:016.076 TELNET listener socket opened on port 19021
      16. T0D1C 000:016.403 WEBSRV WEBSRV_Init(): Starting webserver thread(s)
      17. T0D1C 000:016.555 WEBSRV Webserver running on local port 19080
      18. T0D1C 000:016.654 Looking for J-Link GUI Server exe at: C:\Program Files\SEGGER\JLink_V796\JLinkGUIServer.exe
      19. T0D1C 000:016.690 Forking J-Link GUI Server: C:\Program Files\SEGGER\JLink_V796\JLinkGUIServer.exe
      20. T0D1C 000:040.377 J-Link GUI Server info: "J-Link GUI server V7.96 "
      21. T0D1C 000:042.698 - 40.686ms returns "O.K."
      22. T0D1C 000:042.826 JLINK_EMU_GetCurrConnectionInfo()
      23. T0D1C 000:043.003 - 0.178ms returns 0
      24. T0D1C 000:043.031 JLINK_GetSN()
      25. T0D1C 000:043.037 - 0.008ms returns 822000298
      26. T32E8 022:285.482 JLINK_Lock()
      27. T32E8 022:285.534 JLINK_CommunicateEx(0xDEC9DDF0, 0x0001 Bytes, 0xDED13FA0, 0x0072 Bytes, IsCommand == 1)
      28. T32E8 022:286.004 - 0.469ms returns 0x72
      29. T32E8 022:287.988 JLINK_CommunicateEx(0xDEC9DDF0, 0x0001 Bytes, 0xDED13FA0, 0x0004 Bytes, IsCommand == 1)
      30. T32E8 022:289.572 - 1.581ms returns 0x04
      31. T32E8 022:291.638 JLINK_CommunicateEx(0xDEC9DDF0, 0x0001 Bytes, 0xDED13FA0, 0x0020 Bytes, IsCommand == 1)
      32. T32E8 022:293.550 - 1.911ms returns 0x20
      33. T32E8 022:295.666 JLINK_CommunicateEx(0xDEC9DDF0, 0x0001 Bytes, 0xDED13FA0, 0x0072 Bytes, IsCommand == 1)
      34. T32E8 022:296.036 - 0.371ms returns 0x72
      35. T32E8 022:319.188 JLINK_CommunicateEx(0xDEC9DDF0, 0x0001 Bytes, 0xDED13FA0, 0x0072 Bytes, IsCommand == 1)
      36. T32E8 022:319.606 - 0.420ms returns 0x72
      37. T32E8 022:321.794 JLINK_CommunicateEx(0xDEC9DDF0, 0x000E Bytes, 0xDED13FA0, 0x0004 Bytes, IsCommand == 1)
      38. T32E8 022:323.660 - 1.863ms returns 0x04
      39. T32E8 022:323.706 JLINK_Communicate(0x00000000, 0x0000 Bytes, 0xDED13FA4, 0x0200 Bytes)
      40. T32E8 022:323.884 - 0.179ms returns 0x200
      41. T32E8 022:325.842 JLINK_CommunicateEx(0xDEC9DDF0, 0x000E Bytes, 0xDED13FA0, 0x0004 Bytes, IsCommand == 1)
      42. T32E8 022:326.028 - 0.186ms returns 0x04
      43. T32E8 022:326.044 JLINK_Communicate(0x00000000, 0x0000 Bytes, 0xDED13FA4, 0x2000 Bytes)
      44. T32E8 022:326.470 - 0.427ms returns 0x2000
      45. T32E8 022:328.504 JLINK_CommunicateEx(0xDEC9DDF0, 0x0001 Bytes, 0xDED13FA0, 0x0004 Bytes, IsCommand == 1)
      46. T32E8 022:328.748 - 0.244ms returns 0x04
      47. T32E8 022:339.098 JLINK_CommunicateEx(0xDEC9DDF0, 0x0005 Bytes, 0xDED13FA0, 0x0004 Bytes, IsCommand == 1)
      48. T32E8 022:339.396 - 0.298ms returns 0x04
      49. T32E8 022:341.738 JLINK_CommunicateEx(0xDEC9DDF0, 0x000A Bytes, 0xDED13FA0, 0x0004 Bytes, IsCommand == 1)
      Display All


      The log with the failed attempt:


      Source Code

      1. T2E30 000:000.759 SEGGER J-Link V7.96 Log File
      2. T2E30 000:000.913 DLL Compiled: Mar 7 2024 16:49:04
      3. T2E30 000:000.927 Logging started @ 2024-07-29 19:19
      4. T2E30 000:000.938 Process: C:\Program Files\SEGGER\JLink_V796\JLinkRemoteServerCL.exe
      5. T2E30 000:000.952 - 0.951ms
      6. T2E30 000:000.988 JLINK_Open()
      7. T2E30 000:007.700 Firmware: J-Link V12 compiled Mar 14 2024 13:16:19
      8. T2E30 000:013.535 Firmware: J-Link V12 compiled Mar 14 2024 13:16:19
      9. T2E30 000:023.953 Hardware: V12.00
      10. T2E30 000:024.029 S/N: 822000298
      11. T2E30 000:024.057 OEM: SEGGER
      12. T2E30 000:024.085 Feature(s): GDB
      13. T2E30 000:031.910 Bootloader: 2022 Oct 19
      14. T2E30 000:037.609 USB speed mode: High speed (480 MBit/s)
      15. T2E30 000:047.105 TELNET listener socket opened on port 19021
      16. T2E30 000:047.226 WEBSRV WEBSRV_Init(): Starting webserver thread(s)
      17. T2E30 000:047.355 WEBSRV Webserver running on local port 19080
      18. T2E30 000:047.450 Looking for J-Link GUI Server exe at: C:\Program Files\SEGGER\JLink_V796\JLinkGUIServer.exe
      19. T2E30 000:047.480 Forking J-Link GUI Server: C:\Program Files\SEGGER\JLink_V796\JLinkGUIServer.exe
      20. T2E30 000:065.416 J-Link GUI Server info: "J-Link GUI server V7.96 "
      21. T2E30 000:067.456 - 66.465ms returns "O.K."
      22. T2E30 000:067.529 JLINK_EMU_GetCurrConnectionInfo()
      23. T2E30 000:069.137 - 1.609ms returns 0
      24. T2E30 000:069.163 JLINK_GetSN()
      25. T2E30 000:069.168 - 0.005ms returns 822000298
      Display All


      Regards,
      Gabriel

    • Hello,

      The logs appear to be fine.

      It's possible that the port (19021) is being blocked by your firewall, or that the RemoteServerCL application does not have the necessary permissions to access your local network.

      Best regards,
      Simon
      Please read the forum rules before posting.

      Keep in mind, this is *not* a support forum.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/
      Or you can contact us via e-mail.

    • Hi Simon,


      Thanks for checking the log.

      Can you elaborate on the permission/firewall issues?
      Don't you think it would be surprising that RemoteServerCL would be blocked, but RemoteServer would work fine?

      Regards,
      Gabriel