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?

[Jeff4BLE]

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

[jsample]

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

[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

[jsample]

Tried installing the latest on my coworkers Win10 computer as well and see the same behavior as my system.

[Jeff4BLE]

Hi John,

I just learned of the 64 bit version yesterday. I sent a note to the web team that this needs to be easier to find.

BTW- I just switched from using the PCA10040 to PCA10056. No changes in behavior.

Cheers,

Jeff