Build Fail when trying to modify SLM application sample

RE: Build Fail when trying to modify SLM application sample

dejans — Wed, 05 Mar 2025 11:34:39 GMT

Hi,

It is recommended to use 1M baudrate. Otherwise, traces could be lost.

Best regards,
Dejan

RE: Build Fail when trying to modify SLM application sample

Alan-Ni — Mon, 03 Mar 2025 07:20:59 GMT

Hi Dejans,

Good news and bad news.

I've tried your method of only configuring the TX/RX pin assignment, and it works!

However if I tried to set the UART1 baudrate to 230400, it still can output something, but definitely not complete.

From the logged file of my uart logger, I still can see the AT commands appears inside it, but as I import the bin file to cellular monitor program, the program and wireshark program both couldn't resolve packets inside it.

Do you have any Idea to make it work at different baudrates? Or I might just need to give up and find some other uart logger module that support 1M baudrate in this point...

binary1, outputted with 230400 baudrate
devzone.nordicsemi.com/.../output.bin

binary2, outputted with 1M baudrate.
devzone.nordicsemi.com/.../output2.bin

RE: Build Fail when trying to modify SLM application sample

dejans — Fri, 28 Feb 2025 09:50:52 GMT

Hi,

Your (or similar) solution should work fine. This part is only used for modem trace collection but it does affect all applications that use it.

Best regards,
Dejan

RE: Build Fail when trying to modify SLM application sample

Alan-Ni — Thu, 27 Feb 2025 14:41:01 GMT

Hi Dejans,

Wow this really is a great news!!
I'll try this as soon as I get back to work(Didn't have the board with me now).

However I have some little concern for now.

Since these was implemented in the library, I assume they would be used by all the applications I might be building(if is version 2.4.0). So it might be risky to directly change the library itself?
(Change is needed cause the highest matched baudrate of nrf and our UART logger was 230400)

I've roughly viewed the uart.c file, and came up with an idea.
If I wrapped the line 60~ line 68 inside an #ifdef #else #endif like below, and then add the "CONFIG_NRF_MODEM_TRACE_LOG_BAUDRATE" self-defined keyword in the extra Kconfig fragments, would this be a safer may to add the change?
Or is this a totally misunderstand of how config keywords works?

#ifdef CONFIG_NRF_MODEM_TRACE_LOG_BAUDRATE
const nrfx_uarte_config_t config = {
		.skip_gpio_cfg = true,
		.skip_psel_cfg = true,
		.hal_cfg.hwfc = NRF_UARTE_HWFC_DISABLED,
		.hal_cfg.parity = NRF_UARTE_PARITY_EXCLUDED,
		.baudrate = NRF_UARTE_BAUDRATE_230400,
		.interrupt_priority = DT_IRQ(UART1_NL, priority),
		.p_context = NULL,
	};
#else
const nrfx_uarte_config_t config = {
		.skip_gpio_cfg = true,
		.skip_psel_cfg = true,
		.hal_cfg.hwfc = NRF_UARTE_HWFC_DISABLED,
		.hal_cfg.parity = NRF_UARTE_PARITY_EXCLUDED,
		.baudrate = NRF_UARTE_BAUDRATE_1000000,
		.interrupt_priority = DT_IRQ(UART1_NL, priority),
		.p_context = NULL,
	};
#endif

RE: Build Fail when trying to modify SLM application sample

dejans — Thu, 27 Feb 2025 14:01:18 GMT

Hi,

I have discussed this issue with our developers.

In NCS 2.4.0, the modem trace is not configurable by device tree. Instead, it uses UARTE1 (uart1) by default:
github.com/.../Kconfig

Most of the parameters are hardcoded, and if these need to be changed, changes are needed in here:
github.com/.../uart.c

But it does follow the pintctrl of: uart1_default: uart1_default
github.com/.../uart.c

For getting this to work, you do not need to enable uart1 (as this will lead to IRQ issue as uart1 will likely have a conflict with itself), or uart3. You only need to set the following:

uart1_default: uart1_default {
                group1 {
                        psels = <NRF_PSEL(UART_RX, 0, 3)>;
                        bias-pull-up;
                };
                group2 {
                        psels = <NRF_PSEL(UART_TX, 0, 4)>;
                };
        };

Best regards,
Dejan

RE: Build Fail when trying to modify SLM application sample

Alan-Ni — Wed, 26 Feb 2025 08:59:50 GMT

Hi Dejans,

Just tried exchanging to that config, but sadly nothing changed. I'm still only receiving modem trace LOG from the virtual port.

I also tried to use the default 1Mbps baudrate recommended to output LOG, but still nothing changed...

RE: Build Fail when trying to modify SLM application sample

Alan-Ni — Wed, 26 Feb 2025 08:59:49 GMT

Hi Dejans,

Just tried exchanging to that config, but sadly nothing changed. I'm still only receiving modem trace LOG from the virtual port.

I also tried to use the default 1Mbps baudrate recommended to output LOG, but still nothing changed...

RE: Build Fail when trying to modify SLM application sample

dejans — Tue, 25 Feb 2025 10:22:44 GMT

Hi,

