<?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>Hostless vs Hosted Bluetooth LE design</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/91705/hostless-vs-hosted-bluetooth-le-design</link><description>I&amp;#39;m trying to go through the proes and cons of a Hosted Vs Hostless Solution for BLE using the nRF52840. I have an AP thats running a stripped down version of Linux. Currently I have the Host Stack running on the AP and the nRF52840 configured just as</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 07 Sep 2022 11:23:18 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/91705/hostless-vs-hosted-bluetooth-le-design" /><item><title>RE: Hostless vs Hosted Bluetooth LE design</title><link>https://devzone.nordicsemi.com/thread/385007?ContentTypeID=1</link><pubDate>Wed, 07 Sep 2022 11:23:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0f649a04-8cdd-49be-846a-8c7800b153e7</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Think this will be mainly depending on the application, I can see the potential to lower power if you run the host on the nRF52840 and thereby can optimize the serial interface (and lower the current). However, you may end up with a less generic solution if you run the host on the nRF52840, but if you know exactly what peer you want to connect (e.g. in terms of features and behaviour) then it should not be a problem to run the host on the nRF52840 either.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>