Search Results

I have two projects in one solution. Both projects should have their own build configurations. Let's say project1 has build configurations buildconfig1 and buildconfig2 based on commonbuildconfig1, and project2 has build configurations buildconfig3 and buildconfig4 based on commonbuildconfig2. How can this be accomplished? It seems the build configurations are always on a solution level somehow. For example, if the selected build configuration (in the UI) is buildconfig1, both project1 and proje…

I think I have the same problem: I have two projects in one solution. Both projects should have their own build configurations. Let's say project1 has build configurations buildconfig1 and buildconfig2 based on commonbuildconfig1, and project2 has build configurations buildconfig3 and buildconfig4 based on commonbuildconfig2. How can this be accomplished? It seems the build configurations are always on a solution level somehow. For example, if the selected build configuration (in the UI) is buil…

JLink serials: 760049244 and 760048979. This only happens when using the remote server in LAN mode. Connection sequence: J-Link1 Remote->J-Link2 Remote->Debug Session 1->Debug Session 2 When stopping debug session1, debug session 2 is disconnected, and the JLink cannot be connected to anymore. Only after power cycling the JLink (disconnecting and reconnecting USB), it can be connected again. Both remote servers run on the same host, on different ports.

Hi Nino, after some more testing I found there must be a timeout of 5 minutes somewhere when using the tunnel. This means: if a client does not connect to the remote server through the tunnel within 5 minutes after starting the remote server, the remote server needs to be restarted before a client can connect. Since I have access to the LAN through VPN, I would prefer to work without the tunnel. Unfortunately, this is not workable for me due to the issue described in: Stopping a debug session in…

Yes that works! Is there some kind of timeout on the connection from remote server to the tunnel server? It seems I cannot connect anymore after some time, even though the remote server still indicates "Waiting for client authentication". The main reason I want to use the tunnel connection is because of the problem as described in: Stopping a debug session in one SES instance disconnects JLINK in other SES instance

I tried those steps. See attached screenshots. Using JLink.exe, I can connect through the tunnel. Using SES 4.42 I can not connect through the tunnel. I tried both IP tunnel:SN and IP SN. forum.segger.com/index.php/Attachment/3857/ forum.segger.com/index.php/Attachment/3858/ forum.segger.com/index.php/Attachment/3861/ forum.segger.com/index.php/Attachment/3859/ forum.segger.com/index.php/Attachment/3860/

How to setup SES solution options to connect to a remote JLink through a tunnel? "IP 012345678" or "IP tunnel:012345678" with JLink serial 012345678 does not seem to work.

My setup consists of two targets connected to a host through two USB JLinks. This host runs two instances of Jlink Remote server (on two different ports). On my dev machine, I run two instances of SES and start debugging. When stopping the debug session on the SES instance where the debug session was started first, the JLink connection on the second SES instance is also disconnected. Moreover, when both targets are streaming RTT data, the target where the debug session was started second (and is…