Migrating MQTT Sample to a Custom Board

RE: Migrating MQTT Sample to a Custom Board

RodWatt — Tue, 26 Nov 2024 13:53:11 GMT

Hi Dejan,

I have tried building with and without TLS

I have tried this

west build --pristine -b nrf9160dk_nrf9160_ns -- -DEXTRA_CONF_FILE=overlay-tls-nrf91.conf -DDTC_OVERLAY_FILE=./boards/my_board.overlay

and this

west build --pristine -b nrf9160dk_nrf9160_ns -- -DDTC_OVERLAY_FILE=./boards/my_board.overlay

I am using vs2.8.0 and have tried both version 1.3.6 and 1.3.7 firmware.

I have gone back to 1.3.6 and rebuilt. and it appears to be working! Here is my trace file.

devzone.nordicsemi.com/.../Test_2D00_26_5F00_11_5F00_24.pcapng

Rod

RE: Migrating MQTT Sample to a Custom Board

dejans — Mon, 25 Nov 2024 17:24:14 GMT

Hi Rod,

Is provided log from working board?

I have tested unmodified MQTT sample in NCS v2.8.0 on the nrf9160-dk without additional overlay files and I got the log shown below.

*** Booting nRF Connect SDK v2.8.0-a2386bfc8401 ***
*** Using Zephyr OS v3.7.99-0bc3393fb112 ***
[00:00:00.293,273] <inf> network: Bringing network interface up and connecting to the network
[00:00:00.529,693] <inf> nrf_modem_lib_trace: Trace thread ready
[00:00:00.537,322] <inf> nrf_modem_lib_trace: Trace level override: 2
+CEREG: 2,"816C","03138801",7
+CSCON: 1
+CGEV: ME PDN ACT 0
%MDMEV: SEARCH STATUS 2
+CEREG: 1,"816C","03138801",7,,,"00001010","11000001"
[00:00:02.594,238] <inf> network: Network connectivity established
+CGEV: IPV6 0
[00:00:08.326,416] <inf> transport: Connected to MQTT broker
[00:00:08.326,477] <inf> transport: Hostname: test.mosquitto.org
[00:00:08.326,507] <inf> transport: Client ID: 351358811129656
[00:00:08.326,538] <inf> transport: Port: 1883
[00:00:08.326,568] <inf> transport: TLS: No
[00:00:08.326,599] <inf> transport: Subscribing to: 351358811129656/my/subscribe/topic
[00:00:08.593,536] <inf> transport: Subscribed to topic 351358811129656/my/subscribe/topic
+CSCON: 0
[00:01:00.303,436] <inf> transport: Published message: "Hello MQTT! Current uptime is: 60294" on topic: "351358811129656/my/publish/topic"
%MDMEV: SEARCH STATUS 2
+CSCON: 1
+CSCON: 0
[00:02:00.303,680] <inf> transport: Published message: "Hello MQTT! Current uptime is: 120294" on topic: "351358811129656/my/publish/topic"
%MDMEV: SEARCH STATUS 2
+CSCON: 1
+CSCON: 0

There is a difference in our logs regarding TLS. Your log shows "<inf> transport: TLS: Yes". Which NCS version did you use for the latest testing and how did you build the sample?

[quote user="RodWatt"]I have flashed both boards with the latest modem firmware.[/quote]

You mentioned previously that you used modem firmware v1.3.6. However, the most recent version is v1.3.7. Are your boards flashed with modem firmware v1.3.6 or v1.3.7?

Best regards,
Dejan

RE: Migrating MQTT Sample to a Custom Board

RodWatt — Fri, 22 Nov 2024 14:10:52 GMT

Hi Dejan,

I am running the "standard mqtt sample", (nrf/samples/net/mqtt) unmodified; so have not touched the code. It runs fine on the nRF9160DK board.

I tried another one of my boards and it seems to work, although I cant see any traces on the UART on the second board. This is what I see on the serial terminal.

