<?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>UART HW flow control bugs</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/27327/uart-hw-flow-control-bugs</link><description>I have an nrf52832 connected to a UART-USB driver with RTS/CTS. CLI manages the UART connection. Using SDK 14.0. 
 When HWFC is enabled, if a serial connection is NOT established immediately, the scheduler library overflows with tasks causing the device</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 30 May 2018 02:49:25 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/27327/uart-hw-flow-control-bugs" /><item><title>RE: UART HW flow control bugs</title><link>https://devzone.nordicsemi.com/thread/133916?ContentTypeID=1</link><pubDate>Wed, 30 May 2018 02:49:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8fa8dea1-b869-490a-b36d-f79cec165d16</guid><dc:creator>abhipray</dc:creator><description>&lt;p&gt;Oh wow, thanks for that. Any ideas on possible solutions?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART HW flow control bugs</title><link>https://devzone.nordicsemi.com/thread/133915?ContentTypeID=1</link><pubDate>Wed, 30 May 2018 02:47:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:07f62e88-2a0d-45c0-a1bf-1a8bfff0ea3d</guid><dc:creator>hmolesworth</dc:creator><description>&lt;p&gt;I posted this elsewhere, but offhand forget where.&amp;nbsp;I think that the flow control is incorrectly inverted in the hardware for use with a UART-USB (typically an FTDI part) connected to a PC. The complication starts with the meaning of &amp;quot;flow control&amp;quot;, as there are at least two versions, the traditional modem CTS/RTS usage and the more modern CTS/RTS handshake. I added these comments to clarify this:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="c_cpp"&gt;/**@brief  Function for initializing the UART module.
 * Traditional Modem Flow Control
 * If flow control is enabled, a transmission will be automatically suspended when CTS is deactivated and
 * resumed when CTS is activated again.
 * A byte that is in transmission when CTS is deactivated will be fully transmitted before the transmission is
 * suspended.
 * nRF52 DTE Output pin to DCE - asserts to request transmit
 * nRF52 DTE Input pin from DCE - asserts to allow transmit
 *
 * Hardware Flow Control
 * &amp;quot;RTS/CTS handshaking&amp;quot; the DTE asserts RTS whenever it is ready to receive data from the DCE, and the DCE
 * asserts CTS whenever it is ready to receive data from the DTE. Unlike the original use of RTS and CTS with
 * half-duplex modems, these two signals operate independently from one another.
 * nRF52 DTE Output pin to DCE - asserts to allow DCE to transmit
 * nRF52 DTE Input pin from DCE - asserts to allow nRF52 DTE transmit
 */
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;The nRF52 hardware supports the traditional modem usage, but the software is written for the more recent CTS/RTS handshake which requires an inverter for proper operation as the nRF52832 does not allow configuring active-high/low operation unless the lines are driven manually (the logic is inverted so does not work correctly). Hope this helps.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART HW flow control bugs</title><link>https://devzone.nordicsemi.com/thread/133914?ContentTypeID=1</link><pubDate>Wed, 30 May 2018 02:15:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:09eb845e-6928-4bba-bfa5-bda881233b77</guid><dc:creator>abhipray</dc:creator><description>&lt;p&gt;Any updates on this? We&amp;#39;re still seeing this issue.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART HW flow control bugs</title><link>https://devzone.nordicsemi.com/thread/107952?ContentTypeID=1</link><pubDate>Tue, 21 Nov 2017 18:21:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:df76f4ec-73ab-4b85-9bf8-54adf61bc670</guid><dc:creator>abhipray</dc:creator><description>&lt;p&gt;I have not tested this on the DK. The UART-USB bridge is an SI Labs CP-2102. I can try to upload some example code that reproduces the problem.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART HW flow control bugs</title><link>https://devzone.nordicsemi.com/thread/107951?ContentTypeID=1</link><pubDate>Mon, 20 Nov 2017 16:39:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bc1cf647-6d52-4c65-a885-a9e84ac1d22e</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Do you have this issue when using the nrf52832-DK ?&lt;/li&gt;
&lt;li&gt;Since this is not a eval kit/ DK, what kind &amp;quot;UART-USB bridge&amp;quot; are you using ?&lt;/li&gt;
&lt;li&gt;Could you upload some example code / project, so that we can reproduce the issue here ?&lt;/li&gt;
&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART HW flow control bugs</title><link>https://devzone.nordicsemi.com/thread/107950?ContentTypeID=1</link><pubDate>Mon, 20 Nov 2017 15:58:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:50f4a29d-e00b-43bc-bdfb-0b0dd48520d1</guid><dc:creator>abhipray</dc:creator><description>&lt;p&gt;I am not using an eval kit. Would this same problem show up if I use an external Segger j-link probe for programming?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART HW flow control bugs</title><link>https://devzone.nordicsemi.com/thread/107949?ContentTypeID=1</link><pubDate>Mon, 20 Nov 2017 14:05:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f6ba8a45-10c6-4d35-8c1a-b2004178ba5e</guid><dc:creator>Krzysztof Chruscinski</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;it maybe related to the fact how Segger chip determines if HWFC should be &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52/dita/nrf52/development/nrf52_dev_kit/dyn_hw_flow_control.html"&gt;used&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>