<?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>On how to deal with nWP-031 with nRF 51</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/38181/on-how-to-deal-with-nwp-031-with-nrf-51</link><description>Hi, 
 I am developing software supporting LEsecure using SDK 12.3 with nRF 51822. 
 There is a shift to SDK 15.0 as a measure against &amp;quot;nWP - 031&amp;quot;, but can not cope with nRF 51 because the HEX file of soft device does not exist? Or is it possible to cope</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 05 Sep 2018 07:31:35 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/38181/on-how-to-deal-with-nwp-031-with-nrf-51" /><item><title>RE: On how to deal with nWP-031 with nRF 51</title><link>https://devzone.nordicsemi.com/thread/147281?ContentTypeID=1</link><pubDate>Wed, 05 Sep 2018 07:31:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:afc45c01-ba23-4d43-ae45-b2172e34ec27</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Please refer to &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/37035/how-to-implement-ecc-functions-on-sdk-v12-3-0-and-nrf51822/142314#142314"&gt;this post&lt;/a&gt;&amp;nbsp;where I have described a simple fix for&amp;nbsp;SDK 12.3.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>