<?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>slow down the CPU clock</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/76613/slow-down-the-cpu-clock</link><description>Hello, I am using NRF52840, I tried to use Jtrce for debugging but the results are unreliable due to design of the nRF52 target device in regards to the trace clock speed. The only way around this is to slow down the CPU clock. can you tell me what is</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 23 Jun 2021 16:47:27 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/76613/slow-down-the-cpu-clock" /><item><title>RE: slow down the CPU clock</title><link>https://devzone.nordicsemi.com/thread/316813?ContentTypeID=1</link><pubDate>Wed, 23 Jun 2021 16:47:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d13c3abc-1404-479a-9c66-ab8dbb6f8d7c</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;Seems to continue here:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/76684/leading-trace-solution---nrf52840"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/76684/leading-trace-solution---nrf52840&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: slow down the CPU clock</title><link>https://devzone.nordicsemi.com/thread/316780?ContentTypeID=1</link><pubDate>Wed, 23 Jun 2021 14:23:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0581625a-d397-4de5-a5f4-f39cbece961f</guid><dc:creator>noy</dc:creator><description>&lt;p&gt;HI,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;our project is working in Ozone.&lt;/p&gt;
&lt;p&gt;In Ozone there is an option to see&amp;nbsp;&lt;span&gt;&amp;nbsp;the execution count of source lines and instructions. The counters are updated live from the trace stream, while the application is running&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;In some sequential sections of the code, the executions counters do not match . Below is an example:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1624458141913v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Software Engineer of SEGGER told us the result are&amp;nbsp;&lt;span&gt;unreliable(overflow issue )due to design of the nRF52 target device in regards to the trace clock speed.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: slow down the CPU clock</title><link>https://devzone.nordicsemi.com/thread/316767?ContentTypeID=1</link><pubDate>Wed, 23 Jun 2021 13:50:22 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cd6975d2-f8f8-4e49-af09-d692df3b5daf</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi noy,&lt;/p&gt;
[quote user=""], I tried to use Jtrce for debugging but the results are unreliable due to design of the nRF52 target device in regards to the trace clock speed. The only way around this is to slow down the CPU clock[/quote]
&lt;p&gt;Can you explain a bit more at the exact specification due to which you see unreliable results caused by to the JTrace debugging? I am not sure if we allow dynamic control of clock speed as these are done internally . Before I go to the architects on this, I need to understand exactly in detail what is it that you are trying to solve.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>