• State Not Answered
  • Replies 25 replies
  • Subscribers 66 subscribers
  • Views 816 views
  • Users 0 members are here
Attachments (2) Download All
Nordic Case Info
  • Case ID: 328159
Options

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

Parents
  • 0

    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.

  • 0 in reply to Pradeep Gamidi

    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

  • 0 in reply to runsiv

    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

  • 0 in reply to Pradeep Gamidi

    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

  • 0 in reply to runsiv

    Hi Runar,

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

  • 0 in reply to Pradeep Gamidi

    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

  • 0 in reply to Ø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. 

Reply
  • 0 in reply to Ø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. 

Children
Related