<?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>what happened when I create a kernel timer (based on the 32k RTC) by nrf connect sdk on nrf 52840 dk?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/79796/what-happened-when-i-create-a-kernel-timer-based-on-the-32k-rtc-by-nrf-connect-sdk-on-nrf-52840-dk</link><description>what happened when I create a kernel timer (based on the 32k RTC) by nrf connect sdk on nrf 52840 dk? 
 static const struct k_timer my_timer; static const struct k_work my_work; 
 void my_work_handler(struct k_work *work) { printk(&amp;quot;timer is clock! /n</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 20 Sep 2021 07:20:00 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/79796/what-happened-when-i-create-a-kernel-timer-based-on-the-32k-rtc-by-nrf-connect-sdk-on-nrf-52840-dk" /><item><title>RE: what happened when I create a kernel timer (based on the 32k RTC) by nrf connect sdk on nrf 52840 dk?</title><link>https://devzone.nordicsemi.com/thread/330162?ContentTypeID=1</link><pubDate>Mon, 20 Sep 2021 07:20:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9c23720c-2e84-4d6b-8c38-f96ac8761974</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
[quote user=""][00:00:09.937,286] [1;31m&amp;lt;err&amp;gt; os: ***** USAGE FAULT *****[0m&lt;br /&gt;[00:00:09.937,316] [1;31m&amp;lt;err&amp;gt; os: Illegal use of the EPSR[0m&lt;br /&gt;[00:00:09.937,316] [1;31m&amp;lt;err&amp;gt; os: r0/a1: 0x0002c2a8 r1/a2: 0x200021d0 r2/a3: 0x200021d0[0m&lt;br /&gt;[00:00:09.937,316] [1;31m&amp;lt;err&amp;gt; os: r3/a4: 0x00000000 r12/ip: 0x00033bf7 r14/lr: 0x00023983[0m&lt;br /&gt;[00:00:09.937,316] [1;31m&amp;lt;err&amp;gt; os: xpsr: 0x60000021[0m&lt;br /&gt;[00:00:09.937,347] [1;31m&amp;lt;err&amp;gt; os: Faulting instruction address (r15/pc): 0x00000000[0m&lt;br /&gt;[00:00:09.937,347] [1;31m&amp;lt;err&amp;gt; os: &amp;gt;&amp;gt;&amp;gt; ZEPHYR FATAL ERROR 0: CPU exception on CPU 0[0m[/quote]
&lt;p&gt;&amp;nbsp;The registers here give you an indication on what the state was when the fault occurred.&lt;/p&gt;
&lt;p&gt;Could you try to resolve the flash mapped addresses using &amp;quot;arm-none-eabi-addr2line&amp;quot;?&lt;/p&gt;
&lt;p&gt;arm-none-eabi-addr2line -e my_build_folder/zephyr/zephyr.elf 0x23983&lt;/p&gt;
&lt;p&gt;&lt;span&gt;arm-none-eabi-addr2line -e my_build_folder/zephyr/zephyr.elf 0x2c2a8&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;arm-none-eabi-addr2line -e my_build_folder/zephyr/zephyr.elf 0x33bf7&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Kind regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Håkon&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>