Recently (after 10+ years of using J-Links) I have had occasion to use the J-Link Remote Tunnel server. Once to help out a co-worker who was remote working due to the pandemic situation, and once to diagnose and fix some problems a field team was having servicing a unit.
That software and service are totally awesome! Super easy to setup, and once connected everything works just like I was using the J-Link at my desk (only somewhat slower).
I would like to suggest a couple things that might help make a client connection go smoother:
1. The remote server software has a "Client connection string" (that looks like: "ip tunnel:mwb1100:password:jlink-america.segger.com"), but the client dialogs that let you connect to the remote server has separate fields for the name (mwb1100 here), password, and the tunnel server name. That's workable of course, but it would be nicer if I could just copy/past the "client connection string" that the guy running the remote server sends me in a message into some field. As far as I know, right now the client connection string is only directly useful as an argument to the jlink.exe "-IP" command line option.
2. in Jflash there isn't a way to set the tunnel configuration in the project settings dialog (there are only options for USB, USB SN, and TCP/IP - which will only accept a plain IP address or hostname). It would be nice if the project settings allowed an "IP via tunnel" configuration option or if I could paste the "ip tunnel:mwb1100:password:jlink-america.segger.com" connection string into the IP field and have it figure out that the tunnel server should be used instead of a plain IP connection.
3. related to #2, in JFlash it seems that the only way to get the dialog that allows you to specify the client tunnel configuration is to disconnect all local USB-connected J-Links. And you don't get the dialog that allows you to configure the tunnel connection until you try to connect to the target and JFlash finds no USB connected J-Links to use.
But all-in-all, the remote tunnel service was a godsend! Who is it I should buy a beer for?
Thanks!
That software and service are totally awesome! Super easy to setup, and once connected everything works just like I was using the J-Link at my desk (only somewhat slower).
I would like to suggest a couple things that might help make a client connection go smoother:
1. The remote server software has a "Client connection string" (that looks like: "ip tunnel:mwb1100:password:jlink-america.segger.com"), but the client dialogs that let you connect to the remote server has separate fields for the name (mwb1100 here), password, and the tunnel server name. That's workable of course, but it would be nicer if I could just copy/past the "client connection string" that the guy running the remote server sends me in a message into some field. As far as I know, right now the client connection string is only directly useful as an argument to the jlink.exe "-IP" command line option.
2. in Jflash there isn't a way to set the tunnel configuration in the project settings dialog (there are only options for USB, USB SN, and TCP/IP - which will only accept a plain IP address or hostname). It would be nice if the project settings allowed an "IP via tunnel" configuration option or if I could paste the "ip tunnel:mwb1100:password:jlink-america.segger.com" connection string into the IP field and have it figure out that the tunnel server should be used instead of a plain IP connection.
3. related to #2, in JFlash it seems that the only way to get the dialog that allows you to specify the client tunnel configuration is to disconnect all local USB-connected J-Links. And you don't get the dialog that allows you to configure the tunnel connection until you try to connect to the target and JFlash finds no USB connected J-Links to use.
But all-in-all, the remote tunnel service was a godsend! Who is it I should buy a beer for?
Thanks!