enable modem trace logs.

RE: enable modem trace logs.

Øyvind — Fri, 28 Jun 2024 10:29:24 GMT

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.

RE: enable modem trace logs.

Øyvind — Thu, 27 Jun 2024 08:22:49 GMT

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

Kind regards,
Øyvind

RE: enable modem trace logs.

Pradeep Gamidi — Thu, 27 Jun 2024 07:05:27 GMT

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

RE: enable modem trace logs.

Øyvind — Thu, 20 Jun 2024 10:44:42 GMT

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.

RE: enable modem trace logs.

Øyvind — Thu, 20 Jun 2024 08:48:21 GMT

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

RE: enable modem trace logs.

Pradeep Gamidi — Wed, 19 Jun 2024 10:37:32 GMT

Hi Runar,

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

RE: enable modem trace logs.

runsiv — Tue, 18 Jun 2024 12:02:26 GMT

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

RE: enable modem trace logs.

Pradeep Gamidi — Tue, 18 Jun 2024 09:32:50 GMT

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?

devzone.nordicsemi.com/.../datalog.bin

RE: enable modem trace logs.

runsiv — Mon, 17 Jun 2024 13:06:44 GMT

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

[quote user="runsiv"]

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.

[/quote]

Regards

Runar

RE: enable modem trace logs.

Pradeep Gamidi — Mon, 17 Jun 2024 08:57:11 GMT

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?

RE: enable modem trace logs.

runsiv — Mon, 17 Jun 2024 06:51:13 GMT

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

RE: enable modem trace logs.

Pradeep Gamidi — Sat, 15 Jun 2024 17:09:07 GMT

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.

RE: enable modem trace logs.

runsiv — Fri, 14 Jun 2024 06:58:12 GMT

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

RE: enable modem trace logs.

Pradeep Gamidi — Fri, 14 Jun 2024 05:11:52 GMT

Hi Runar,

As mentioned in the Minimum Requirements and Limitations, my modem firmware version is 1.3.1 and SDK version is 1.7.0, which do not meet the minimum requirements for modem trace logging.

We are currently blocked by an eDRX issue and urgently need modem trace logs to resolve it. Could you please suggest any alternative methods to obtain these logs? If necessary, we can arrange a call to discuss this high-priority issue.

RE: enable modem trace logs.

runsiv — Thu, 13 Jun 2024 08:15:28 GMT

In the current release of Cellular Monitor, the RTT interface is not supported for traces capture. You can only view RTT modem traces captured outside of the tool.

To view RTT modem traces captured outside of the tool in Cellular Monitor, complete the following steps:

Enable the RTT trace backend in your device’s application using the Kconfig option CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_RTT in the prj.conf file.
Ensure your device is running supported modem firmware, see Minimum requirements and limitations, and note the version for playback.
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

RE: enable modem trace logs.

Pradeep Gamidi — Thu, 13 Jun 2024 05:04:36 GMT

Thanks to your guidance, I successfully enabled modem trace logging on the nRF9160 by updating the configuration with CONFIG_LOG_BACKEND_RTT=y. The build and flash processes completed successfully.

Following the instructions in Lesson 7: Debugging with a Modem Trace, I performed the following steps:

Built and flashed the firmware from my workspace.
Sent the AT command AT%XMODEMTRACE=1,2<CR><LF>.
Downloaded the Cellular Monitor application from nRF Connect for Desktop to decode trace logs.

However, the Cellular Monitor application is not detecting the COM port for my device. Could you please assist me in resolving this issue so I can view the trace logs?

RE: enable modem trace logs.

runsiv — Tue, 11 Jun 2024 11:43:54 GMT

Could you try to enable CONFIG_LOG_BACKEND_RTT? According to this case it might fix the issue

Regards

Runar

RE: enable modem trace logs.

Pradeep Gamidi — Tue, 11 Jun 2024 09:11:18 GMT

Yes i have tested 'CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y' ,I am encountering error as shown below, posted prj.cnf for reference .

ERROR

c:/h565935/cl5g_r200/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: modules/nrf/lib/nrf_modem_lib/lib..__nrf__lib__nrf_modem_lib.a(nrf_modem_os.c.obj): in function `nrf_modem_os_trace_put':
C:/H565935/CL5G_R200/nrf/lib/nrf_modem_lib/nrf_modem_os.c:706: undefined reference to `SEGGER_RTT_ASM_WriteSkipNoLock'
collect2.exe: error: ld returned 1 exit status
[381/394] No install step for 'mcuboot_subimage'
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\H565935\CL5G_R200\toolchain\opt\bin\cmake.EXE' --build 'C:\H565935\CL5G_R200\cp_r200_app\build'

devzone.nordicsemi.com/.../25318.prj.conf

RE: enable modem trace logs.

runsiv — Tue, 11 Jun 2024 08:00:57 GMT

Could you post your prj.conf?

Since the issue seems to be related to RTT, do it work if you do not output the modem trace over RTT? Did you also test with CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y?

Regards

Runar

RE: enable modem trace logs.

Pradeep Gamidi — Tue, 11 Jun 2024 07:15:28 GMT

Hi Runar,

can you please suggest a solution for solving this issue.

Thanks and Regards,
Pradeep Gamidi.

RE: enable modem trace logs.

runsiv — Mon, 10 Jun 2024 13:20:59 GMT

I need to check regarding the SEGGER_RTT_ASM_WriteSkipNoLock. However regarding CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y is not the same as CONFIG_NRF_MODEM_LIB_TRACE=y

Regards

Runar

RE: enable modem trace logs.

Pradeep Gamidi — Mon, 10 Jun 2024 11:12:18 GMT

Hi,

As mentioned above i have used CONFIG_NRF_MODEM_LIB_TRACE_ENABLED and CONFIG_NRF_MODEM_LIB_TRACE_MEDIUM_RTT, but i was facing below error

Error

c:/h565935/cl5g_r200/toolchain/opt/bin/../lib/gcc/arm-none-eabi/9.2.1/../../../../arm-none-eabi/bin/ld.exe: modules/nrf/lib/nrf_modem_lib/lib..__nrf__lib__nrf_modem_lib.a(nrf_modem_os.c.obj): in function `nrf_modem_os_trace_put':
C:/H565935/CL5G_R200/nrf/lib/nrf_modem_lib/nrf_modem_os.c:706: undefined reference to `SEGGER_RTT_ASM_WriteSkipNoLock'
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'C:\H565935\CL5G_R200\toolchain\opt\bin\cmake.EXE' --build 'C:\H565935\CL5G_R200\cp_r200_app\build'

It appears that the linker is unable to locate the SEGGER_RTT_ASM_WriteSkipNoLock function, can you help to solve this issue.

Thanks and Regards,
Pradeep Gamidi.

RE: enable modem trace logs.

runsiv — Mon, 10 Jun 2024 09:10:13 GMT

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

RE: enable modem trace logs.

Pradeep Gamidi — Mon, 10 Jun 2024 05:26:04 GMT

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.

RE: enable modem trace logs.

runsiv — Fri, 07 Jun 2024 07:06:52 GMT

Hi Gamidi

Please see Lesson 7 Debugging with a modem trace on our Cellular IoT Fundamentals course

Regards

Runar