<?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>IAR I-Jet Debugging Won&amp;#39;t Run</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/6217/iar-i-jet-debugging-won-t-run</link><description>I can&amp;#39;t get a simple application, no soft device, to debug on the nRFDK 10028 board using the I-Jet. I am using the debug in and powering the device from an external power supply at 3.0V. 
 When I start the debug session I get the following in the debug</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 27 Mar 2015 08:28:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/6217/iar-i-jet-debugging-won-t-run" /><item><title>RE: IAR I-Jet Debugging Won't Run</title><link>https://devzone.nordicsemi.com/thread/21762?ContentTypeID=1</link><pubDate>Fri, 27 Mar 2015 08:28:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1c6c9584-492b-48ac-aceb-e368dbc908aa</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;This answer might be helpful to you
&lt;a href="https://devzone.nordicsemi.com/question/94/can-i-user-other-programmers-than-j-link/"&gt;devzone.nordicsemi.com/.../&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: IAR I-Jet Debugging Won't Run</title><link>https://devzone.nordicsemi.com/thread/21761?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2015 06:46:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6217c5b3-1a03-4181-9ecc-5418c6f21e56</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Unfortunately, no one at Nordic uses I-Jet, As I said we make sure that a standard SWD compliant programmer or debugger works with onchip debugger and nordic debugging tools. We expect any other standard SWD compliant programmer or debugger to work the same way.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: IAR I-Jet Debugging Won't Run</title><link>https://devzone.nordicsemi.com/thread/21764?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2015 03:13:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d0a04444-8d42-4487-b110-1ec1ae527a51</guid><dc:creator>WestCoastDaz</dc:creator><description>&lt;p&gt;RK,&lt;/p&gt;
&lt;p&gt;Thank you for taking the time to answer.  An I-JET is a debugger from IAR Systems.  I have looked at the definition file you speak of and did find a mistake in it which I corrected before I posted my question.  The mistake was an obvious one where the end of memory range was at a lower address than the start.&lt;/p&gt;
&lt;p&gt;The think is the description file works with the J-Link lite debugger that is built into the nRFDK.  I have also connected IAR to see if they can support this issue.&lt;/p&gt;
&lt;p&gt;Darren&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: IAR I-Jet Debugging Won't Run</title><link>https://devzone.nordicsemi.com/thread/21763?ContentTypeID=1</link><pubDate>Thu, 26 Mar 2015 01:32:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c6c86817-30bf-4bd7-ade3-70ca9ffe5da3</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;I have no idea what I-Jet is and you probably should seek some support through whoever supports it. However just looking at the error message gives you some ideas doesn&amp;#39;t it?&lt;/p&gt;
&lt;p&gt;Clearly there must be some kind of map/definition of the chip being debugged which I-Jet uses to know what&amp;#39;s RAM, what&amp;#39;s FLASH and where SFRs go (I have no idea what an SFR is, possibly Special Function Register or something like that, unexplained 3-letter acronyms are somewhat useless).&lt;/p&gt;
&lt;p&gt;If you look at the map which it prints out right there for you in the error message you can see that the area where the nrf51 peripherals are is denoted as &amp;#39;RAM&amp;#39;, perhaps that&amp;#39;s ok, as it writable, perhaps it&amp;#39;s not and that should be &amp;#39;Uncached/SFR&amp;#39;. I&amp;#39;m guessing somewhere is a definition file or table being used which isn&amp;#39;t correct, or you have to tell I-Jet what the chip is or where the definition file is or something similar.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: IAR I-Jet Debugging Won't Run</title><link>https://devzone.nordicsemi.com/thread/21760?ContentTypeID=1</link><pubDate>Wed, 25 Mar 2015 23:54:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ac34b39f-467f-48be-a0d5-3c8c16b98d25</guid><dc:creator>WestCoastDaz</dc:creator><description>&lt;p&gt;Aryan,&lt;/p&gt;
&lt;p&gt;So no one at Nordic has experience with using I-Jet debuggers or can help me?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: IAR I-Jet Debugging Won't Run</title><link>https://devzone.nordicsemi.com/thread/21759?ContentTypeID=1</link><pubDate>Wed, 25 Mar 2015 12:44:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1596652d-84e4-4e6a-9aac-66782908507a</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;Hi Darren,&lt;/p&gt;
&lt;p&gt;We have tested the IAR workspace with Segger debugger to make sure that we are inline with debugging standards. We do not use I-Jet for testing here.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>