issue with the new Jlink command line tools on ubuntu 19.04

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

    • issue with the new Jlink command line tools on ubuntu 19.04

      I've installed the new tools yesterday, JlinkRTTClient does not connect to the 19021 port for some reason, telnet does! after trying to connect with JlinkRTTClient i can't connect with telnet either, ss command shows 2 connections is state TIME_WAIT and FIN_WAIT:

      Source Code

      1. CLOSE-WAIT1 0 127.0.0.1:19021 127.0.0.1:35056
      2. FIN-WAIT-20 0 127.0.0.1:35056 127.0.0.1:19021
      3. FIN-WAIT-20 0 127.0.0.1:35054 127.0.0.1:19021
      4. CLOSE-WAIT1 0 127.0.0.1:19021 127.0.0.1:35054
      it worked just fine in the previous version.

      connecting to feather nrf52 (adafruit/nordic) using segger edu mini

      EDIT:
      I just checked and apparently i can't see logs in any app using JLinkRTTViewer, JLinkLogger and JLinkExec with Telnet (like i wrote before JLinkRTTClient does not connect).

      The post was edited 1 time, last by eyal.gal ().

    • i donwngraded the segger tools to version 6.42, now JLinkRTTClient works but i still can't see logs!!!!
      trying to use JLinkRTTLogger results in getting:

      Brainfuck Source Code

      1. SEGGER J-Link RTT Logger
      2. Compiled Jan 30 2019 17:40:16
      3. (c) 2016-2017 SEGGER Microcontroller GmbH, www.segger.com
      4. Solutions for real time microcontroller applications
      5. ------------------------------------------------------------
      6. Device name. Default: NRF51822_XXAA >
      7. Target interface. >
      8. Interface speed [kHz]. Default: 4000 kHz >
      9. RTT Control Block address. Default: auto-detection >
      10. RTT Channel name or index. Default: channel 1 > 0
      11. Output file. Default: RTT_<ChannelName>_<Time>.log >
      12. ------------------------------------------------------------
      13. Connected to:
      14. J-Link EDU Mini V1 compiled May 27 2019 15:50:07
      15. S/N: 801004717
      16. Searching for RTT Control Block...
      Display All
      when i connected my j-link after upgrading to 6.46 the fw was updated too, could have defected it maybe ?
    • Hello,

      when i connected my j-link after upgrading to 6.46 the fw was updated too, could have defected it maybe ?
      No, I do not think so.

      If you can't see logs (I assume you are talking about RTT output) in any of our software, this may have several reasons.
      In order to investigate this behavior, could you please answer the following questions?

      1) Did you make sure that your target is running an application that makes use of RTT? For example, using SEGGER_RTT_printf(..)?
      2) Are you using some kind of low-power mode on your target device? If so, could you please disable it? Please refer to SEGGER Wiki - General information about RTT
      3) Are you running other applications that use J-Link (e.g. an IDE like SEGGER Embedded Studio) in parallel to the J-Link RTT Logger?
      Best regards,
      Leon.