[00:00:00.721,435] <inf> nrf_modem_lib_trace: Trace thread ready
[00:00:00.722,595] <inf> nrf_modem_lib_trace: Trace level override: 2
[00:00:00.724,426] <err> lte_lc: Could not send AT command, error: 65536
[00:00:00.724,456] <err> lte_lc: Failed to set system mode and mode preference, err -14
[00:00:02.118,682] <wrn> nrf_modem_lib_netif: lte_lc_modem_events_enable, error: -14
+CEREG: 2,"01B0","0928D982",7,0,0,"11100000","11100000"
[00:00:16.853,210] <wrn> lte_lc: Registration rejected, EMM cause: 0, Cell ID: 153672066, Tracking area: 432, LTE mode: 7
+CSCON: 1
+CGEV: ME PDN ACT 0,0
+CNEC_ESM: 50,0
+CEREG: 1,"01B0","0928D982",7,,,"11100000","11100000"
[00:00:19.289,672] <inf> network: Network connectivity established
+CSCON: 0
+CSCON: 1
+CSCON: 0
+CSCON: 1
[00:00:45.602,630] <inf> transport: Connected to MQTT broker
[00:00:45.602,691] <inf> transport: Hostname: test.mosquitto.org
[00:00:45.602,722] <inf> transport: Client ID: 352656100493439
[00:00:45.602,722] <inf> transport: Port: 8883
[00:00:45.602,752] <inf> transport: TLS: Yes
[00:00:45.602,813] <inf> transport: Subscribing to: 352656100493439/my/subscribe/topic
[00:00:46.262,634] <inf> transport: Subscribed to topic 352656100493439/my/subscribe/topic
[00:00:46.606,658] <inf> transport: Published message: "Hello MQTT! Current uptime is: 46605" on topic: "352656100493439/my/publish/topic"
[00:00:46.627,716] <inf> transport: Published message: "Hello MQTT! Current uptime is: 46626" on topic: "352656100493439/my/publish/topic"
[00:00:46.640,441] <inf> transport: Published message: "Hello MQTT! Current uptime is: 46639" on topic: "352656100493439/my/publish/topic"
[00:00:46.653,015] <inf> transport: Published message: "Hello MQTT! Current uptime is: 46651" on topic: "352656100493439/my/publish/topic"
[00:00:46.664,398] <inf> transport: Published message: "Hello MQTT! Current uptime is: 46663" on topic: "352656100493439/my/publish/topic"

So, summarise.

When i run the code on one of my boards, i get a trace on UART0 but the board does not connect to the network.

When i run the same code on another board, (exact same hardware, same code, same SIM card etc). It does connect but I do not see a trace.

I have flashed both boards with the latest modem firmware.

Apart from the possibility of a hardware fault, is there anything else i am missing?

Thanks,

Rod

RE: Migrating MQTT Sample to a Custom Board

dejans — Wed, 13 Nov 2024 12:27:41 GMT

Hi Rod,

AT%XSYSTEMMODE command is allowed only before activating the modem using AT+CFUN=1. Before changing the system mode, you could try to put the modem in a required state using AT+CFUN=0 (or AT+CFUN=4).

Best regards,
Dejan

RE: Migrating MQTT Sample to a Custom Board

dejans — Fri, 08 Nov 2024 18:41:32 GMT

Hi Rod,

I will look into this during next week.
I expect to get back to you by the end of next week.

Best regards,
Dejan

RE: Migrating MQTT Sample to a Custom Board

RodWatt — Thu, 07 Nov 2024 15:14:47 GMT

Hi Dejan,

I am running the latest, 1.3.6.

devzone.nordicsemi.com/.../Test_2D00_nov7.pcapng

Rod

RE: Migrating MQTT Sample to a Custom Board

dejans — Thu, 07 Nov 2024 15:00:18 GMT

Hi Rod,

What is your current modem firmware version?

When I compare your trace file with the trace file for nrf9160-dk, there seem to be no connection procedure or attachment attempt in your log. Can you take a longer modem trace which would potentially show that?

Best regards,
Dejan

RE: Migrating MQTT Sample to a Custom Board

RodWatt — Thu, 07 Nov 2024 11:08:05 GMT

Hi Dejan,

Yes, still getting the same error.

