enable modem trace logs.

[Pradeep Gamidi]

Hi,

i want collect modem trace logs for nRF9160, can you please help with steps how to collect modem trace logs

BR,

Pradeep Gamidi

[Pradeep Gamidi]

Thanks Runar for update,
I'm currently working on enabling modem trace logs for the nRF9160 using nRF Connect SDK version 1.7.0 and modem firmware version 1.3.0. I’ve followed the recommended configurations by adding the following macros to my prj.conf file:

# Enable modem trace CONFIG_NRF_MODEM_LIB_TRACE=y # Select the backend for trace output CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_RTT=y

However, I am encountering the following errors:

prj.conf:189: warning: attempt to assign the value 'y' to the undefined symbol NRF_MODEM_LIB_TRACE error: Aborting due to Kconfig warnings CMake Error at C:/H565935/CL5G_R200/zephyr/cmake/kconfig.cmake:268 (message): command failed with return code: 1 Call Stack (most recent call first): C:/H565935/CL5G_R200/zephyr/cmake/app/boilerplate.cmake:554 (include) C:/H565935/CL5G_R200/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include) C:/H565935/CL5G_R200/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate) CMakeLists.txt:31 (find_package) -- Configuring incomplete, errors occurred! FATAL ERROR: command exited with status 1: 'C:\H565935\CL5G_R200\toolchain\opt\bin\cmake.EXE' '-DWEST_PYTHON=C:\H565935\CL5G_R200\toolchain\opt\bin\python.exe' '-BC:\H565935\CL5G_R200\cp_r200_app\build' '-SC:\H565935\CL5G_R200\cp_r200_app' -GNinja -DBOARD=nrf9160_cl5gmns

It appears that the NRF_MODEM_LIB_TRACE and NRF_MODEM_LIB_TRACE_BACKEND_RTT symbols are not recognized. Could you please provide guidance on how to properly enable modem trace logging with this SDK version? If these features are not supported in SDK 1.7.0, is there an alternative approach.

Thank you for your assistance.

[runsiv]

Hi

Try to use CONFIG_NRF_MODEM_LIB_TRACE_ENABLED instead of CONFIG_NRF_MODEM_LIB_TRACE. If you want RTT you can use CONFIG_NRF_MODEM_LIB_TRACE_MEDIUM_RTT

Regards

Runar

[runsiv]

Hi

Since you are using RTT, could you try to use Segger RTT viewer and use log to file, and then import it into Cellular Monitor?

Regards

Runar

[Pradeep Gamidi]

Hi Runar,

I have attempted to use the Segger RTT viewer for capturing logs, but I am not receiving all the logs. I have attached a screenshot for your reference.

[runsiv]

Hi Pradeep

Was there anything in the log file? What did you see when you tried to import the log file into cellular monitor? 

Regards

Runar

[Pradeep Gamidi]

Hi Runar,

The log file generated contains unreadable data and cannot be imported into the Cellular Monitor because it is saved with a .log extension. Could you please provide guidance on how to generate a log file that can be used with the Cellular Monitor?

[runsiv]

Hi Pradeep

Did you save the log as .bin as I wrote in the instructions? Just renmae the file from logfile.log to logfile.bin

runsiv said:

• Use the J-Link RTT logger to collect the trace or traces and save in binary (.bin) format.
  See SEGGER Real Time Transfer (RTT) for more information.
• Load and playback the trace in Cellular Monitor.
  See Loading modem traces for playback for more information.

Regards

Runar

[Pradeep Gamidi]

Hi Runar,

As mentioned, I have saved the log file with a .bin extension. However, when I loaded this file into the Cellular Monitor, it did not display any data. I am attaching the log file for your reference.

Could you please assist in resolving this issue?

datalog.bin

[runsiv]

Hi

Could you confirm a thing for me. Are you connect to turkcell over NB-Iot? If so set AT%XEPCO=0 as Turkcell do not support ePCO. If you run into issues after that you can provide a new trace. 

What is the issues you are experiencing? 

Try

Regards

Runar

[Pradeep Gamidi]

Hi Runar,

We are not using Turkcell; we are working with Cat M1 and enabling eDRX feature.

[Øyvind]

Hello, 

Runar had to prioritize another issue and asked me to handle this ticket for him. There might have been an issue with the modem trace that you provided, as we are not able to convert it correctly. Seems to be corrupted and very short.

In your prj.conf can you please test with the following change:
CONFIG_RTT_CONSOLE=n

Kind regards,
Øyvind

[Øyvind]

I did some testing on my side. Building the asset tracker v2 application from NCS v1.7.1 and adding the following configurations to the prj.conf

# Segger RTT
CONFIG_LOG=y
CONFIG_USE_SEGGER_RTT=y
CONFIG_RTT_CONSOLE=n
CONFIG_LOG_BACKEND_RTT=y
CONFIG_UART_CONSOLE=n
CONFIG_LOG_BACKEND_UART=n

CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y
CONFIG_NRF_MODEM_LIB_TRACE_MEDIUM_RTT=y

Then I started the Segger RTT Logger application with the following command in command line (Windows):

nrfjprog --reset && "C:\Program Files\SEGGER\JLink_V794e\JLinkRTTLogger.exe" -Device NRF9160_XXAA -If SWD -Speed 5000 C:\Temp\Support\328159\modemtrace.bin

You may need to change the path to JLinkRTTLogger.exe, but everything else should be the same.

The modemtrace.bin that was the output provided me with correct information and a working modem trace.