<?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>Bluetooth SIG qualification - timelines, ICS</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/34028/bluetooth-sig-qualification---timelines-ics</link><description>Hi, 
 The amount of information and reference documents available about Bluetooth qualification is overwhelming. It would be great if someone with this experience sheds some light on certain aspects of the process. Apologies if parts of this question</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 23 May 2018 07:38:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/34028/bluetooth-sig-qualification---timelines-ics" /><item><title>RE: Bluetooth SIG qualification - timelines, ICS</title><link>https://devzone.nordicsemi.com/thread/132891?ContentTypeID=1</link><pubDate>Wed, 23 May 2018 07:38:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6d570d75-48c2-460b-b42c-41bfa7cdc50b</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;yes, simply reference our qualified design for the softdevice and chip combo you are using and you should be fine.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth SIG qualification - timelines, ICS</title><link>https://devzone.nordicsemi.com/thread/131559?ContentTypeID=1</link><pubDate>Wed, 09 May 2018 14:43:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:75349ea3-fa7a-4d88-8be7-a7701e1cbe23</guid><dc:creator>chaitz</dc:creator><description>&lt;p&gt;The product&amp;nbsp;will only have custom services. So, the qualification process then needs testing for RF PHY. For the rest of the tests I assume the test evidence can state that it is just using the reference QDID properties.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth SIG qualification - timelines, ICS</title><link>https://devzone.nordicsemi.com/thread/131490?ContentTypeID=1</link><pubDate>Wed, 09 May 2018 11:46:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:10ade035-7bac-40d7-834f-a6fc6416a7c2</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;If you are following the reference design and do not have any bluetooth sig defined profiles that require qualification, yes. I would still recommend doing the rf_phy test, but that is up to your assessment.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth SIG qualification - timelines, ICS</title><link>https://devzone.nordicsemi.com/thread/131475?ContentTypeID=1</link><pubDate>Wed, 09 May 2018 10:35:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0578d652-877e-466c-9eea-953072075ae1</guid><dc:creator>chaitz</dc:creator><description>&lt;p&gt;Thank you for the detailed explanation.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It great to know that using the reference design allows for simplification of the qualification procedure. So, in this case&amp;nbsp;can the product can go through qualification path - &amp;quot;Path 1: Qualification Process with No Required Testing&amp;quot;?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bluetooth SIG qualification - timelines, ICS</title><link>https://devzone.nordicsemi.com/thread/131014?ContentTypeID=1</link><pubDate>Fri, 04 May 2018 12:26:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8b043adb-3808-45aa-b3bf-b4c0f19c49f0</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;1. No, if you are referencing our qualified design for the Softdevice you are using you do not need to retest this. If you make sure you also follow our reference layout on your custom board you can claim that the rf-phy test is also valid, but we usually recommend that customers retest this part to verify their design.&lt;/p&gt;
&lt;p&gt;2. Not sure. In-House depends on your experience in this things. BQTF will depend on the test facility so you have to ask them. Note that you can create a private case if you want us to help with schematic and layout review.&lt;/p&gt;
&lt;p&gt;3. No, if you change the ICS retesting will be required. It is perfectly fine to use only a subset of the features supported by the softdevice.&lt;/p&gt;
&lt;p&gt;4. RF tests require a tester. e.g &lt;a href="https://www.anritsu.com/en-US/test-measurement/products/mt8852b"&gt;Anritzu&lt;/a&gt; or similar. Other tests requires the pts tool from the bluetooth sig. But you only need to test profiles that is not already qualified as part of our profile subsystem. The profile subsystem can be combined with our qualified design for Softdevices.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>