*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using ZK OS v3.6.99-100befc70c74 ***
[00:00:00.404,541] <ifrݽɭ: Bringing network interface up and connecting to the Sݽɭm[0m
[00:00:00.405,151] <dbg> mqtt_helper: mqtt_stae5: State transition: MQTT_STATE_UNINIT --> MQTT_STATE_DISCONECTED
[00:00:00.435,607] <dbg> mqtt_helper: mqtt_helper_poll_loop:aiting for connection_poll_sem
[00:00:00.633,056] <i> nrf_modem_lib_trace: Trace thread ready
[00:00:00.640,3NW<inf> nrf_modem_lib_trace: Trace level override: 2
A҂҂r41,937] <err> lte_lc: Could not send AT command, error: 65536
[00:00:00.641,967] <err> lte_lc: Failed to set system mode and mode preference, err -14

Regards, Rod

RE: Migrating MQTT Sample to a Custom Board

dejans — Tue, 05 Nov 2024 08:02:11 GMT

Hi Rod,

Do you still get the same error in the application log (shown below)?

<err> lte_lc: Could not send AT command, error: 65536
<err> lte_lc: Failed to set system mode and mode preference, err -14

If there is any difference, please provide new application log.

Best regards,
Dejan

RE: Migrating MQTT Sample to a Custom Board

RodWatt — Mon, 04 Nov 2024 14:58:06 GMT

Hi Dejan,

I started again with a clean build, refreshed modem firmware etc. I also enabled the RTS/CTS signals on the trace port and am now seeing some traces.

devzone.nordicsemi.com/.../6811.test.pcapng

Regards,

Rod

RE: Migrating MQTT Sample to a Custom Board

dejans — Fri, 25 Oct 2024 09:13:13 GMT

Hi Rod,

Here are some discussions related to the same/similar problem:
- LTE LC cannot send AT commands
- error switching LTE to LTE GPS
- lte_lc_func_mode_set() fails
- fatal error using NB-IoT with GNSS

Regarding modem trace, you can find more information in Debugging with modem trace. Sending traces over RTT needs to be enabled using CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_RTT.

I hope that at least some of above-mentioned links can be helpful to you.

Best regards,
Dejan

RE: Migrating MQTT Sample to a Custom Board

RodWatt — Thu, 24 Oct 2024 09:06:51 GMT

Hi Dejan,

I tried RTT previously and could get that to work either, Do I need to use the RTS/CTS signals for flow control?

We started down this route to address the initial error of

lte_lc: Could not send AT command, error: 65536

Failed to set system mode and mode preference, err -14

Do you have any suggestions on how i can address these, without having the trace files?

Rod

RE: Migrating MQTT Sample to a Custom Board

dejans — Thu, 24 Oct 2024 08:47:57 GMT

Hi Rod,

Your trace file seems to be empty. As I mentioned previously, you could try to use RTT instead of UART and do tracing with RTT.

Best regards,
Dejan

RE: Migrating MQTT Sample to a Custom Board

RodWatt — Wed, 23 Oct 2024 15:01:34 GMT

Hi Dejan,

To answer your questions.

Can you send your latest trace file so that I can also try to open it?

>> Attatched below.

devzone.nordicsemi.com/.../trace_2D00_2024_2D00_10_2D00_23T14_2D00_53_2D00_28.874Z.mtrace

What happens when you switch to some older NCS version? Is tracing successful?

>> I get the same error/lack of packets

You could try choosing "Autoselect" for modem trace database.

>> The window pops up and sits for ages

Can you double check that you tried to open correct mtrace file?

>>> Yes, I am using the correct file.

Have you tried to use snippets to enable traces as it was suggested by Charlie previously?

>>> Yes, I tried that too.

Rod

RE: Migrating MQTT Sample to a Custom Board

dejans — Tue, 22 Oct 2024 09:49:03 GMT

Hi Rod,

Can you send your latest trace file so that I can also try to open it?

What happens when you switch to some older NCS version? Is tracing successful?

You could try choosing "Autoselect" for modem trace database.

Can you double check that you tried to open correct mtrace file?

Have you tried to use snippets to enable traces as it was suggested by Charlie previously?

Best regards,
Dejan

RE: Migrating MQTT Sample to a Custom Board

RodWatt — Mon, 21 Oct 2024 15:56:03 GMT

Hi Dejan,

In the process of moving to UART0, I noticed an error in my overlay file which I have now corrected. (I labeled the pins a xx_default_alt and listed the names as xxx_default, without the _alt)

I am now able to generate a .mtrace file.

However, it doesn't open in waveshark which reports no packets

my prj.conf file is as follows

# General
CONFIG_HW_ID_LIBRARY=y
CONFIG_ASSERT=y

# Logging
CONFIG_LOG=y
CONFIG_MQTT_HELPER_LOG_LEVEL_DBG=y

# Networking
CONFIG_NETWORKING=y
CONFIG_NET_SOCKETS_OFFLOAD=y
CONFIG_NET_SOCKETS=y
CONFIG_POSIX_API=y
CONFIG_NET_IPV4=y
CONFIG_NET_TCP=y
CONFIG_NET_NATIVE=y
CONFIG_NET_CONNECTION_MANAGER=y

# ZBus
CONFIG_ZBUS=y

# Zephyr state framework
CONFIG_SMF=y

# MQTT
CONFIG_MQTT_HELPER=y
CONFIG_MQTT_CLEAN_SESSION=y

CONFIG_MQTT_SAMPLE_TRANSPORT_BROKER_HOSTNAME="test.mosquitto.org"
#CONFIG_MQTT_SAMPLE_TRANSPORT_BROKER_HOSTNAME="192.168.1.124"

CONFIG_MQTT_SAMPLE_TRANSPORT_CLIENT_ID="SeaHorse_Test_Data"
CONFIG_MQTT_SAMPLE_TRANSPORT_PUBLISH_TOPIC="publish/topic"
CONFIG_MQTT_SAMPLE_TRANSPORT_SUBSCRIBE_TOPIC="subscribe/topic"

#Modem Trace
#CONFIG_NRF_MODEM_LIB_TRACE=y
#CONFIG_AT_HOST_LIBRARY=y

CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_UART_ZEPHYR=y

CONFIG_UART_ASYNC_API=y
CONFIG_SERIAL=y

#UART Trace
CONFIG_USE_SEGGER_RTT=n
CONFIG_RTT_CONSOLE=n
CONFIG_UART_CONSOLE=y
CONFIG_LOG_BACKEND_RTT=n
CONFIG_LOG_BACKEND_UART=y

# UART configuration
CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y
CONFIG_UART_1_ASYNC=y
CONFIG_UART_1_INTERRUPT_DRIVEN=n

# Power management
CONFIG_PM_DEVICE=y

# TFM logging over uart1
CONFIG_TFM_LOG_LEVEL_SILENCE=n
CONFIG_TFM_SECURE_UART1=y
CONFIG_TFM_SECURE_UART_SHARE_INSTANCE=y
CONFIG_TFM_EXCEPTION_INFO_DUMP=y
CONFIG_TFM_SPM_LOG_LEVEL_DEBUG=y

# General
CONFIG_HW_STACK_PROTECTION=y
CONFIG_HW_ID_LIBRARY_SOURCE_IMEI=y
CONFIG_PICOLIBC=y
CONFIG_DK_LIBRARY=y
CONFIG_AT_HOST_LIBRARY=y

# Modem trace
CONFIG_NRF_MODEM_LIB_TRACE=y
CONFIG_NRF_MODEM_LIB_TRACE_BACKEND_UART=y
CONFIG_SERIAL=y
CONFIG_UART_ASYNC_API=y

CONFIG_UART_0_ASYNC=y
CONFIG_UART_0_INTERRUPT_DRIVEN=n

# Disable Duplicate Address Detection (DAD)
# due to not being properly implemented for offloaded interfaces.
CONFIG_NET_IPV6_NBR_CACHE=n
CONFIG_NET_IPV6_MLD=n

# Zephyr NET Connection Manager and Connectivity layer.
CONFIG_NET_CONNECTION_MANAGER_MONITOR_STACK_SIZE=1024
CONFIG_NRF_MODEM_LIB_NET_IF=y

Regards,

Rod

RE: Migrating MQTT Sample to a Custom Board

dejans — Fri, 18 Oct 2024 13:25:55 GMT

Hi Rod,

You could try to redirect your traces to UART0 and see if this has any effect. If you choose to do so, you need to replace instances of uart1 (as it is shown in the sending traces over UART section) with uart0. Then your terminal connection could go to uart1. If UART tracing is for some reason not possible or you have only one UART available on your custom board, you can try to do tracing with RTT.

Best regards,
Dejan

RE: Migrating MQTT Sample to a Custom Board

RodWatt — Thu, 17 Oct 2024 13:24:41 GMT

Hi Dejan,

I started by trying this process using the nRF9169DK board

I produced this trace file

devzone.nordicsemi.com/.../trace_2D00_2024_2D00_10_2D00_17T12_2D00_47_2D00_05.939Z.mtrace

which opened automatically in Waveshark.

I noticed that I was unable to subsequently open the same file in Waveshark but had to open the file that had been saved in Waveshark.

devzone.nordicsemi.com/.../nrf9160_5F00_WS.pcapng

Anyway, this seems to work OK.

I then tried this on my own board using the same process and this is where i see problems.

Although I seem to be generating a .mtrace file, Waveshark reports no data.

Im guessing I have something wrong with my UART set up?

This is my overlay file

/ {
   chosen {
      nordic,modem-trace-uart = &uart1;
   };
};

&uart0 {
	status = "okay";
	current-speed = < 115200 >;
	pinctrl-0 = <&uart0_default>;
   	pinctrl-1 = <&uart0_sleep>;
   	pinctrl-names = "default", "sleep";
	/delete-property/ rts-pin;
	/delete-property/ cts-pin;
};

/* Enable uart1 for tracing. */


&uart1 {
   	status = "okay";
   	current-speed = <1000000>;
   	pinctrl-0 = <&uart1_default_alt>;
   	pinctrl-1 = <&uart1_sleep_alt>;
   	pinctrl-names = "default", "sleep";
	/delete-property/ rts-pin;
	/delete-property/ cts-pin;
};


&pinctrl {
	uart0_default: uart0_default {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 6)>, <NRF_PSEL(UART_RX, 0, 7)>;
		};
	};

	uart0_sleep: uart0_sleep {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 6)>, <NRF_PSEL(UART_RX, 0, 7)>;
			low-power-enable;
		};
	};
};

