<?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>Memory regions of nRF52 linker script</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/10749/memory-regions-of-nrf52-linker-script</link><description>I&amp;#39;m faced with a curious problem. 
 The examples of nRF52 SDK 0.9.2 have linker sciprt like this: 
 /* Linker script to configure memory regions. */

SEARCH_DIR(.)
GROUP(-lgcc -lc -lnosys)

MEMORY
{
 FLASH (rx) : ORIGIN = 0x0, LENGTH = 0x80000</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 09 Dec 2015 12:16:49 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/10749/memory-regions-of-nrf52-linker-script" /><item><title>RE: Memory regions of nRF52 linker script</title><link>https://devzone.nordicsemi.com/thread/40161?ContentTypeID=1</link><pubDate>Wed, 09 Dec 2015 12:16:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d99d89f9-6e7d-4626-824d-1b1d81c2ac71</guid><dc:creator>monpetit</dc:creator><description>&lt;p&gt;I see. Thank you. =)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Memory regions of nRF52 linker script</title><link>https://devzone.nordicsemi.com/thread/40160?ContentTypeID=1</link><pubDate>Wed, 09 Dec 2015 12:13:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e9d367d-5179-4a31-9655-8b32dd016c55</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;If you have the &amp;quot;engineering B&amp;quot; of nRF52832 (the PCA10040 DK, and not the nRF52-PreviewKit PCA10036), then you can safely expand the RAM area to 64K.&lt;/p&gt;
&lt;p&gt;The first engineering sample &amp;quot;A&amp;quot; had an issue where one 32K chunk was located at a different area:
&lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.nrf52832.errata.v1.0.0/anomaly_832_34.html#anomaly_832_34"&gt;infocenter.nordicsemi.com/.../anomaly_832_34.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;It still has 64K of RAM, but it&amp;#39;s not located at the address it was supposed to be. This has been fixed in Engineering B.&lt;/p&gt;
&lt;p&gt;Cheers,
Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>