<?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 framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/9301/uart-framing-error-after-nvic-softreset</link><description>Hi all 
 Our application, built on the NRF51822 Rev. 3 and the SoftDevice S130 V1.0.0, uses the UART0 with 115&amp;#39;200 baud, 8N1, to communicate with another controller/PC. Hardware flow control is disabled. The SoftDevice is already initialized (with RC</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 12 Jul 2016 16:05:35 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/9301/uart-framing-error-after-nvic-softreset" /><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34340?ContentTypeID=1</link><pubDate>Tue, 12 Jul 2016 16:05:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a2806015-6483-4c72-a053-e00c21128ff7</guid><dc:creator>Inspectron</dc:creator><description>&lt;p&gt;Of course. I will send it on your mail in a few minutes.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34339?ContentTypeID=1</link><pubDate>Tue, 12 Jul 2016 15:54:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f4993a03-8e58-459d-9962-1e1548be8d0a</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;Could I have a picture, schematic, and layout of the rigado board?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34338?ContentTypeID=1</link><pubDate>Tue, 12 Jul 2016 15:41:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:62d2217f-c910-41b5-b440-65ada41de0fe</guid><dc:creator>Inspectron</dc:creator><description>&lt;p&gt;The sensor has a STI32F100 with a 12MHz Crystal on it. The crystal has 10ppm accuracy. I tested now the same application with RC LFCLK on the nRF52-DK and its working. So it should work with the RC LFCLK.&lt;/p&gt;
