<?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>RAM start address determination</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/58994/ram-start-address-determination</link><description>For RAM locations, I&amp;#39;ve looked at the getting started guide that discusses using debugging to find the RAM address. https://devzone.nordicsemi.com/nordic/short-range-guides/b/getting-started/posts/adjustment-of-ram-and-flash-memory 
 
 But, I see in the</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 24 Mar 2020 04:19:03 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/58994/ram-start-address-determination" /><item><title>RE: RAM start address determination</title><link>https://devzone.nordicsemi.com/thread/241259?ContentTypeID=1</link><pubDate>Tue, 24 Mar 2020 04:19:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b32a6092-55ed-4b8d-a8e5-df3f528c8b92</guid><dc:creator>matt.heins</dc:creator><description>&lt;p&gt;I had to port it to a 52840 because there wasn&amp;#39;t enough room on the 52810 to enable logging with the peer manager with the S113 soft device.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RAM start address determination</title><link>https://devzone.nordicsemi.com/thread/239545?ContentTypeID=1</link><pubDate>Thu, 12 Mar 2020 13:37:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b317cc0f-01ff-4f09-ab02-0f3a684723f9</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;The&amp;nbsp;nrf_sdh_ble_default_cfg_set() which is used in all of our BLE examples will give you the RAM requirements, and print in the log if you need to adjust them.&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t know the formula by heart, but these requirements depend on many parameters, mainly: Are you a central or a peripheral? How many central connections do you support, how many peripherals connections do you support, and most importantly, how many Services and characteristics do you have? How big are the sizes of your characteristic values, and so on.&lt;/p&gt;
&lt;p&gt;I believe that the easiest approach is to monitor the nrf_sdh_ble_default_cfg_set() call, and see if you need to apply any changes to your RAM settings.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RAM start address determination</title><link>https://devzone.nordicsemi.com/thread/239410?ContentTypeID=1</link><pubDate>Wed, 11 Mar 2020 20:19:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4c960703-fef9-423b-ab4c-bcd23610a541</guid><dc:creator>Justin</dc:creator><description>&lt;p&gt;Which chip are you using? Also are you using Soft Device? If so which version?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>