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?

[Kenneth]

Hi,

Not sure if I have any good idea other than try to download the latest and greatest, e.g.:
https://www.nordicsemi.com/eng/nordic/Products/nRF52-DK/nRF5x-Command-Line-Tools-Win32/51499 

If still not luck try directly:
https://www.segger.com/downloads/jlink/#J-LinkSoftwareAndDocumentationPack 

If still not luck try not to use USB hub or change USB port.

Best regards,
Kenneth

[jsample]

Hi Kenneth,

So at the time I initially posted about this issue i was using version 9.7.3 of the command line tools and I'm pretty sure I had updated the Segger software to a newer version that didn't come with 9.7.3 but I can't remember what version it was.  I uninstalled the command line tools and all of the Segger software and did a clean install of 9.7.3 and everything was back to working normally.

Recently I updated to version 9.8.0 of the command line tools and started having the same issues again.  Uninstalling that and reinstalling 9.7.3 has it working again.  So maybe its a compatibility issue between the command line tools and the newer Segger software?

John

[jsample]

Hi Håvard,

A clean 9.7.3 install works consistently without issue and a clean 9.8.0 doesn't.  As for the "newer Segger software" looking back at my downloads folder I had 6.34e downloaded in September so it was most likely that version.  I haven't tried 6.40.

There is no important reason to use 9.8.0 so I'll stick with 9.7.3 for now.

John

[jsample]

Hi Håvard,

One more thing I wanted to mention I noticed when using 9.8.0 is that the data shows up in the RTT Viewer very slowly compared to when using 9.7.3.  When I do a reset on my project about 80 lines of RTT debug spit out as everything initializes and with 9.7.3 they all show up together pretty immediately, but with 9.8.0 the lines show up slowly in chunks and it takes several seconds for everything to appear.

John

[Håvard]

Good news jsample!

Looks like  nRF5x-Command-Line-Tools v9.8.1 has just been released.

It uses the newes J-Link V6.40

Could you try it and let us know if you have any luck?

[jsample]

Hi Håvard,

I'm still seeing the same issues with 9.8.1 and 6.40.  One other thing I'm noticing with the 6.40 RTT Viewer is that every time I try to connect I get a popup titled: "J-Link V6.40 Script file not found".  The text reads: "Could not find script file referenced by debugger: unspecified Proper functionality cannot be guaranteed".

John

[Jeff4BLE]

Hi John,

As indicated in my early message today. I have been able to get nRFjprog 9.8.1 and RTT Viewer V6.40 to operate concurrently in the way you expect. I was even able to use SES to program and debug and maintain the RTT connection.

I do not recall seeing the specific popup you are describing. But until I selected the initial "Specify Target Device" I repeatedly received a popup directing me to pick a device to connect with.

Do you have anything in the "Script fie (optional)" dialog box?

Though unlikely, it's may be possible the issue you are seeing is device dependent. What device are your working with? More likely, you are experiencing an system environment issue.

I have not tried 9.7.3. But I did notices that depending on the amount of log data and the BLE traffic, there was a very noticeable lag from the time an event occurred before is was logged to the RTT window.

I may look into that a bit more later.

Best regards,

Jeff

[Jeff4BLE]

John,

This video shows CLT and RTT working together as desired. I am investigating why it's taking RTT so long to flush it's buffers.

The programs are the same. I only change the output string.

Cheers,

Jeff