&lt;p&gt;With the Rigado board I tested all LFCK&amp;#39;s and none of this worked. And with the nRF52-DK all of these worked...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34337?ContentTypeID=1</link><pubDate>Tue, 12 Jul 2016 15:41:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6dd1f17-d849-4047-a3e2-3b9a122de844</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;Could you also try yo make the HFCLK run at all time?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34336?ContentTypeID=1</link><pubDate>Tue, 12 Jul 2016 15:31:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:78ba3c9e-3c77-4678-9f29-bbffc6a2a99c</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;Okay, I see, it means that there is a bit error. Could you check if you see the same problem when using RC oscillator or synthesized clock with the nRF52-DK?&lt;/p&gt;
&lt;p&gt;Also, what is the clock source on the sensor? How accurate is that clock?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34335?ContentTypeID=1</link><pubDate>Tue, 12 Jul 2016 15:14:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c83d3b4-3f7e-4dc7-80b6-d0a2e817df1c</guid><dc:creator>Inspectron</dc:creator><description>&lt;p&gt;Yes, I have APP_UART_COMMUNICATION_ERROR and APP_UART_FIFO_ERROR, like it is in the example. And I will get into APP_UART_COMMUNICATION_ERROR with the err_code = 9&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34334?ContentTypeID=1</link><pubDate>Tue, 12 Jul 2016 15:08:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6b40f136-cf13-493f-aae3-a74327d482bb</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;The problem can be related to a bit error. It will lead to an  APP_UART_COMMUNICATION_ERROR error. (How) Do you handle UART errors? Do you have a uart_error_handle(..) like in the UART example in the SDK?&lt;/p&gt;
&lt;p&gt;It can also be useful to take a look at this post regarding &lt;a href="https://devzone.nordicsemi.com/question/60125/my-device-is-freezing-and-restarting/?answer=60126#post-id-60126"&gt;system reset&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34333?ContentTypeID=1</link><pubDate>Tue, 12 Jul 2016 14:54:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2848e87e-71bc-403f-9d9f-bd59a199d445</guid><dc:creator>Inspectron</dc:creator><description>&lt;p&gt;I will now try it with the synthesized LFCLK. In the uart event handler the p_event-&amp;gt;evt_type is APP_UART_TX_EMPTY. But when I try the same software on the nRF52-DK, then p_event-&amp;gt;evt_type wont be APP_UART_TX_EMPTY and I then the CPU wont reset.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34332?ContentTypeID=1</link><pubDate>Tue, 12 Jul 2016 14:44:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d0ed4fe7-da0d-4406-a035-4f6c5bbcbb05</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;Yes, you can try to use the synthesized LFCLK instead. It has a considerably better frequency tolerance, but it also uses considerably more current, see &lt;a href="http://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.nrf52832.ps.v1.1%2Fclock.html&amp;amp;cp=2_2_0_18_3_4&amp;amp;anchor=unique_1886868466"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;By handling asserts I meant how you handle errors, if you check and handle error codes?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34331?ContentTypeID=1</link><pubDate>Tue, 12 Jul 2016 14:37:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cbeabb20-679a-44f0-94a9-7b1ae988aa0d</guid><dc:creator>Inspectron</dc:creator><description>&lt;p&gt;The wires from the sensor to uC are 30cm long. We cant change the Baudrate because the sensor has a fix baudrate(19200).&lt;/p&gt;
&lt;p&gt;Would it be better if we use the Synthesized LFCLK?&lt;/p&gt;
&lt;p&gt;What do you mean with, &lt;em&gt;how do you handle asserts&lt;/em&gt;?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34330?ContentTypeID=1</link><pubDate>Tue, 12 Jul 2016 14:30:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:469e9c04-2470-45f2-9a2e-5758281a796f</guid><dc:creator>FormerMember</dc:creator><description>&lt;p&gt;What is the distance between the nRF52 and the sensor? UART doesn&amp;#39;t work for more than 2-3m.&lt;/p&gt;
&lt;p&gt;How do you handle asserts?&lt;/p&gt;
&lt;p&gt;When using the internal RC oscillator instead of  external crystal, the clock rate on UART will not be that accurate.&lt;/p&gt;
&lt;p&gt;You can also consider to reduce the rate over UART.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34329?ContentTypeID=1</link><pubDate>Tue, 12 Jul 2016 12:29:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:041e18cd-4a72-4607-89ab-ae1e6b9740c0</guid><dc:creator>Inspectron</dc:creator><description>&lt;p&gt;I have the same problem. I work with a distance sensor which communicates trough UART. With an crystal oscillator everything works. But when I try the same without the crystal, then I will get a System reset, as soon as I recieve data from the sensor.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34328?ContentTypeID=1</link><pubDate>Mon, 21 Sep 2015 17:58:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e701980-e41a-4cdb-80b3-97e872f9f0f3</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;and i assume that the GPIO is set high when UART re-initialization has finished?
Can you check if there is a glitch on the GPIO pin after the reset?
The technique of using gpio as a signal to other side is good, and this way it should not mater if disabling the softdevice or not OR using XTAL or RC.
I am interested to look into your code, any possibility of sharing it in PM or in MY Page support portal?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34327?ContentTypeID=1</link><pubDate>Mon, 21 Sep 2015 14:42:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d932eb66-e8fb-410c-93c4-f5e6afcf707c</guid><dc:creator>Remo</dc:creator><description>&lt;p&gt;Hi Aryan. Thanks for the response. No, we don&amp;#39;t use the HW flow control of the UART interface. But we use a dedicated GPIO to signal the peer device when the interface of the nRF chip is ready and initialized. More precisely, as soon as this GPIO is set to HIGH by the nRF, the peer device may start sending commands.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: UART framing error after NVIC softreset</title><link>https://devzone.nordicsemi.com/thread/34326?ContentTypeID=1</link><pubDate>Mon, 21 Sep 2015 12:11:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:121b0c08-6a9a-48a8-9276-4ff372dbec23</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;When you said that there is a framing error, then it means that the device that is sending commands over serial port got out of sync. Is it using hardware flow control on UART?&lt;/p&gt;
&lt;p&gt;How does the peer device know that nRF chip booted up from its reset, and all its UART configuration re-initialized before sending new commands?&lt;/p&gt;
&lt;p&gt;I have a couple of theories of why disabling softdevice or using XTAL clock works for you. But before going that way, we have to make sure that your peer device is waiting enough time for the chip to come to a stable state. Please let me know how your peer device waits?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>