RTT Viewer / nrfjprog Issue

RE: RTT Viewer / nrfjprog Issue

jsample — Wed, 31 Oct 2018 15:01:44 GMT

Hi Jeff,

By default the script file box was populated with the text "undefined", but I've found if I clear that then I don't get the popup I mentioned. It was "undefined" on the older version as well, but didn't cause the popup so it must just be a change Segger made. This doesn't seem to change the behavior in any way though.

The device I am programming is a custom nRF52840 board connected to the PCA10056 through the P19 Debug out connector. I just tried disconnecting my board and programming the PCA10056 itself and see the same issues though.

One more thing I've noticed is that when the issue occurs and nrfjprog and RTT Viewer both lock up, if I wait awhile instead of resetting the dev board Windows will eventually give me a "USB Device not recognized popup". If I go into Device Manger the PCA10056 no longer shows up under ports and is instead listed as an "Unknown USB Device (Device Descriptor Request Failed".

So maybe the problem is with the PCA10056?

John

RE: RTT Viewer / nrfjprog Issue

Jeff4BLE — Wed, 31 Oct 2018 02:54:49 GMT

John,

devzone.nordicsemi.com/.../CLT-and-RTT.mp4

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

RE: RTT Viewer / nrfjprog Issue

Jeff4BLE — Tue, 30 Oct 2018 21:21:24 GMT

I have used PCA10056 V1.0.0 and PCA10040 V1.0.1.

RE: RTT Viewer / nrfjprog Issue

jsample — Tue, 30 Oct 2018 21:14:01 GMT

I'm using a PCA10056 V1.0.0 my coworker is using a PCA10040 V1.0.0.

RE: RTT Viewer / nrfjprog Issue

Jeff4BLE — Tue, 30 Oct 2018 21:10:17 GMT

What version of the PCA10056 board are you using?

RE: RTT Viewer / nrfjprog Issue

Jeff4BLE — Tue, 30 Oct 2018 21:07:38 GMT

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

RE: RTT Viewer / nrfjprog Issue

jsample — Tue, 30 Oct 2018 21:01:59 GMT

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

RE: RTT Viewer / nrfjprog Issue

Jeff4BLE — Tue, 30 Oct 2018 20:55:18 GMT

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

RE: RTT Viewer / nrfjprog Issue

jsample — Tue, 30 Oct 2018 20:48:45 GMT

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

RE: RTT Viewer / nrfjprog Issue

Jeff4BLE — Tue, 30 Oct 2018 20:16:28 GMT

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

RE: RTT Viewer / nrfjprog Issue

jsample — Tue, 30 Oct 2018 18:28:54 GMT

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

RE: RTT Viewer / nrfjprog Issue

Håvard — Tue, 30 Oct 2018 17:10:17 GMT

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?

RE: RTT Viewer / nrfjprog Issue

jsample — Mon, 29 Oct 2018 21:12:20 GMT

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

RE: RTT Viewer / nrfjprog Issue

jsample — Mon, 29 Oct 2018 20:48:48 GMT

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

RE: RTT Viewer / nrfjprog Issue

jsample — Mon, 29 Oct 2018 20:45:29 GMT

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

RE: RTT Viewer / nrfjprog Issue

Turbo J — Mon, 29 Oct 2018 20:22:53 GMT

There is a workaround for the RTT problem: The Segger GDB server.

It will not only allow you to flash the chip via (arm-none-eabi-)gdb, but you can use any telnet client (I use putty) to connect to the RTT port (localhost:19021 for the first RTT terminal).

RE: RTT Viewer / nrfjprog Issue

Jeff4BLE — Mon, 29 Oct 2018 19:12:01 GMT

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

RE: RTT Viewer / nrfjprog Issue

Håvard — Mon, 29 Oct 2018 18:27:46 GMT

Hi jsample,

I'm pretty sure a clean install of Command Line Tools 9.8.0 should work fine.

I'm a bit confused about what you actually have installed. (What is working what is not, what was installed when.)

Could you remove all traces of J-Link and other segger software, then install Command Line tools 9.8.0, and let me know how things are working?

When you say "newer Segger software" here, what are you referring to? Did you install J-Link V6.40 after installing the Command Line Tools?

You should be able to use the RTT viewer in J-Link V6.34g (The one used in 9.8.0)

Lastly, is there an important reason for you to use 9.8.0? If the solution remains elusive, you might just want to stick with 9.7.3 for your work environment. 🙂

RE: RTT Viewer / nrfjprog Issue

jsample — Mon, 29 Oct 2018 16:45:41 GMT

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

RE: RTT Viewer / nrfjprog Issue

Kenneth — Tue, 25 Sep 2018 06:49:18 GMT

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