<?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>Flow control options for nRF52833</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/92684/flow-control-options-for-nrf52833</link><description>Hello, 
 
 because of some hardware constraints we had to put our nRF52833 behind an i2c-to-uart bridge (ref SC16IS741A ). 
 Our preliminary tests have showed some potential data loss in the communication from our board to the 52833 using the bridge.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 11 Jan 2023 09:53:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/92684/flow-control-options-for-nrf52833" /><item><title>RE: Flow control options for nRF52833</title><link>https://devzone.nordicsemi.com/thread/404253?ContentTypeID=1</link><pubDate>Wed, 11 Jan 2023 09:53:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d4c8eeda-544e-4b63-8d03-1a7c152b9f47</guid><dc:creator>Marshall</dc:creator><description>&lt;p&gt;Hi Benjamin&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I&amp;#39;m trying to develop a Zephyr Driver for the&amp;nbsp;&lt;span&gt;&amp;nbsp;&amp;nbsp;&lt;a href="https://www.nxp.com/docs/en/data-sheet/SC16IS741A.pdf"&gt;SC16IS7&lt;/a&gt;52 which is functionally similar to the one you have used.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Would you be able to share your library for the device, along with overlays, yaml etc to help get me started,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;It would be really appreciated.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Kind Regards&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Marshall&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flow control options for nRF52833</title><link>https://devzone.nordicsemi.com/thread/390694?ContentTypeID=1</link><pubDate>Thu, 13 Oct 2022 15:11:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:56620d1b-dfeb-4705-9204-a2263796f943</guid><dc:creator>bfrottier</dc:creator><description>&lt;p&gt;Perfect.&lt;/p&gt;
&lt;p&gt;Thank you Einar!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flow control options for nRF52833</title><link>https://devzone.nordicsemi.com/thread/390618?ContentTypeID=1</link><pubDate>Thu, 13 Oct 2022 11:26:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d580557f-9521-49bb-9462-438cb5f8811a</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Yes, the part about enabling flow control in the overlay file applies to other samples as well. (You can see it used a lot in&amp;nbsp;the SDK if you search for &amp;quot;hw-flow-control&amp;quot; in all &amp;quot;*.overlay&amp;quot; files.)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flow control options for nRF52833</title><link>https://devzone.nordicsemi.com/thread/390448?ContentTypeID=1</link><pubDate>Wed, 12 Oct 2022 12:38:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4f3cac85-bdee-4554-bf08-4ad3ced718c6</guid><dc:creator>bfrottier</dc:creator><description>&lt;p&gt;Hi Einar,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
[quote userid="7377" url="~/f/nordic-q-a/92684/flow-control-options-for-nrf52833/390011"]&lt;p&gt;You are right that HW flow control is what is supported, not software flow control.&lt;/p&gt;
&lt;p&gt;You are right about the Kconfig configurations when using Zigbee. Note that&amp;nbsp;CONFIG_ZIGBEE_UART_SUPPORTS_FLOW_CONTROL is just a configuration for the NCP sample, and and if you look at the implementation of the sample (nrf/samples/zigbee/ncp/src/main.c) you can see how it is used. Essentially it reads the pins from the device tree overlay file, and configures the UART accordingly by calls to&amp;nbsp;uart_line_ctrl_set().&amp;nbsp;The pins come from the device tree (or rather board specific overlay files in the sample), from the UART that is referenced by &amp;quot;zigbee_uart&amp;quot;, which for the nRF52833 DK for instance, maps to uart1.&lt;/p&gt;[/quote]
&lt;p&gt;thanks for the confirmation and clarification!&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
[quote userid="7377" url="~/f/nordic-q-a/92684/flow-control-options-for-nrf52833/390011"]As the above configuration is only for the Zigbee sample, you can ignore it when it comes to what is used in the bootloader. That will typically use what is in the DeviceTree directly, so you would just need to ensure that you have&amp;nbsp;control set for the&amp;nbsp;UART instance,[/quote]
&lt;p&gt;Does this also apply for other samples?&lt;/p&gt;
&lt;p&gt;For instance radio_test (nrf/samples/peripherical/radio_test) would only requires to add in the device tree (or overlay) &lt;strong&gt;rts-pin&lt;/strong&gt;, &lt;strong&gt;cts-pin&lt;/strong&gt; and &lt;strong&gt;hw-flow-control&lt;/strong&gt;?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Benjamin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Flow control options for nRF52833</title><link>https://devzone.nordicsemi.com/thread/390011?ContentTypeID=1</link><pubDate>Mon, 10 Oct 2022 12:06:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:558d4498-36d2-40fd-9d7c-b1d3f1a15e6d</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi Benjamin,&lt;/p&gt;
&lt;p&gt;You are right that HW flow control is what is supported, not software flow control.&lt;/p&gt;
&lt;p&gt;You are right about the Kconfig configurations when using Zigbee. Note that&amp;nbsp;CONFIG_ZIGBEE_UART_SUPPORTS_FLOW_CONTROL is just a configuration for the NCP sample, and and if you look at the implementation of the sample (nrf/samples/zigbee/ncp/src/main.c) you can see how it is used. Essentially it reads the pins from the device tree overlay file, and configures the UART accordingly by calls to&amp;nbsp;uart_line_ctrl_set().&amp;nbsp;The pins come from the device tree (or rather board specific overlay files in the sample), from the UART that is referenced by &amp;quot;zigbee_uart&amp;quot;, which for the nRF52833 DK for instance, maps to uart1.&lt;/p&gt;
&lt;p&gt;As the above configuration is only for the Zigbee sample, you can ignore it when it comes to what is used in the bootloader. That will typically use what is in the DeviceTree directly, so you would just need to ensure that you have&amp;nbsp;control set for the&amp;nbsp;UART instance, by having something like this in an overlay file for instance:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;&amp;amp;uart1 {
	status = &amp;quot;okay&amp;quot;;
	hw-flow-control;
};&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Einar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>