<?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>softwareserial on nrf52</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/26627/softwareserial-on-nrf52</link><description>We create library for work with software serial, we use two modules gpiote, timer.
We have done software serial one instance but we need four (actually just for rx). We don&amp;#39;t understand how to solve the problem with bit banging more than just one softwareserial</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 08 Nov 2017 16:21:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/26627/softwareserial-on-nrf52" /><item><title>RE: softwareserial on nrf52</title><link>https://devzone.nordicsemi.com/thread/104760?ContentTypeID=1</link><pubDate>Wed, 08 Nov 2017 16:21:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cae18265-ca7f-47c6-a018-696d07ef7765</guid><dc:creator>Stas</dc:creator><description>&lt;p&gt;Mostly we need only 9600 baudrate. But It seems best decision is to use additional chip e.g. stm32f205 has 4 usart, 2 uart.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softwareserial on nrf52</title><link>https://devzone.nordicsemi.com/thread/104759?ContentTypeID=1</link><pubDate>Wed, 08 Nov 2017 16:02:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:af016b3f-8dd3-483b-bace-a8169df9394e</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Yes, but I was thinking of high UART baudrate , says 115200bps, the CPU has to wake up every 8us. Also since the 4 UART is not syncronized, you need to sample twice as fast as the clock to make sure you won&amp;#39;t miss any pulse.
Another limitation is if you have higher priority interrupt (softdevice activity for example) you will miss some bytes on UART.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softwareserial on nrf52</title><link>https://devzone.nordicsemi.com/thread/104757?ContentTypeID=1</link><pubDate>Tue, 07 Nov 2017 19:13:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ca97ec1d-0835-4c89-bd13-9516823f2e13</guid><dc:creator>Stas</dc:creator><description>&lt;p&gt;CPU to read pins only on timer interrupt. All time after interrupt CPU in WFI state.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softwareserial on nrf52</title><link>https://devzone.nordicsemi.com/thread/104758?ContentTypeID=1</link><pubDate>Tue, 07 Nov 2017 16:39:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6eeae3b6-51d2-4cd5-bf8f-319ac64d4627</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;How exactly did you implement your soft serial ? My understanding is to use high frequency timer, and use CPU to read the pin on every pulse of the timer, to detect the start bit , stop bit and the data. And on each pulse of the timer the CPU read all 4 pins a the same time, so it doesn&amp;#39;t matter if you have 4 UART or more.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s mor like a parallel port, but in this case you have only 4 bit, and start bit and stop bit has to be handled.&lt;/p&gt;
&lt;p&gt;But this solution requires the CPU to stay in the timer event handle most of the time. So what you are thinking of using external UART chip maybe a better solution.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softwareserial on nrf52</title><link>https://devzone.nordicsemi.com/thread/104756?ContentTypeID=1</link><pubDate>Tue, 07 Nov 2017 11:28:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1aca32cc-4607-4cf7-b75d-c6c8297a4aca</guid><dc:creator>Stas</dc:creator><description>&lt;p&gt;The problem is we can not manage handler from different instances of one timer simultaneously. We can work only with one softserial uart at a time. When the packets coincide our library is fail. So we wonder could freertos solve this problem. We gonna use hardware uart too of course.
We tend to use additional chip stm32f205ret6 it has 6 uart modules 51 GPIO and a lot of other peripherals, on the board we gonna connect it by spi with our main chip nrf52832.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: softwareserial on nrf52</title><link>https://devzone.nordicsemi.com/thread/104755?ContentTypeID=1</link><pubDate>Tue, 07 Nov 2017 10:11:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4ec1c559-18e7-457a-8ed7-93b82ec0c0a6</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Stas,&lt;/p&gt;
&lt;p&gt;Could you explain a little bit more what is the problem when you mentioned &amp;quot;some conflicts in timer handlers&amp;quot; ?&lt;/p&gt;
&lt;p&gt;Could you provide some more information why you can&amp;#39;t use the hardware UART on the nRF52 ? At least it would reduce the number of bit banging UART to 3&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>