<?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>SDK 15.0.0 incompatible with S332</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/33550/sdk-15-0-0-incompatible-with-s332</link><description>BLE_GAP_ADV_SET_DATA_SIZE_MAX is use din ble_advertising.h 
 This macro is defined in ble_gap.h for each softdevice - however not in the header for S332. Also ble_gap_adv_data_t is missing. I&amp;#39;me using the code below to work around the defect. Can you</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 24 Apr 2018 08:44:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/33550/sdk-15-0-0-incompatible-with-s332" /><item><title>RE: SDK 15.0.0 incompatible with S332</title><link>https://devzone.nordicsemi.com/thread/129499?ContentTypeID=1</link><pubDate>Tue, 24 Apr 2018 08:44:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f27b9ad3-b265-426f-af02-953ac483412b</guid><dc:creator>Joakim Jakobsen</dc:creator><description>&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;There is no support for Softdevice S332 in SDK v15.0.0, so I would advise you to roll back to an SDK version where S332 is supported.&lt;/p&gt;
&lt;p&gt;There might be support for S332 again in future releases of the SDK. Roadmap related questions should be directed to your RSM. If you don&amp;#39;t know who that is, send me a PM with your location and I&amp;#39;ll provide you with the contact information.&lt;/p&gt;
&lt;p&gt;I&amp;#39;m sorry to hear that you are not satisfied, but I appreciate the feedback and I will forward this internally.&lt;/p&gt;
&lt;p&gt;Be sure to let us know if you face any other issues, and we will do our best to help you.&lt;/p&gt;
&lt;p&gt;Best regards, &lt;br /&gt;Joakim.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: SDK 15.0.0 incompatible with S332</title><link>https://devzone.nordicsemi.com/thread/129096?ContentTypeID=1</link><pubDate>Fri, 20 Apr 2018 08:25:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:43a06ca4-65fa-46f6-b690-e7899a7ff267</guid><dc:creator>Morten Kristiansen</dc:creator><description>&lt;p&gt;Well, as a followup there&amp;#39;s a lot more incompatibilities when you actually enable GAP, so my conclusion is SDK 15.0.0 completely breaks S332 and SDK14.2.0 has a defective fstorage. Guess my only option is to roll back and if I want work done.&lt;/p&gt;
&lt;p&gt;Nordic, I&amp;#39;m not that much of a fan of you.&amp;nbsp;The problem I have is when you have defects, instead of fixing them you release a new SDK with huge differences. The last time you left us stranded with thousands of nRF51 devices in a revision where only a defective SDK was available. I clearly understand that it&amp;#39;s more fun building new stuff than fixing it - but every time you do this hundreds of developers has to follow you. I&amp;#39;d very much appreciate fixes and API stability in comparison.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The faster we get our stuff done, the faster we&amp;#39;ll be on the market, the more we sell and the more we buy from you.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>