<?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>Strange nRF52833DK behaviour with nRF Connect SDK 2.3.0</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/99626/strange-nrf52833dk-behaviour-with-nrf-connect-sdk-2-3-0</link><description>Dear Support Team, 
 I recently started evaluating a nRF52833 DK board with the nRF Connect SDK 2.3.0. 
 I noticed a very strange behaviour while developing an ADXL accelerometer driver with interrupt handling. This is the setup and the symptoms: 
 Interrupt</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 19 May 2023 09:19:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/99626/strange-nrf52833dk-behaviour-with-nrf-connect-sdk-2-3-0" /><item><title>RE: Strange nRF52833DK behaviour with nRF Connect SDK 2.3.0</title><link>https://devzone.nordicsemi.com/thread/426209?ContentTypeID=1</link><pubDate>Fri, 19 May 2023 09:19:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0c6f323a-ab9e-4ca0-8c9f-7455e76a99d6</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;No worries, Viktor. I am glad to hear that you found the source of the issue.&lt;/p&gt;
&lt;p&gt;I will close the ticket.&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><item><title>RE: Strange nRF52833DK behaviour with nRF Connect SDK 2.3.0</title><link>https://devzone.nordicsemi.com/thread/426043?ContentTypeID=1</link><pubDate>Wed, 17 May 2023 07:23:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e2ca5cc9-4473-4cca-a076-51f49c622a4f</guid><dc:creator>ViktorVarjas</dc:creator><description>&lt;p&gt;Hello Edvin!&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank you very much for the reply! In the meantime I figured out that the source of the strange behavior is not the DK but the accelerator triggering the interrupt.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thank again and sorry for wasting you time! :) From my side this case can be deleted!&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;All the ebst,&lt;/p&gt;
&lt;p&gt;Viktor&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Strange nRF52833DK behaviour with nRF Connect SDK 2.3.0</title><link>https://devzone.nordicsemi.com/thread/425109?ContentTypeID=1</link><pubDate>Thu, 11 May 2023 12:46:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f7cf6670-0b7b-4cc7-b31a-556ccd70f417</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello Viktor,&lt;/p&gt;
&lt;p&gt;I can&amp;#39;t tell what&amp;#39;s wrong from your snippet. Did you try to debug the application after the power cycle? How about logs? Do you see any logs? Try adding a piece of logging at the very start of your main() to see if this is even reached.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If you are replicating this issue on nRF52833 DKs, would it be possible to upload the application folder here so that I can try to replicate the same behavior on my desk?&lt;/p&gt;
&lt;p&gt;&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>