<?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 TLM secCount always starts with 0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/51208/eddystone-tlm-seccount-always-starts-with-0</link><description>normally the secCount in Eddystone TLM should be the t ime since power-on or reboot: 
 https://github.com/google/eddystone/blob/master/eddystone-tlm/tlm-plain.md 
 but the current implementation looks like this in components/ble/ble_services/eddystone</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 22 Aug 2019 11:07:11 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/51208/eddystone-tlm-seccount-always-starts-with-0" /><item><title>RE: Eddystone TLM secCount always starts with 0</title><link>https://devzone.nordicsemi.com/thread/205550?ContentTypeID=1</link><pubDate>Thu, 22 Aug 2019 11:07:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ab455906-2e83-4a18-a475-c436d6a258df</guid><dc:creator>yuecelm</dc:creator><description>&lt;p&gt;sorry the bug report is invalid, my beacon is going to shutdown and a wakeup from it works like a reset. So the 0 value is coming from es_tlm_init which is completely valid...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Eddystone TLM secCount always starts with 0</title><link>https://devzone.nordicsemi.com/thread/205541?ContentTypeID=1</link><pubDate>Thu, 22 Aug 2019 10:59:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:67b7167b-2790-414e-8d20-573637fd955b</guid><dc:creator>yuecelm</dc:creator><description>&lt;p&gt;sorry, you are right, give me some time to re-analyse the problem...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Eddystone TLM secCount always starts with 0</title><link>https://devzone.nordicsemi.com/thread/205507?ContentTypeID=1</link><pubDate>Thu, 22 Aug 2019 09:31:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:af65018c-fa6b-40bb-9ca8-15f08b60874b</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I am afraid I do not see any connection between time_counter and TLM.&lt;/p&gt;
&lt;p&gt;Looking into nRF5 SDK v15.3.0, which is currently the newest release, I find es_tlm.c to use its own stopwatch for populating the SEC_CNT field. It is initialized in es_tlm_init(). Where is the link between the TLM frame in es_tlm.c and the time_counter value in es_security.c?&lt;/p&gt;
&lt;p&gt;In es_tlm.c, the SEC_CNT field is called &amp;quot;ADV_SEC&amp;quot; in a code comment, which is incorrect. The es_tlm_frame_t structure correctly uses the name sec_cnt for the field. I think this should be aligned to both use the same terminology, but I do not know if that alone is enough to warrant an update.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Eddystone TLM secCount always starts with 0</title><link>https://devzone.nordicsemi.com/thread/205313?ContentTypeID=1</link><pubDate>Wed, 21 Aug 2019 12:24:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:632df797-60b1-468f-9bfe-31c6501c9eb9</guid><dc:creator>yuecelm</dc:creator><description>&lt;p&gt;the problem is that&amp;nbsp;&lt;span&gt;time_counter is also used for secCount in Eddystone TLM, and &amp;quot;when an EID slot is configured&amp;quot; is not really the same as&amp;nbsp;&lt;/span&gt;&lt;span&gt;&amp;quot;time since power-on or reboot&amp;quot;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Eddystone TLM secCount always starts with 0</title><link>https://devzone.nordicsemi.com/thread/205305?ContentTypeID=1</link><pubDate>Wed, 21 Aug 2019 12:08:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:180a616e-e1e0-418d-ace5-6adbe41ad188</guid><dc:creator>tesc</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I need some help to better understand what is the issue, so that I can verify and file a bug report.&lt;/p&gt;
&lt;p&gt;From what I can tell, time_counter is correctly updated through the function es_security_update_time() whenever a beacon packet is sent (see the callback function adv_evt_handler() in nrf_ble_es.c.)&lt;/p&gt;
&lt;p&gt;time_counter is set to&amp;nbsp;APP_CONFIG_TIMING_INIT_VALUE on Eddystone module initialization, and/or when an EID slot is configured. Is this the issue, that it should have been set to a non-zero value (or not set at all) in any of those situations?&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Terje&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>