&pinctrl {
	uart1_default_alt: uart1_default_alt {
		group1 {
			psels = <NRF_PSEL(UART_RX, 0, 14)>;
			bias-pull-up;
		};
		group2 {
			psels = <NRF_PSEL(UART_TX, 0, 13)>;
		};
	};

	uart1_sleep_alt: uart1_sleep_alt {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 14)>,
				<NRF_PSEL(UART_RX, 0, 13)>;
			low-power-enable;
		};
	};
};

Regards,

Rod

RE: Migrating MQTT Sample to a Custom Board

dejans — Mon, 14 Oct 2024 09:16:28 GMT

Hi Rod,

You might not have taken traces correctly or somehow trace file got corrupted. Can you try to do it again? Please have a look at instructions on how to capture modem trace in our Cellular IoT Fundamentals course. It should be possible to upload file in mtrace format.

Best regards,
Dejan

RE: Migrating MQTT Sample to a Custom Board

RodWatt — Fri, 11 Oct 2024 10:47:15 GMT

Hi Dejan,

Sorry for the delay in getting back to you, i have been on holiday.

I have tried to open the file in Wireshark and am unable too. To check, i had a look at other .mtrace files that others have uploaded and tried the trace file on this ticket.

RE: STUCK LTE Connection

I was unable to open that file.

