<?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>nRF52840 RAM adjustment causes hard lock</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/85481/nrf52840-ram-adjustment-causes-hard-lock</link><description>Hi all, 
 I&amp;#39;m experiencing a weird behaviour when adding NUS BLE profile to a standard BLE Peripheral HRS example. 
 The code compiles fine without any error or warning, and it&amp;#39;s expected that the RAM starting point should be adjusted once SoftDevice</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 07 Mar 2022 13:05:20 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/85481/nrf52840-ram-adjustment-causes-hard-lock" /><item><title>RE: nRF52840 RAM adjustment causes hard lock</title><link>https://devzone.nordicsemi.com/thread/356600?ContentTypeID=1</link><pubDate>Mon, 07 Mar 2022 13:05:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a7aac3bb-edd4-4348-bc77-476a810942ad</guid><dc:creator>Kenneth</dc:creator><description>&lt;p&gt;Not seen anyting like this before, what happens if you go back to the default example without any modifications and only change to&amp;nbsp;RAM_START=0x20002be0 and&amp;nbsp;RAM_SIZE=0x3d420? (You should get a warning, but it should work.)&lt;/p&gt;
&lt;p&gt;Maybe double check the nRF5 SDK release_notes.txt and check if you are using the correct toolchain for that release? Also, make sure you are using the latest nRF5 SDK.&lt;/p&gt;
&lt;p&gt;Kenneth&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>