I you have not seen it already, please refer to my previous reply for additional information regarding modem tracing on a specific UART.

Do you see any change if you replace

CONFIG_UART_2_NRF_HW_ASYNC_TIMER=2
CONFIG_UART_2_NRF_HW_ASYNC=y

with

CONFIG_UART_3_NRF_HW_ASYNC_TIMER=2
#CONFIG_UART_3_NRF_HW_ASYNC=y

in your configuration file?

Best regards,
Dejan

RE: Build Fail when trying to modify SLM application sample

dejans — Tue, 25 Feb 2025 09:53:58 GMT

Hi,

Modem tracing can be enabled and configured using nrf91-modem-trace-uart snippet as shown in modem trace lesson. Using this snippet enables UART1. You can also look at enabling tracing in the application where it is mentioned that UART1 is used for capturing modem trace. It is possible to use another UART peripheral for modem trace output but then some changes in modem library and configuration are needed (see Note in the linked page). When connecting with external MCU, the modem in nrf91 can directly be controlled by the application on external MCU. On the last linked page, you can find an example of configuring connection to external MCU using UART_2.

Best regards,
Dejan

RE: Build Fail when trying to modify SLM application sample

Alan-Ni — Tue, 25 Feb 2025 08:42:19 GMT

Hi Dejans,

Information update!

According to the suggestion from Nordic AI to check the zephyr.dts, I kind of figure out that UART1 was likely to also be assigned to use by "arduino_serial". Guess that might be the reason IRQ error pops when I try to configure UART1.
(Screenshot was taken "after" I changed the port, so uart1 is now disabled)

However as I tried to configure the modem trace output port to UART3, it could successfully build(new extra configure file attached below). But I ends up still receiving trace from one of the virtual port of the DK board instead of the expected PO.03/PO.04.
devzone.nordicsemi.com/.../custom_5F00_9160_5F00_A1_5F00_1.conf

devzone.nordicsemi.com/.../custom_5F00_9160_5F00_A1_5F00_1.overlay

devzone.nordicsemi.com/.../uart_5F00_trace.conf

RE: Build Fail when trying to modify SLM application sample

Alan-Ni — Tue, 25 Feb 2025 02:32:59 GMT

Hi Dejans,

Sorry we do not have the modem trace yet. The environment there doesn't have space for an J-Link and a laptop there. That's the reason I wanna build a slm application that could output trace through another UART while communicating with out external MCU.

What we have now is the LOG of UART communication between external MCU and nRF-9160. It was separated into files because we logged them through 2 TF card UART logger.

Also for some unknown reason, the LOG should be way more larger than this since its overnight logging, but this is what we got for now.

9160 sending to M452(our Nuvoton external MCU):

devzone.nordicsemi.com/.../9160_5F00_to_5F00_M452_5F00_FILE0000.TXT devzone.nordicsemi.com/.../9160_5F00_to_5F00_M452_5F00_FILE0001.TXT

M452 sending to 9160

devzone.nordicsemi.com/.../M452_5F00_to_5F00_9160_5F00_FILE0003.TXT

Also I am continuing trying to build the slm application, but I noticed that in the description under SLM sample's documnet folder, there's a file named slm_description.rst mentioned:
"""

To save power, both the console and the output logs over ``UART_0`` are disabled in this application.

"""
So it seems like the default uart port used to output trace is actually UART 0 instead of UART1?
I've asked Nordic AI again and this time it also reply the default port is UART 0.

If this is the case then here comes a new problem that in order to communicate with external MCU, the document says we have to enable UART 2 and disable UART0, but the default UART port used to output trace was UART 0.
Is this solvable with configuration? Or this could only be solve by going into the codes to modify them?

RE: Build Fail when trying to modify SLM application sample

dejans — Mon, 24 Feb 2025 11:16:36 GMT

Hi,

Can you provide complete application log and modem trace?

Best regards,
Dejan

RE: Build Fail when trying to modify SLM application sample

Alan-Ni — Sat, 22 Feb 2025 00:06:45 GMT

Hi Dejans,

Yes I am trying to build a firmeare for my custom board. I'm aware that the pins might already assinged for other use on the DK board, but somehow our hardware engineer decide to place them there...

We've been using that board as modem for a while, so far it works fine.

But recently at our new site, we are having a phenomenon thay even if the signal was good (power level is 8 from the response of AT%CONEVAL), the board would periodically response ERROR while we send XSEND command(TCP packet, with data mode).

The data throughput of device there were about 100 bytes per packet, one packet per 10 second. And the Error would pop up roughly every 24 sends(sometimes less).

Since error doesn't shows evertime we send XSEND, I assume the syntax was correct, so I am trying to make the 9160 output its LOG for more information about what's happening inside.

RE: Build Fail when trying to modify SLM application sample

dejans — Fri, 21 Feb 2025 18:10:04 GMT

Hi,

Are you trying to modify and build the sample for nrf9160dk_nrf9160_ns board target or for your custom board?

I have reproduced your issue by building SLM sample for nrf9160dk_nrf9160_ns board target in NCS v2.4.0 with your config/overlay files. I will look further into it. I expect to get back to you by the end of next week.

Best regards,
Dejan