<?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>Peer manager flash write disabling</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/23240/peer-manager-flash-write-disabling</link><description>Hello, 
 i am writing an application which uses the SDK13 peer manager library for bonding. The Nordic chip is acting as a peripheral. 
 Is there an easy way to prevent the peer manager from saving every change to flash memory? For instance, when enabling</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 04 Jul 2017 14:26:42 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/23240/peer-manager-flash-write-disabling" /><item><title>RE: Peer manager flash write disabling</title><link>https://devzone.nordicsemi.com/thread/91398?ContentTypeID=1</link><pubDate>Tue, 04 Jul 2017 14:26:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9fa0c706-ecf6-47dc-a93a-b5b034b7858c</guid><dc:creator>tommik</dc:creator><description>&lt;p&gt;Thank you, this actually explains everything!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Peer manager flash write disabling</title><link>https://devzone.nordicsemi.com/thread/91397?ContentTypeID=1</link><pubDate>Tue, 04 Jul 2017 12:28:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0f56759a-b618-4435-b5ef-5675fe242ed1</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Peripheral is expected to store bonding information and CCCD configuration for bonded peers across connections (i.e., stored in persistent memory). If you don&amp;#39;t want that you should probably do pairing instead of bonding (set SEC_PARAM_BOND flag to &amp;#39;0&amp;#39;). Just be aware that the key exchange is vulnerable against passive eavesdropping (legacy pairing), so bonding is more secure.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>