<?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>J-Link lite under Eclipse</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/10833/j-link-lite-under-eclipse</link><description>Hello, 
 I am porting a blinky program to my custom board having nRF51822. The program is compiled under Eclipse (+ GCC) and is downloaded to the board via J-Link Lite. But the program is halted as follows: ...Target halted (PC = 0xFFFFFFFE). I would</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sun, 13 Dec 2015 02:39:43 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/10833/j-link-lite-under-eclipse" /><item><title>RE: J-Link lite under Eclipse</title><link>https://devzone.nordicsemi.com/thread/40502?ContentTypeID=1</link><pubDate>Sun, 13 Dec 2015 02:39:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2b3f6ab7-dee9-4d2f-94cc-97a88fc64ceb</guid><dc:creator>shin</dc:creator><description>&lt;p&gt;Thank you very much again for you additional comment. Best regards.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: J-Link lite under Eclipse</title><link>https://devzone.nordicsemi.com/thread/40501?ContentTypeID=1</link><pubDate>Sun, 13 Dec 2015 02:05:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:283270be-8798-485e-8b15-a594f9ec41ab</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;I told you what the difference is in my answer. There are two possible differences either&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;the Keil version was compiled with the profile for a 16kB chip and the GCC one was compiled with a link map for the 32Kb chip. The 16k version will run on either OR&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Keil puts the stack directly after the last block of allocated memory, which in the case of blinky is very low down, and doesn&amp;#39;t use the rest of the 32Kb because it doesn&amp;#39;t need it, however the GCC linker map always puts the stack at the very end of user memory (which is generally a good idea) so if you tell it you have the wrong amount of RAM, it doesn&amp;#39;t work.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: J-Link lite under Eclipse</title><link>https://devzone.nordicsemi.com/thread/40500?ContentTypeID=1</link><pubDate>Sun, 13 Dec 2015 02:02:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9437277c-cfe9-4369-b753-203008323104</guid><dc:creator>shin</dc:creator><description>&lt;p&gt;Thank you very much for your comment.
My custom board has nrf51822 having 16KB RAM and nrf51422 of PCA10028 has 32KB RAM. I have forgotten the fact. Your comment is correct. The blinky program compiled by GCC runs well on the custom board now.
It looks that there is difference between the executable object by Keil and the one by GCC on how to treat RAM. If you know it, could you please let me know it?
Thank you very much again for your advice. Best regards.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: J-Link lite under Eclipse</title><link>https://devzone.nordicsemi.com/thread/40503?ContentTypeID=1</link><pubDate>Sat, 12 Dec 2015 14:20:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e3c62021-2423-4dd5-a059-7460c0cd4f35</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Do you have a different version of the nrf51822 on your custom board, one with a different amount of RAM in it than on the PCA10028? If you do then you need to change the linker map file when you&amp;#39;re using GCC so that the stack stays within the actual RAM on the chip. That&amp;#39;s exactly the error I&amp;#39;d expect to see if you&amp;#39;re trying to initialize the stack where there is no RAM. The GCC linker files tend to put the stack at the top of all available RAM, so if you get that wrong, the program won&amp;#39;t run. Either Keil doesn&amp;#39;t do that, or you have specified a smaller-RAM version of the chip when you&amp;#39;re compiling in Keil so the image works on either board.&lt;/p&gt;
&lt;p&gt;And J-Link Lite has GDB server and all the other capabilities of the other JLinks, a Segger is a Segger is a Segger ,they all work about the same.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>