Modem trace for modem fw 1.2.3 with cellular monitor

[y009]

Hey.

I'm trying to get the modem trace log in a readable format. 

I've redirected my uart0 to rtt and put uart1 on previosuly uart0 pins to capture the output. 
The cellular monitor doesn't pick up any information form the trace output - no data displayed, but mtrace file is logged.
I can see some human readable data in there, so something is working at least.

The cellular monitor says modem fw 1.3.1+ req, but is there any way to get it parse for fw 1.2.3 (the database at least list all versions so idk?)

Or if there is an easier way to get the AT command sequence extracted that would be helpful as well.

[Øyvind]

Hello, 

During the summer season, our workforce is currently operating with reduced staff levels throughout the company, which may lead to slight delays in our response time as we await additional resources. Rest assured, we are actively addressing all issues and working diligently to resolve them promptly.

---

The cellular monitor doesn't pick up any information form the trace output - no data displayed, but mtrace file is logged.

Could you please elaborate more on this? What happens in the Cellular Monitor when you start a trace with you device running an application that has modem trace enabled?

Are you able to provide the mtrace file?

Kind regards,
Øyvind

[y009]

Sorry for the reply also on my half, I didnt get a notification for a reponse.

All of the data on the cellular monitor show as unknown.
This is with loading trace from file.

trace-2023-07-23T10-51-28.103Z.mtrace
I have included the same file that I tried to load back in to cellular modem.
The file was saved with the same app.

Regards,
Henry

[y009]

Fullscreen 2766.test.log Download

# SEGGER J-Link RTT Viewer V7.66a Terminal Log File
# Compiled: 15:16:36 on May 19 2022
# Logging started @ 04 Sep 2023 15:47:48

# Logging stopped @ 04 Sep 2023 16:12:35

i did check with hex editor, it is empty 

[Øyvind]

This means that the modem trace has not been configured correctly, i.e. CONFIG_NRF_MODEM_LIB_TRACE=y and CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_RTT =y

Please see the Modem trace module documentation.

[y009]

Sorry for long reply again (this is not a poject that is in active dev)

I realized I haven't mentiod ncs version, but it's ncs1.8.0
and checked that the version specific configs:

CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y

CONFIG_NRF_MODEM_LIB_TRACE_MEDIUM_RTT=y
are indeed set.

[Øyvind]

Just to verify, please follow these steps

1. Go into prj.conf and add these two lines (which you have done):
CONFIG_NRF_MODEM_LIB_TRACE_ENABLED=y
CONFIG_NRF_MODEM_LIB_TRACE_MEDIUM_RTT=y

 

You might also need to disable other RTT logging channels:
CONFIG_LOG_BACKEND_RTT=n
CONFIG_RTT_CONSOLE=n

 

2. Compile and flash the project.

 

3. Open JLinkRTTViewer, select device "nRF9160_xxaa"

 

4. When successfully connected, go to "Logging" -> "Start Data Logging", and select a path to save the file.

 

5. See that the .log file grows in size. When finished tracing, stop data logging and rename the .log file to .bin

6. Open the recorded .bin file in Cellular Monitor.

[y009]

I feel kinda dumb now. Rtt backend might have been active. 

I got the log file with some values a least.
Can the AT commands be parsed out of the trace aswell? or is there another way i could do that?

[Øyvind]

y009 said:

I feel kinda dumb now. Rtt backend might have been active.

No need to feel dumb, this can be tricky some times

When you open a log file in Cellular Monitor it should include AT commands as well. These are visible in the time line. 

What happens when you open the file on your side? 

-Øyvind

[y009]

Ah the green dots, yes, i didnt realize, they showed the at cmds in them also. 
Got it exported with wireshark also.

Thank you