<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Communication Between NRF9160 and Nucleo Board Using SLM Example</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/111037/communication-between-nrf9160-and-nucleo-board-using-slm-example</link><description>Hello everyone, 
 I&amp;#39;ve successfully implemented the SLM example on the NRF9160, and it&amp;#39;s functioning properly. Now, I&amp;#39;m attempting to send AT commands to the modem using my Nucleo board. I&amp;#39;ve disabled hardware flow control in the Nucleo configuration</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 21 May 2024 20:25:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/111037/communication-between-nrf9160-and-nucleo-board-using-slm-example" /><item><title>RE: Communication Between NRF9160 and Nucleo Board Using SLM Example</title><link>https://devzone.nordicsemi.com/thread/485224?ContentTypeID=1</link><pubDate>Tue, 21 May 2024 20:25:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:03940c4a-0ff4-426f-8682-e551913d1278</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Do you have a logic analyzer&amp;nbsp;to use in your debugging? It could help debug the communication lines. That said, our Serial LTE Modem team tested on their side and inform me that you might need to disable &lt;code&gt;CONFIG_SPI_NOR&lt;/code&gt;.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Further points to follow up with:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Are the voltages set correctly? NRF9160DK voltage can be changed with &lt;strong&gt;VDD IO switch (SW9)&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Do&amp;nbsp;you see an incoming AT-command with SLM RTT traces? To check whether AT-command is received, CONFIG_SLM_LOG_LEVEL_DBG=y should be set. Then RTT-traces will show if the command is received in SLM and if the response is sent.
&lt;ul&gt;
&lt;li&gt;If no, concentrate on TX:
&lt;ul&gt;
&lt;li&gt;Is the wiring correct between Nucleo TX and 9160 RX?&lt;/li&gt;
&lt;li&gt;Can they send the AT-message to 9160 when they are not in the interrupt handler?&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;If yes, concentrate on RX:
&lt;ul&gt;
&lt;li&gt;Are they receiving something to UART1_IRQHandler when \r\n\OK\r\n should come?&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Other noted things:&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;NRF SDK version is 3.5.99-ncs1, which seems odd as we are currently in 2.6.99. Might be Zephyr version.&lt;/li&gt;
&lt;li&gt;CONFIG_SLM_CR_TERMINATION=y is used but CR_LF sending is still used.&lt;/li&gt;
&lt;li&gt;UART2 is chosen twice.&lt;/li&gt;
&lt;li&gt;The OK response is actually &lt;code&gt;\r\nOK\r\n&lt;/code&gt;. Depending on how the &lt;code&gt;UART_ReceiveString&lt;/code&gt; is implemented, this could explain things.&amp;nbsp;&lt;/li&gt;
&lt;li&gt;It is also worth noting, that &lt;code&gt;LL_USART_ReceiveData8&lt;/code&gt; is used inside IRQ handler to get data one byte at a time and &lt;code&gt;UART_ReceiveString&lt;/code&gt; is called inside it. Does the interrupt handler process data instead of the intended method? The OK response does not differ from the Ready as both come through UART.
&lt;ul&gt;
&lt;li&gt;If we are on the interrupt handler for UART, it is also possible that sending through&amp;nbsp;UART is not allowed at that point.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;What application are you running on the Nucleo side? Have you tested with our SLM Shell sample? Our developers point out that they got the&amp;nbsp;&lt;span&gt;&lt;span dir="ltr"&gt;sample to work with exact settings they are using &amp;nbsp;and the disablement of the &lt;code&gt;CONFIG_SPI_NOR&lt;/code&gt;.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Communication Between NRF9160 and Nucleo Board Using SLM Example</title><link>https://devzone.nordicsemi.com/thread/483029?ContentTypeID=1</link><pubDate>Mon, 13 May 2024 12:06:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f59e34fa-be4a-4410-ac15-a97a163c3e06</guid><dc:creator>Milad_</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/members/oys"&gt;Øyvind&lt;/a&gt;&amp;nbsp;it&amp;#39;s done before in&amp;nbsp;nrf9160dk_nrf9160_ns.conf as below:&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;#
# Copyright (c) 2021 Nordic Semiconductor ASA
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

# Configuration file for nRF9160DK.
# This file is merged with prj.conf in the application folder, and options
# set here will take precedence if they are present in both files.

# Use UART_0 (when working with PC terminal)
# unmask the following config
# CONFIG_UART_0_NRF_HW_ASYNC_TIMER=2
# CONFIG_UART_0_NRF_HW_ASYNC=y
# CONFIG_SLM_POWER_PIN=6
# CONFIG_SLM_INDICATE_PIN=2

# Use UART_2 (when working with external MCU)
# unmask the following config
CONFIG_UART_2_NRF_HW_ASYNC_TIMER=2
CONFIG_UART_2_NRF_HW_ASYNC=y
CONFIG_SLM_POWER_PIN=31
CONFIG_SLM_INDICATE_PIN=30
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;But still I can&amp;#39;t communicate with modem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Communication Between NRF9160 and Nucleo Board Using SLM Example</title><link>https://devzone.nordicsemi.com/thread/483017?ContentTypeID=1</link><pubDate>Mon, 13 May 2024 11:51:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aabd8b64-d1e3-40ea-b7b2-b241a288da80</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Looking at your setup, I can&amp;#39;t see that you have enabled the following KConfig options:&lt;br /&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;# Use UART_2 (when working with external MCU)
# unmask the following config
CONFIG_UART_2_NRF_HW_ASYNC_TIMER=2
CONFIG_UART_2_NRF_HW_ASYNC=y
CONFIG_SLM_POWER_PIN=31
CONFIG_SLM_INDICATE_PIN=30&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Please see the&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ncs-2.6.1/page/nrf/applications/serial_lte_modem/doc/slm_description.html#connecting_with_an_external_mcu"&gt;Connecting with an external MCU documentation&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>