<?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>IOT Timer Resolution ICMP example</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/34526/iot-timer-resolution-icmp-example</link><description>Hi, 
 I&amp;#39;m using the ICMP example provided in SDK 15 to test the 6lowpan and wanted to check the RTT from the nrf52832 dev kit. 
 I managed to do so with the IOT Timer, I check the time when sending the ICMP packet and print the difference upon receiving</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 23 May 2018 11:12:22 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/34526/iot-timer-resolution-icmp-example" /><item><title>RE: IOT Timer Resolution ICMP example</title><link>https://devzone.nordicsemi.com/thread/132960?ContentTypeID=1</link><pubDate>Wed, 23 May 2018 11:12:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f4a86135-06ca-4ac3-8fcc-16e475590cb2</guid><dc:creator>gsalazar</dc:creator><description>&lt;p&gt;Hi,&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
&lt;p&gt;I did what you sugested and the error comes from the main.c of the ICMP example in line 526, which corresponds to the&amp;nbsp;&lt;strong&gt;iot_timer_init&lt;/strong&gt; function&lt;strong&gt;.&amp;nbsp;&lt;/strong&gt;The error code is 7, which is INVALID_PARAMETER.&lt;/p&gt;
&lt;p&gt;After checking, I observed that in the &lt;strong&gt;app_timer.h&lt;/strong&gt; the&amp;nbsp;&lt;strong&gt;APP_TIMER_MIN_TIMEOUT_TICKS&lt;/strong&gt;&amp;nbsp;was defined as 5 ms. Changed that to 1 ms and now everything works.&lt;/p&gt;
&lt;p&gt;Thank you for&amp;nbsp;pointing me in the right direction.&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: IOT Timer Resolution ICMP example</title><link>https://devzone.nordicsemi.com/thread/132909?ContentTypeID=1</link><pubDate>Wed, 23 May 2018 08:11:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c2571d45-7e7b-4483-9a7a-1d24befc4ad1</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Where does this error come from?&lt;/p&gt;
&lt;p&gt;When you get these kind of errors, they typically come from one of the&amp;nbsp;APP_ERROR_CHECK(err_code); where the err_code != NRF_SUCCESS (0).&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Try to define DEBUG in your preprocessor defines, and then disable optimization (set it to -O0). Then try to debug, and set a breakpoint on line 90 in app_error.c, and see if it stops there. Then you can add *p_info to watch, and check where the APP_ERROR_CHECK(err_code); that triggered is located. See if you can make any sense of the call that returned the err_code, and why it did.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>