• State Not Answered
  • Replies 20 replies
  • Subscribers 73 subscribers
  • Views 8432 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 214373
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

RTT Viewer / nrfjprog Issue

jsample

If I have the J-Link RTT Viewer open and connected to my PCA10056 (viewing RTT output from an external board connected to P19) and then reprogram the board using nrfjprog this will result in both nrfjprog and RTT Viewer locking up until I unplug and plug back in the PCA10056.  When this happens RTT Viewer prints the following error: "Communication timed out: Requested 12 bytes, received 0 bytes!"  Sometimes this won't happen and it will program just fine and RTT will print out after the boards resets, but the majority of the time it does.  This never used to happen though and I'm not sure what changed to cause it.  If I disconnect the RTT Viewer, program, then reconnect RTT I don't have any problems, but it's annoying to have to do this everytime I want to program the board.

Has anyone one else had this problem?

Parents
  • 0

    Hi John,

    It is not possible to run nrfjprog while connected to the RTT viewer. The tools use the same virtual com port and only one can be connected at a time.

    In my experience with Windows systems, this has always been the case. I would not think that this would be OS dependent issue. But I wanted to add this just in case.

    Best regards,

    Jeff

  • 0 in reply to Jeff4BLE

    Hi Jeff,

    From my experience on Windows when things are working I can have RTT Viewer open and logging, flash a new build via nrfjprog and then RTT Viewer will pick up the RTT output after the chip resets without issue.

    When things aren't working I'll have to disconnect RTT, then flash via nrfjprog, then reconnect.

    John

  • 0 in reply to jsample

    John and Turbo J,

    One of my colleagues informed me that there was an older combination of older RTT and nrfjprog programs that do not like a shared connection. Apparently this was some time ago and I never picked up on that change.  

    Today, using a slightly modified ble_app_uart application, nrfjprog 9.8.1, RTT Viewer V6.40, and Tera Term V4.1, did a little experimenting. All three  maintained the desired connection through erasing, reprogramming, and uart interaction. I was even able to use Segger Embedded Studio to make changes and program the DK without losing the RTT and Tera Term connections.

    As I suspect there may be some platform dependencies, I should note I am running Win 10 and I used the new nrf_command_line tools for Win 64. 

    Best Regards,

    Jeff

  • 0 in reply to Jeff4BLE

    Jeff,

    I didn't even know there was a 64 bit version of the command line tools.  Unfortunately I see the same issues as when I was using the 32 bit version though.  I don't know what it is with my system - I'm running Win 10 as well.

    John

Reply Children
Related
Terms of service