<?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>NRF52832 - real time tasks(CAN Open)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/23333/nrf52832---real-time-tasks-can-open</link><description>Would it be advisable for system design to use CAN(CAN Open) and BT simultaneously on nRF52832 IC? 
 Why this bothers me is because capabilities of nRF BT MCU&amp;#39;s are growing both in processor power and memory size, but still soft-device can interrupt</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 07 Jul 2017 09:36:01 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/23333/nrf52832---real-time-tasks-can-open" /><item><title>RE: NRF52832 - real time tasks(CAN Open)</title><link>https://devzone.nordicsemi.com/thread/91735?ContentTypeID=1</link><pubDate>Fri, 07 Jul 2017 09:36:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b3237616-510c-4314-94d9-0142e5de3879</guid><dc:creator>tuv0k</dc:creator><description>&lt;p&gt;I&amp;#39;ll stick with STM32 then. That&amp;#39;s what I thought in first place. Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52832 - real time tasks(CAN Open)</title><link>https://devzone.nordicsemi.com/thread/91734?ContentTypeID=1</link><pubDate>Fri, 07 Jul 2017 06:59:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eea20bfa-f512-4045-9935-a55c9715966b</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;It could work if you are sure that your SW driven interface will fit into certain uninterrupted time slot. That is typically few milliseconds wide but with some effort and limitations you can extend it to much more. However if CAN use case you have in mind is asynchronous with some longer unpredictable activity then you are almost certain to fail. nRF5x are great MCUs but if your desired interface isn&amp;#39;t supported in HW it&amp;#39;s better to sacrifice few cents (or bucks), few dozens of microAmps, some PCB real estate an put dedicated low-power MCU to handle that (and that being connected with SPI or I2C). I&amp;#39;ve seen several designs with NXP LPC or STM ST32 and nRF5x which were pretty good in exactly this.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>