Can't get nRF52811 based sample projects to display on Segger J-Link RTT Viewer

RE: Can't get nRF52811 based sample projects to display on Segger J-Link RTT Viewer

keegretupmoc — Thu, 06 Feb 2025 02:05:24 GMT

Hi Kazi,

Yes, it's very perplexing. I finally just gutted my working project (RTT displays) and put the direct_test_mode code in it and kind of got it working. Hopefully well enough.

It seems to be the SOC setup we have I guess. Something in my project that is needed for even the simple projects to work on.

Since I am past that with my workaround you can close out the ticket.

Thanks,

RE: Can't get nRF52811 based sample projects to display on Segger J-Link RTT Viewer

Kazi Afroza Sultana — Tue, 04 Feb 2025 16:57:46 GMT

I tried your sample, and it worked on the nrf52832 DK for version v2.9.0 with some modification of the header file. That I mentioned on my previous reply.

Now I have tried this on v2.0.0 as same as you. It worked (for old version there is no error related to log.h file, so no modification was needed).

below is my configuration of RTT viewer.

RE: Can't get nRF52811 based sample projects to display on Segger J-Link RTT Viewer

keegretupmoc — Wed, 29 Jan 2025 00:17:05 GMT

Kazi,

Yeah, 2.0.0 is very old. We will be working on getting to the current version. But right now we are on this version. We have an app that is currently running on the nRF52811 processor that is sending RTT data to the display. So I know it works under the SDK version 2.0.0

I have two projects from the samples/bluetooth directory on SDK 2.0.0 under nrf (direct_test_mode and peripheral_uart) that I have been trying to get RTT display working on and it doesn't work. I have also beein trying to get the minimal_log.zip working, which it doesn't work either.

I have spent many hours on this and still no luck. So I am sure there is something in our code on the working version (which I call the BLE) that must not be on the other test projects, but I don't see it. I have done a lot of combing around looking at parameters from proj.conf and what they eventually become in .config and haven't really seen anything there.

I have tried the logger thread on and off (it's off on our working software I think). So I have looked at a lot of things.

I really need to get this working because I need to do an FCC cert on it soon. So any helpful hints you might have would be appreciated.

How does the rtt suff exactly work?

We have the J-Link interface connected to the board on the JTAG I believe. So we aren't using any UARTs specifically. It's through the SWO/CLK/IO.

It would really be helpful to get this working through for what I need to do.

Thanks,

RE: Can't get nRF52811 based sample projects to display on Segger J-Link RTT Viewer

Kazi Afroza Sultana — Tue, 28 Jan 2025 14:16:50 GMT

Hello,

You are using NCS version 2.0.0? It is very old.

I have tried to reproduce the minimal_log.zip on NCS version 2.9.0. Initially it shows there is no file like logging/log.h

This is because there is no use of ''#include "logging/log.h" in current NCS version. The include statement for public zephyr headers has changed what was on NCS v2.0.0.

The proper way to include the logging header in NCS 2.9.0 is:

#include <zephyr/logging/log.h>

Then it worked as expected.

Have you set the target device properly? Which version of RTT viewer you are using?

RE: Can't get nRF52811 based sample projects to display on Segger J-Link RTT Viewer

keegretupmoc — Sun, 26 Jan 2025 01:59:30 GMT

I found another devzone article with a zip file (minimal_log.zip) that has a project that just does what I need it to do. I have downloaded it and built it, but it doesn't output any data either. I do see it connect to the RTT display though:

devzone.nordicsemi.com/.../how-to-enable-ncs-rtt-logging

RE: Can't get nRF52811 based sample projects to display on Segger J-Link RTT Viewer

keegretupmoc — Sat, 25 Jan 2025 20:21:54 GMT

A little extra info. On the J-Link RTT Viewer output, I can see that we are able to connect, but nothing displays:

LOG: Connecting to J-Link via USB...
LOG: Device "NRF52811_XXAA" selected.
LOG: InitTarget() start
LOG: InitTarget() end - Took 2.09ms
LOG: Found SW-DP with ID 0x2BA01477
LOG: DPIDR: 0x2BA01477
LOG: CoreSight SoC-400 or earlier
LOG: Scanning AP map to find all available APs
LOG: AP[2]: Stopped AP scan as end of AP map has been reached
LOG: AP[0]: AHB-AP (IDR: 0x24770011)
LOG: AP[1]: JTAG-AP (IDR: 0x02880000)
LOG: Iterating through AP map to find AHB-AP to use
LOG: AP[0]: Core found
LOG: AP[0]: AHB-AP ROM base: 0xE00FF000
LOG: CPUID register: 0x410FC241. Implementer code: 0x41 (ARM)
LOG: Found Cortex-M4 r0p1, Little endian.
LOG: FPUnit: 6 code (BP) slots and 2 literal slots
LOG: CoreSight components:
LOG: ROMTbl[0] @ E00FF000
LOG: [0][0]: E000E000 CID B105E00D PID 000BB000 SCS
LOG: [0][1]: E0001000 CID B105E00D PID 003BB002 DWT
LOG: [0][2]: E0002000 CID B105E00D PID 002BB003 FPB
LOG: RTT Viewer connected.

It's setup correctly, with the USB and Serial number, target device correct, interface SWD at 4000kHz and Auto Detection. And as I said before the same display will correctly display our current real app that originally used peripheral_uart as a template. So it seems to be something with these sample apps...