<?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>Using printf with ITM</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/31021/using-printf-with-itm</link><description>I would like to use printf using ITM for debugging my application using a BL652 module (nRf52832). 
 I have followed the instructions in the Keil paper APNT_308. Printf is working fine when I execute the code on the PCA10040 board, but when I connect</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 05 Mar 2018 20:18:08 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/31021/using-printf-with-itm" /><item><title>RE: Using printf with ITM</title><link>https://devzone.nordicsemi.com/thread/122912?ContentTypeID=1</link><pubDate>Mon, 05 Mar 2018 20:18:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:109ebb38-273b-4f13-a141-0e4f4cc2d63e</guid><dc:creator>Per Andersen</dc:creator><description>&lt;p&gt;Updating to Segger v 6.22f did the job, thank you.&lt;/p&gt;
&lt;p&gt;/Per&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Using printf with ITM</title><link>https://devzone.nordicsemi.com/thread/122742?ContentTypeID=1</link><pubDate>Mon, 05 Mar 2018 07:58:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:57ef85c5-d691-4afb-8e18-63541b53d6ef</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;There was a bug in segger&amp;#39;s firmware where it listened on the wrong SWO pin in DEBUG_OUT mode and therefore did not route the SWO signal correctly, and this was fixed in v6.22f.&lt;/p&gt;
&lt;p&gt;Could you try a newer Segger JLink Driver and see if this works better? Remember that when prompted to upgrade firmware, press &amp;quot;yes&amp;quot;.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve had issues with getting SWO print to work in Keil myself, but it normally works if I open up a JLink Commander and input &amp;quot;swoview &amp;lt;freq in hz&amp;gt;&amp;quot; (normally 4 MHz). Could you try this and see if that prints anything?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>