<?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>The effects of Zephyr LOGGING on system behavior</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/85764/the-effects-of-zephyr-logging-on-system-behavior</link><description>Hello, guys. 
 I have nRF51822 SoC running Zephyr OS. Among the other things, the nRF should communicate (over I2C) with the touch controller that will fire an interrupt every 20ms if the finger is pressing the touch area. This part of the system is illustrated</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 14 Mar 2022 16:26:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/85764/the-effects-of-zephyr-logging-on-system-behavior" /><item><title>RE: The effects of Zephyr LOGGING on system behavior</title><link>https://devzone.nordicsemi.com/thread/358049?ContentTypeID=1</link><pubDate>Mon, 14 Mar 2022 16:26:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7e202889-8f7d-4ef4-a923-2fa5b0f4a739</guid><dc:creator>bojan</dc:creator><description>&lt;p&gt;Hello, &lt;a href="https://devzone.nordicsemi.com/members/priyankakesav"&gt;Priyanka&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;Thanks for your reply. I closely analyzed the code (this is the code I am porting from SDK bare metal environment into Zephyr OS) and figured out that a kind of interrupt nesting was causing the issue.&lt;/p&gt;
&lt;p&gt;When I optimized the interrupt service routine, I was able to properly run the code with or without the CONFIG_LOG_MODE_IMMEDIATE flag.&lt;/p&gt;
&lt;p&gt;Thanks for your assistance, we can now close this topic.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Bojan.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: The effects of Zephyr LOGGING on system behavior</title><link>https://devzone.nordicsemi.com/thread/358048?ContentTypeID=1</link><pubDate>Mon, 14 Mar 2022 16:20:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:44ad70cb-a85d-4693-a322-55655bbf5943</guid><dc:creator>Priyanka</dc:creator><description>&lt;p&gt;Hi Bojan,&lt;/p&gt;
&lt;p&gt;Could you tell me what doesn&amp;#39;t work as expected when you set the &lt;a href="https://docs.zephyrproject.org/latest/kconfig.html#:~:text=It%20impacts%20performance%20of%20the%20system%20since%20time%20consuming%20operations%20are%20performed%20in%20the%20context%20of%20the%20log%20entry%20(e.g.%20high%20priority%20interrupt)"&gt;CONFIG_LOG_MODE_IMMEDIATE&lt;/a&gt; =n or remove the debug print line? In the link provided, it does mention that this can impact operations which perform on the context of log entry.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1647274944695v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Priyanka&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>