When i look at the types of files that Wireshark open, i dont see .mtrace ?

Do i need to create a different type of trace? How do do that?

Rod

RE: Migrating MQTT Sample to a Custom Board

dejans — Fri, 27 Sep 2024 14:25:57 GMT

Hi Rod,

I am not able to open your provided trace file. Are you able to open trace file in Wireshark on your end?

Best regards,
Dejan

RE: Migrating MQTT Sample to a Custom Board

RodWatt — Wed, 18 Sep 2024 14:40:39 GMT

Hi Charlie,

Thanks for the pointers. I have updated my overlay file as below.

/ {
   chosen {
      nordic,modem-trace-uart = &uart1;
   };
};

&uart0 {
	status = "okay";
	current-speed = < 115200 >;
	pinctrl-0 = <&uart0_default>;
   	pinctrl-1 = <&uart0_sleep>;
   	pinctrl-names = "default", "sleep";
	/delete-property/ rts-pin;
	/delete-property/ cts-pin;
};

/* Enable uart1 for tracing. */


&uart1 {
   	status = "okay";
   	current-speed = <1000000>;
   	pinctrl-0 = <&uart1_default_alt>;
   	pinctrl-1 = <&uart1_sleep_alt>;
   	pinctrl-names = "default", "sleep";
	/delete-property/ rts-pin;
	/delete-property/ cts-pin;
};


