RTT Viewer doesn't show any debug messages from nrf52833.

[bini2007]

We use nrf52833 chip but I don't know which SDK and version.

but I used "s113_nrf52_7.2.0_softdevice.hex" in our project having started on 2021.01.27.

So, It's old project starting before.

The problem is as followings:

Our target device is connected with RTT Viewer.

However, RTT Viewer dosen't show any log messages from our target device.

Our project's current configuration for RTT logging are as followings on "sdk_config.h" header file.

1. define belows. 

#define NRF_LOG_ENABLED 1

#define NRF_LOG_BACKEND_RTT_ENABLED 1

2. call on main() function.

NRF_LOG_DEFAULT_BACKENDS_INIT();

Do we have to do more anything for logging on RTT Viewer?

In addition, I attach our "sdk_config.h" file.

Please check it and advice me.

4010.sdk_config.h

[bini2007]

I found missing definition used in SEGGER_RTT_Syscalls_GCC.c file.

So I added the definition on our project source.

However, it dosen't work with RTT Viewer via swd.

First of all, we can connect  our target through J-link OB debugger RTT viewer.

The following log says:

LOG: J-Link RTT Viewer V7.94e: Logging started.
LOG: Terminal 0 added.
LOG: Connecting to J-Link via USB...
LOG: Device "NRF52833_XXAA" selected.
LOG: InitTarget() start
LOG: CTRL-AP indicates that the device is secured.
For debugger connection the device needs to be unsecured.
Note: Unsecuring will trigger a mass erase of the internal flash.


LOG: Executing default behavior previously saved in the registry.
LOG: Device will be unsecured now.
LOG: InitTarget() end - Took 230ms
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 000BB00C SCS-M7
LOG: [0][1]: E0001000 CID B105E00D PID 003BB002 DWT
LOG: [0][2]: E0002000 CID B105E00D PID 002BB003 FPB
LOG: [0][3]: E0000000 CID B105E00D PID 003BB001 ITM
LOG: [0][4]: E0040000 CID B105900D PID 000BB9A1 TPIU
LOG: [0][5]: E0041000 CID B105900D PID 000BB925 ETM
LOG: RTT Viewer connected

Then, we couldn't see the device logs from our target using RTT viewer.

I guess the conditions goes good a little, however we can't see the logs.

Please advice me.

Thanks,

Jaehong Park

[bini2007]

I tested ble_app_uart, example on nRF53833 DK when I use on SES and RTT Viewer.

The example works well on nRF52833 DK as following SES and RTT Viewer's screenshots.

1. SES

2. RTT Viewer

Then on RTT viewer, it works when I pressed reset button on DK board after connecting nRF SoC using J-link OB. I guess it needs to restart the appllication after connecting to nRF SoC on DK board.

First of all, our target only use 4 pins in swdio, swdclk, Vdd, Gnd.

So, do we have to connect reset pin on our custom target with J-link OB on DK?

and then I mean give the reset signal to our custom target via reset pin after connection with j-link OB.

Please guide us how.

Thanks,

Jaehong Park