[SOLVED] Stopping a debug session in one SES instance disconnects JLINK in other SES instance

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

  • [SOLVED] Stopping a debug session in one SES instance disconnects JLINK in other SES instance

    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 automatically disconnected) cannot be connected to anymore without power cycling.

    JLINK 6.62a
    SES 4.42 64-bit
    targets: nordic nrf52

  • Hello,

    Thank you for your inquiry.
    Such an issue is not known to us.
    Could you provide the serial numbers of the J-Links you are using?
    Are you using the remote server in tunnel mode or in local LAN?
    How is your connection sequence?
    - J-Link1 Remote->J-Link2 Remote->Debug Session 1->Debug Session 2
    or
    - J-Link1 Remote->Debug Session 1->J-Link 2 Remote->Debug Session 2
    or something else?

    Best regards,
    Nino
    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.

  • 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.

  • Hello,

    Thank you for providing more details.
    The reported behaviour is reproducible and we are checking if this can be fixed.
    Keep you posted.

    Best regards,
    Nino
    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.

  • Hello,

    Quick update. This should be fixed in the latest J-Link software. Could you give it a try? Simply install the latest J-Link software package.
    segger.com/downloads/jlink/#J-…twareAndDocumentationPack
    On Windows you will be prompted with the DLL updater at the end of the installation. Make sure the Embedded Studio version is selected and Embedded Studio is closed. Then simply press OK.
    On macOS and Linux you would have to update the J-Link DLL (.so) manually.

    Could you verify that the issue is resolved in the latest J-Link software version?

    Best regards,
    Nino
    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.