<?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>Laird BL652 Bluetooth SIG Declaration</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22618/laird-bl652-bluetooth-sig-declaration</link><description>Hello, 
 We are new in Bluetooth development world. We want to use Laird&amp;#39;s BL652 module. At beginning we want to use smartBasic and later Nordic SDK directly. Is it possible to declare our product and use simultaneously both development ways within one</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 09 Jun 2017 09:18:49 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22618/laird-bl652-bluetooth-sig-declaration" /><item><title>RE: Laird BL652 Bluetooth SIG Declaration</title><link>https://devzone.nordicsemi.com/thread/88971?ContentTypeID=1</link><pubDate>Fri, 09 Jun 2017 09:18:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7e88be98-811f-4d88-87ed-79bd42c5c767</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;I would recommend using the latest non alpha release of the softdevice. Or start developing on an alpha version if you don&amp;#39;t mind migrating to the stable version when it&amp;#39;s released and before you go to production.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m afraid I cannot really comment on the timeline of v5. I would guess sometime this summer, but you should check with our RSM for your region if you need a more accurate estimate.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Laird BL652 Bluetooth SIG Declaration</title><link>https://devzone.nordicsemi.com/thread/88970?ContentTypeID=1</link><pubDate>Thu, 08 Jun 2017 19:06:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7a7fe0b0-033f-4957-8916-291b140a30b4</guid><dc:creator>Luk3</dc:creator><description>&lt;p&gt;Thank you. Is it recommended to use SD v4.x.x instead of v3.0.0? When S132 v5 production will be released?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Laird BL652 Bluetooth SIG Declaration</title><link>https://devzone.nordicsemi.com/thread/88969?ContentTypeID=1</link><pubDate>Thu, 08 Jun 2017 11:21:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f868dbcd-98a4-4c5f-b4e8-9a99a075f348</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;Yes, it should be possible to use QDID 87158 for both developments as long as you use the same softdevice on the two. This is because QDID 87158 is referenceing the Link layer and Host layer of the SD, so it is basically the same as the Nordic QDID.&lt;/p&gt;
&lt;p&gt;When it comes to Bluetooth 5, you can use the same QDID as long as you don&amp;#39;t use any of the new features. If you use new features, thus changing the PIXIT document you need a new QDID.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>