<?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>Debugging nRF51 with Eclipse - Console shows binary garbage</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/10852/debugging-nrf51-with-eclipse---console-shows-binary-garbage</link><description>Hi, 
 i am using Eclipse &amp;#39;Mars&amp;#39; and Segger V5.10c to debug some of the SDK examples. The Eclipse command line shows only binary garbage. How can I get the garbage readable? 
 I used this guide to setup my working environment. Afterwards I able to compile</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 22 Dec 2015 15:33:47 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/10852/debugging-nrf51-with-eclipse---console-shows-binary-garbage" /><item><title>RE: Debugging nRF51 with Eclipse - Console shows binary garbage</title><link>https://devzone.nordicsemi.com/thread/40587?ContentTypeID=1</link><pubDate>Tue, 22 Dec 2015 15:33:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4536a905-0473-4db8-9e50-f97befc34743</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi again Florian,&lt;/p&gt;
&lt;p&gt;Sorry for late response, it&amp;#39;s been busy lately.&lt;/p&gt;
&lt;p&gt;I noticed that you have Semihosting and SWV in the Console log, in my case and in the tutorial it was JLinkGDBServerCL.exe, maybe it was because you are using Linux.&lt;/p&gt;
&lt;p&gt;But what if you try to uncheck the check box for &amp;quot;Allocate console for semihosting and SWO&amp;quot; ?
And were you able to stop at a break point ? Have you made sure you installed Cross compiler, J-link Debugging and Packs ? as described in &amp;quot;Setting up Eclipse the first time&amp;quot; ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Debugging nRF51 with Eclipse - Console shows binary garbage</title><link>https://devzone.nordicsemi.com/thread/40586?ContentTypeID=1</link><pubDate>Wed, 16 Dec 2015 11:05:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:433d1dec-e292-41d4-8430-a781e9df69ac</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Florian,&lt;/p&gt;
&lt;p&gt;We haven&amp;#39;t seen this before.
Please make sure that GDB server path is correct (you can try to put the absolute address, instead of ${jlink_path..)
Please let me know the gcc version you are using. And please update Segger Jlink to latest version.&lt;/p&gt;
&lt;p&gt;One thing you can try is to run GDB server separately and use the GDB client console arm-none-eabi-gdb.exe to debug. This way you don&amp;#39;t need Eclipse and can rule out if the issue is with Eclipse. You can have a look &lt;a href="http://mcuoneclipse.com/2015/03/25/command-line-programming-and-debugging-with-gdb/"&gt;here&lt;/a&gt; to know how to debug with arm-none-eabi-gdb.exe and Segger GDB server.
You can use .axf file instead of the .elf file.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Debugging nRF51 with Eclipse - Console shows binary garbage</title><link>https://devzone.nordicsemi.com/thread/40585?ContentTypeID=1</link><pubDate>Mon, 14 Dec 2015 13:31:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:989af7bd-c432-456a-a2ad-9fc12e6eccee</guid><dc:creator>Hung Bui</dc:creator><description>&lt;p&gt;Hi Florian,&lt;/p&gt;
&lt;p&gt;Could you update the question with a screen shot ? Also with some more description on your steps of testing.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>