<?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>How sdk upgradation affects bluetooth SIG product declaration?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/51188/how-sdk-upgradation-affects-bluetooth-sig-product-declaration</link><description>Hi, We are working on a product that uses EYSHCNZXZ, nRF52832 based module from Taiyo Yuden. The module is qualified as Component at &amp;#39;PHY layer only&amp;#39;. The QDID of this module is 81272. It&amp;#39;s declared with bluetooth version 4.2 (softdevice 132 V2.0.1).</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 21 Aug 2019 05:29:56 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/51188/how-sdk-upgradation-affects-bluetooth-sig-product-declaration" /><item><title>RE: How sdk upgradation affects bluetooth SIG product declaration?</title><link>https://devzone.nordicsemi.com/thread/205166?ContentTypeID=1</link><pubDate>Wed, 21 Aug 2019 05:29:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a9d1e7f0-2d9f-48c8-a6c3-f0548a35e49c</guid><dc:creator>Deljohn</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;span&gt;Andreas,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Thank you for&amp;nbsp;your reply.&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How sdk upgradation affects bluetooth SIG product declaration?</title><link>https://devzone.nordicsemi.com/thread/205015?ContentTypeID=1</link><pubDate>Tue, 20 Aug 2019 11:58:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:26a001b6-3899-4aa7-9ff4-16dff4e9cc8f</guid><dc:creator>Andreas</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;1. You can update the Softdevice if you do not make use or enable any new features that are not in the original declaration, meaning you can upgrade to make use of bug fixes and such.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;2. You can not use any Bluetooth 5 features and treat the device as Bluetooth 4.2. You might be able to disable Bluetooth 5 features and treat it as 4.2, but I am not sure how this would go, you might have to contact the SIG about this. Technically the SD versions compatible with SDK are Bluetooth 5, even if you do not make use of the 2 Mbps, extended advertising etc. Even though these are the &amp;#39;main features&amp;#39; of Bluetooth 5 they are actually optional, what decides if a device is Bluetooth 5 or 4.2 is whether or not the erratas from 4.2 have been implemented, and you can not disable these.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Unfortunately this is what might happen when using a 3rd party module. You could contact Taiyo Yuden and ask why they have not released a more up-to-date version (frankly SDK v11 is quite outdated), use another module/manufacturer or make the design yourself.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>