&pinctrl {
	uart0_default: uart0_default {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 6)>, <NRF_PSEL(UART_RX, 0, 7)>;
		};
	};

	uart0_sleep: uart0_sleep {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 6)>, <NRF_PSEL(UART_RX, 0, 7)>;
			low-power-enable;
		};
	};
};

&pinctrl {
	uart1_default_alt: uart1_default_alt {
		group1 {
			psels = <NRF_PSEL(UART_RX, 0, 14)>;
			bias-pull-up;
		};
		group2 {
			psels = <NRF_PSEL(UART_TX, 0, 13)>;
		};
	};

	uart1_sleep_alt: uart1_sleep_alt {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 14)>,
				<NRF_PSEL(UART_RX, 0, 13)>;
			low-power-enable;
		};
	};
};

Which has enabled me to see output on my terminal,

and looks like trace is working.

This is my trace file.

devzone.nordicsemi.com/.../trace_2D00_2024_2D00_09_2D00_18T14_2D00_24_2D00_19.592Z.mtrace

Rod

RE: Migrating MQTT Sample to a Custom Board

Charlie — Tue, 17 Sep 2024 12:07:43 GMT

Hi Rod,

Let me explain the setup in the original sample to help you understand your custom board setting.

nrf/snippets/nrf91-modem-trace-uart/modem-trace-uart.overlay is used when modem trace is enabled in the official sample. It uses uart1 for modem trace.

The default SLM sample use uart0 for terminal communication and uart1 for TF-M log output, so you need to use nrf/snippets/tfm-enable-share-uart/overlay-tfm-enable-share-uart.conf to make TF-M use uart0 as well when modem trace through uart1 is enabled.

Snippets for an nRF91 Series device (nordicsemi.com)

https://docs.nordicsemi.com/bundle/ncs-2.7.0/page/nrf/libraries/modem/nrf_modem_lib/nrf_modem_lib_trace.html#sending_traces_over_uart_on_a_custom_board

The above overly you have shared is trying to switch uart1 and uart0 functions, you need to copy nrf/snippets/nrf91-modem-trace-uart/modem-trace-uart.overlay here and replace uart1 with uart0 for modem trace collection.

Best regards,

Charlie

RE: Migrating MQTT Sample to a Custom Board

RodWatt — Mon, 16 Sep 2024 20:37:36 GMT

Hi Charlie,

No, I didn't manage to get the trace to work.

I tried the serial LTE example,

/ {
	chosen {
		ncs,slm-uart = &uart1;
	};
};

&uart0 {
	status = "okay";
	hw-flow-control;
};

&uart1 {
	compatible = "nordic,nrf-uarte";
	current-speed = <115200>;
	status = "okay";

	pinctrl-0 = <&uart1_default_alt>;
	pinctrl-1 = <&uart1_sleep_alt>;
	pinctrl-names = "default", "sleep";
};



&i2c2 {
	status = "disabled";
};

&pinctrl {
	uart1_default_alt: uart1_default_alt {
		group1 {
			psels = <NRF_PSEL(UART_RX, 0, 7)>;
			bias-pull-up;
		};
		group2 {
			psels = <NRF_PSEL(UART_TX, 0, 6)>;
		};
	};

	uart1_sleep_alt: uart1_sleep_alt {
		group1 {
			psels = <NRF_PSEL(UART_TX, 0, 6)>,
				<NRF_PSEL(UART_RX, 0, 7)>;
			low-power-enable;
		};
	};
};

I am using my own overlay file, above to redirect the serial. terminal.

Im getting this as an output

All pins have been configured as non-secure
[Sec Thread] Secure image initializing!
TF-M Float ABI: Hard
Lazy stacking enabled
Booting TF-M v2.0.0-ncs2
Ready

Rod

RE: Migrating MQTT Sample to a Custom Board

Charlie — Mon, 16 Sep 2024 11:06:21 GMT

Hi Rod,

Did you manage to collect a modem trace through either uart1 or RTT terminal?

I see you also play with link monitor before. If this is a new custom board, are you able to see it can successfully connect with network when you check with link monitor after programming Serial LTE modem (nordicsemi.com)?

Best regards,

Charlie