<?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>certification BLE wicth nRF24L01+</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/62720/certification-ble-wicth-nrf24l01</link><description>I modified the firmware of our control unit to allow BLE communication. Now It communicates with an ANDROID APP. The chip used is nRF24L01+, It send and get only Non-Connectable Undirected Advertising paket ( channels used: 37,38,39; It transmit every</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 17 Jun 2020 15:39:45 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/62720/certification-ble-wicth-nrf24l01" /><item><title>RE: certification BLE wicth nRF24L01+</title><link>https://devzone.nordicsemi.com/thread/255602?ContentTypeID=1</link><pubDate>Wed, 17 Jun 2020 15:39:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e84ce67f-22ee-4da9-aae5-c919b6a05cd1</guid><dc:creator>Jay Tyzzer</dc:creator><description>&lt;p&gt;1)&amp;nbsp; If you are sending a BLE packet,&amp;nbsp; i.e. a device that is operating and based on the Bluetooth Specification and you plan on commercializing it then you need to have it certified.&amp;nbsp; The Packet structure you stated is based on this specification.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;2)&amp;nbsp; Nordic has not qualified the nRF24L01+ with the Bluetooth Sig and has no plans on doing so.&amp;nbsp; (The nRF24L01+ is not recommended for new designs)&amp;nbsp; &amp;nbsp; So you would need to take&amp;nbsp;your product&amp;nbsp;thru Physical&amp;nbsp; Testing.&amp;nbsp; $$$$$&lt;/p&gt;
&lt;p&gt;3)&amp;nbsp; You would not be using a qualified stack so you would need to take your firmware&amp;nbsp;and have it certified.&amp;nbsp; $$$$$&lt;/p&gt;
&lt;p&gt;4)&amp;nbsp; You will need to be a member of the Bluetooth Sig.&amp;nbsp;&amp;nbsp;&lt;a href="https://www.bluetooth.com/develop-with-bluetooth/join/"&gt;https://www.bluetooth.com/develop-with-bluetooth/join/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I would suggest that you look at one of the nRF528xx devices that are qualified already, that run a qualified Stack (Softdevice).&amp;nbsp; That way you use Nordic&amp;#39;s QDID for that combo and only have to do a End Product listing.&amp;nbsp; You will need to be a member of the BT Sig.&amp;nbsp; There are tiers of memberships with tiered pricing.&amp;nbsp; I suggest you contact the Sig at www.bluetooth.com for more information on this and qualification.&amp;nbsp; &amp;nbsp;&lt;/p&gt;
&lt;p&gt;If all you want to do is transmit advertising packets only then I suggest the nRF52810&amp;nbsp; or the nRF52811 running the Softdevice S112. &amp;quot;&lt;span&gt;The S112 SoftDevice is a&amp;nbsp;&lt;/span&gt;&lt;span class="keyword"&gt;&lt;span class="tm_italic"&gt;Bluetooth&amp;reg;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/span&gt;Low Energy&lt;/span&gt;&lt;span&gt;&amp;nbsp;peripheral protocol stack solution.&amp;quot;&amp;nbsp; &amp;nbsp;Those two parts have a small memory footprint and would be excellent for your application.&amp;nbsp; And it gives you a migration path up if you decide you wish use a part with more memory and peripherals&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Good luck which ever way you go..&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Jay&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>