<?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>Manually set resolvable address.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24174/manually-set-resolvable-address</link><description>I am using S132V3 on NRF52832 device. In my application we need to set a static, non-rotating, private resolvable address. I can&amp;#39;t get into why that is here. In theory this should be easy, just compute a valid address and call sd_ble_gap_addr_set(), however</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 11 Aug 2017 11:53:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24174/manually-set-resolvable-address" /><item><title>RE: Manually set resolvable address.</title><link>https://devzone.nordicsemi.com/thread/95198?ContentTypeID=1</link><pubDate>Fri, 11 Aug 2017 11:53:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:86845d99-4cf9-40bb-b10f-87df2d3757ee</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Jon,&lt;/p&gt;
&lt;p&gt;How exactly did you set the sd_ble_gap_privacy_set() ? I just tested here with S132 v5.0.0 on SDK v14, it worked fine, I have new address everytime I called it and updated every minute. Here what I used:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;privacy_param.privacy_mode=BLE_GAP_PRIVACY_MODE_DEVICE_PRIVACY;
privacy_param.private_addr_cycle_s=60;
privacy_param.private_addr_type=BLE_GAP_ADDR_TYPE_RANDOM_PRIVATE_RESOLVABLE;
privacy_param.p_device_irk= NULL;
err_code = sd_ble_gap_privacy_set(&amp;amp;privacy_param);
&lt;/code&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Manually set resolvable address.</title><link>https://devzone.nordicsemi.com/thread/95197?ContentTypeID=1</link><pubDate>Thu, 10 Aug 2017 15:17:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0051f2a-220a-4a12-a22c-c3fb20ca2faa</guid><dc:creator>jon pry</dc:creator><description>&lt;p&gt;I can&amp;#39;t say why I need it except under NDA. The S132 V2 API provides the functionality I need, since it requires the user to generate the addresses, but I would prefer not to use the aging SDK.&lt;/p&gt;
&lt;p&gt;As a work around, I could potentially deal with the randomly generated addresses, but I&amp;#39;ve run into an interesting bug. When I enable privacy through sd_ble_gap_privacy_set. The first address after power on it always the same. I am concerned that the sequence of addresses used may always be the same. I&amp;#39;ve also encountered bugs where the address rotation fails to happen even though a private resolvable address is clearly being advertised.&lt;/p&gt;
&lt;p&gt;I guess that is my real problem with this new API. There is no control over how/when these &amp;quot;random&amp;quot; addresses are generated. There&amp;#39;s really a lot of non ideal times to be rotating the address when operating as a central. For example when I see a device advertise I want to connect to, it would be best if the SD did not change my address for the next few seconds so that the connection attempt does not fail.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Manually set resolvable address.</title><link>https://devzone.nordicsemi.com/thread/95196?ContentTypeID=1</link><pubDate>Wed, 09 Aug 2017 12:07:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2035a1a4-51c4-4020-9de1-6a159c4e985a</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;I afraid this is restricted by the spec that the resolvable address shouldn&amp;#39;t be set manually. This is due to the main purpose of the random resolvable address, to provide privacy.&lt;/p&gt;
&lt;p&gt;Modifying RAM may not be a good idea, as you already experienced, in some functions, we do check the first bit.&lt;/p&gt;
&lt;p&gt;Why do you need a static resolvable address  ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>