<?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>Eddystone EID slot&amp;#39;s IK is not properly restored from flash on POR</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/20131/eddystone-eid-slot-s-ik-is-not-properly-restored-from-flash-on-por</link><description>Hi,
this is for anyone having problem with the eddystone EID after reboot. There seems to be a problem that the EID slot will write the encrypted IK to flash instead of the plain one.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 03 Mar 2017 14:23:38 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/20131/eddystone-eid-slot-s-ik-is-not-properly-restored-from-flash-on-por" /><item><title>RE: Eddystone EID slot's IK is not properly restored from flash on POR</title><link>https://devzone.nordicsemi.com/thread/78370?ContentTypeID=1</link><pubDate>Fri, 03 Mar 2017 14:23:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b83e45c6-e156-415a-9d55-eb17c608d255</guid><dc:creator>Sigurd</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thank you for reporting this and for posting the patch.&lt;/p&gt;
&lt;p&gt;This will be fixed in the next SDK release (SDK 13.0.0).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Eddystone EID slot's IK is not properly restored from flash on POR</title><link>https://devzone.nordicsemi.com/thread/78369?ContentTypeID=1</link><pubDate>Thu, 02 Mar 2017 14:09:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1cb23d1b-470d-43d7-ae02-556d6f49210a</guid><dc:creator>Tamisoft</dc:creator><description>&lt;p&gt;This following patch fixes the problem in SDK 12.2.0 (I think it can apply to 13.0.1alpha as well):&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;diff --git a/components/libraries/experimental_eddystone/es_slot.c b/components/libraries/experimental_eddystone/es_slot.c
index e589865..a2283e7 100644
--- a/components/libraries/experimental_eddystone/es_slot.c
+++ b/components/libraries/experimental_eddystone/es_slot.c
@@ -214,7 +214,7 @@ ret_code_t es_slot_write_to_flash(uint8_t slot_no)
         {
             m_reg.slots[slot_no].seconds  = es_security_clock_get(slot_no);
             m_reg.slots[slot_no].k_scaler = es_security_scaler_get(slot_no);
-            es_security_encrypted_eid_id_key_get(slot_no, m_reg.slots[slot_no].ik);
+            es_security_plain_eid_id_key_get(slot_no, m_reg.slots[slot_no].ik);
         }
         return es_flash_access_slot_configs(slot_no,
                                             &amp;amp;m_reg.slots[slot_no],
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;We have tested it, and google recognizes the device even if it was rebooted. This was also verified by the eidtools.py.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>