<?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>What would be a good reason to use NRF8001 with a separate microcontroller instead of having a one-chip solution with NRF52</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/32999/what-would-be-a-good-reason-to-use-nrf8001-with-a-separate-microcontroller-instead-of-having-a-one-chip-solution-with-nrf52</link><description>I know that few companies choose to use NRF528001 with a separate microcontroller like Fitbit. 
 I would like to know why would they do so instead of using an NRF52 chip that already has the BLE capability and consumes less space. 
 Would there be any</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 09 Apr 2018 10:03:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/32999/what-would-be-a-good-reason-to-use-nrf8001-with-a-separate-microcontroller-instead-of-having-a-one-chip-solution-with-nrf52" /><item><title>RE: What would be a good reason to use NRF8001 with a separate microcontroller instead of having a one-chip solution with NRF52</title><link>https://devzone.nordicsemi.com/thread/127385?ContentTypeID=1</link><pubDate>Mon, 09 Apr 2018 10:03:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3b12c6de-2e89-4ff2-bd63-39653a5a72bb</guid><dc:creator>David Edwin</dc:creator><description>&lt;p&gt;If your application can fit in a single microcontroller then you should consider the nRF5x series. You should consider the nRF8001 only when the nRF5 series does not fit your needs and you need a connectivity solution with a 2 chip solution. Even at that stage you should still consider the nRF5 series as a connectivty option vs the nRF8001 as a connectivity option before a decision.&lt;/p&gt;
&lt;p&gt;One of the advantages of the nRF8001 as a connectivity option is has a smaller and easier to use interface as compare to the nRF5x connectivity option.&lt;/p&gt;
&lt;p&gt;However you can choose to have your own custom connectivity command set for your application running on the nR5x connectivity and compare that to your needs.&lt;/p&gt;
&lt;p&gt;In any case use an evaluation to see what fits your needs.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What would be a good reason to use NRF8001 with a separate microcontroller instead of having a one-chip solution with NRF52</title><link>https://devzone.nordicsemi.com/thread/126606?ContentTypeID=1</link><pubDate>Tue, 03 Apr 2018 08:39:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fe5e7049-39e6-48ec-bab8-f6341cc59d97</guid><dc:creator>haakonsh</dc:creator><description>&lt;p&gt;Hey John,&lt;/p&gt;
&lt;p&gt;I do not know of any advantage of using the nRF8001. I believe some manufacturers have used 8001 in their product because the nRF52832 was not ready at the time of development. I strongly urge you to use an nRF52 series SoC over the nRF8001 Tranceiver + ext MCU. We have a lot more resources dedicated to supporting the new 52 series than the old 8001.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;Håkon.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>