<?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>nRF9160 AT interface UART hardware related</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/46054/nrf9160-at-interface-uart-hardware-related</link><description>Hi, 
 I&amp;#39;m trying to make provision for AT command interface in my new nRF9160-SiP based design. 
 Couple of questions related to that: 
 1) Which UART (nRF9160-SiP pins) should I be using for this purpose? Also - are handshake (RTS, CTS, etc) lines absolutely</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 11 Apr 2019 13:08:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/46054/nrf9160-at-interface-uart-hardware-related" /><item><title>RE: nRF9160 AT interface UART hardware related</title><link>https://devzone.nordicsemi.com/thread/181620?ContentTypeID=1</link><pubDate>Thu, 11 Apr 2019 13:08:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f72ccb0f-ae60-46d4-bbc6-2aea5f1a685f</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Ash,&lt;/p&gt;
&lt;p&gt;1) The &lt;a href="https://github.com/NordicPlayground/fw-nrfconnect-nrf/blob/master/lib/at_host/at_host.c" rel="noopener noreferrer" target="_blank"&gt;AT Host library&amp;nbsp;&lt;/a&gt;lets you choose which UART to use. &lt;br /&gt;As default it is UART0 and the pins&amp;nbsp;can be&amp;nbsp;&lt;a href="https://www.nordicsemi.com/DocLib/Content/Product_Spec/nRF9160/latest/pin?926#pin_assign" rel="noopener noreferrer" target="_blank"&gt;any of the GPIOs.&amp;nbsp;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;For the nRF91 DK for example, the UART0 is using the pins&amp;nbsp;&lt;span&gt;P0.26, P0.27, P0.28, and P0.29 and they are routed to VCOM0.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The RTS, CTS lines are&amp;nbsp;not absolutely needed,&amp;nbsp;but usually recommended.&amp;nbsp;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;2) Please refer to the &lt;a href="https://devzone.nordicsemi.com/b/nrf9160-development-status/posts/nrf9160-development-status" rel="noopener noreferrer" target="_blank"&gt;Development Status page&lt;/a&gt; on what is supported and what is coming.&lt;/p&gt;
&lt;p&gt;Please note that the &lt;a href="https://www.nordicsemi.com/DocLib/Content/Product_Spec/nRF9160/latest/nRF9160_html5_keyfeatures" rel="noopener noreferrer" target="_blank"&gt;nRF9160 SIP&lt;/a&gt;&amp;nbsp;in &lt;strong&gt;not &lt;span style="text-decoration:underline;"&gt;just&lt;/span&gt; a modem.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;It has its own Microcontroller with the ARM Cortex M33++, &lt;a href="https://www.nordicsemi.com/DocLib/Content/Product_Spec/nRF9160/latest/nRF9160_html5_keyfeatures" rel="noopener noreferrer" target="_blank"&gt;Product Specification&lt;/a&gt;.&lt;br /&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-899523bfb156403ba706f25d61f60526/pastedimage1554987859224v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;The only functionality you would lose if you do not want to interface the nRF9160 SIP with a nRF52840 chip is typical BLE which the nrf52 has.&lt;/em&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>