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

[Ø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. 

[Pradeep Gamidi]

Hi Øyvind,

After adding CONFIG_RTT_CONSOLE=n, I was able to collect the modem trace. Thank you for your support.

Thanks and Regards,
Pradeep Gamidi

[Øyvind]

Happy to hear! Are the modem trace usable as well? Is the information you need in the trace?

Kind regards,
Øyvind

[Øyvind]

Pradeep Gamidi did you run modem trace as instructed in my last comment? See below.

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

Please provide the modem trace here.