<?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>Using SD 132 on NRF52833</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/97994/using-sd-132-on-nrf52833</link><description>Hi, 
 We make a solution based on NRF52833 chips using SD 132 7.2.0. 
 It&amp;#39;s already deployed in production, but i have seen that this SD is not on the compatibility matrix https://infocenter.nordicsemi.com/index.jsp?topic=%2Fstruct_nrf52%2Fstruct%2Fnrf52833</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 23 Mar 2023 12:57:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/97994/using-sd-132-on-nrf52833" /><item><title>RE: Using SD 132 on NRF52833</title><link>https://devzone.nordicsemi.com/thread/417076?ContentTypeID=1</link><pubDate>Thu, 23 Mar 2023 12:57:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4fbce12a-874a-4d01-95af-b7b57823ed2c</guid><dc:creator>Julien</dc:creator><description>&lt;p&gt;Okay,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks for the answer&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using SD 132 on NRF52833</title><link>https://devzone.nordicsemi.com/thread/417027?ContentTypeID=1</link><pubDate>Thu, 23 Mar 2023 11:40:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dd7d4f7b-19c8-4466-92be-f0adbfce41a5</guid><dc:creator>Jared</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;That&amp;#39;s difficult to say as we don&amp;#39;t test the S132 with nRF52833. S140 might contain some bugfixes for the nRF52833 that hasn&amp;#39;t been included in the S132.In addition, at some point you&amp;#39;ll need to get the device Bluetooth qualified. The combination S132 and nRF52833 will not pass qualification as we haven&amp;#39;t added this option.&lt;/p&gt;
&lt;p&gt;regards&lt;br /&gt;Jared&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using SD 132 on NRF52833</title><link>https://devzone.nordicsemi.com/thread/417011?ContentTypeID=1</link><pubDate>Thu, 23 Mar 2023 10:18:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e2fe35c4-196b-4fac-a83b-765f9829f01f</guid><dc:creator>Julien</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Currently the NR52833 works with the SD132 in our customers, more than several month.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;We have not implemented DFU softdevice so we cannot to intervene.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;My question is what could be the risk of NRF52833 working with SD132.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Julien&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using SD 132 on NRF52833</title><link>https://devzone.nordicsemi.com/thread/417009?ContentTypeID=1</link><pubDate>Thu, 23 Mar 2023 10:13:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9a816e6c-3b1c-4f49-81d2-8b0ef6d9c9bf</guid><dc:creator>Jared</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Yes this is a mistake that should be corrected, the S132 does not support the nRF52833, and you should change the Softdevice to S140, S122 or S113.&lt;/p&gt;
&lt;p&gt;Changing the Softdevice is often a trivial task as long it supports all of the features that you&amp;#39;re application is using,&lt;/p&gt;
&lt;p&gt;regards&lt;/p&gt;
&lt;p&gt;Jared&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>