RE: RAM adjustment warnings - different addresses provided

MartinBL — Thu, 02 Jun 2016 13:13:06 GMT

Hi,

@Wojtek is pretty much spot on. The two first lines are printed when you call

CHECK_RAM_START_ADDR(CENTRAL_LINK_COUNT,PERIPHERAL_LINK_COUNT);

The function returns RAM start address and size based on

Information about the SoC you are working (some defines in the code and information about amount of RAM found in the FICR registers)
Default information about attribute database.
How many peripheral and central links you plan to use.

The three next lines are printed when you call softdevice_enable(&ble_enable_params);. It returns RAM start address and size based on the information mentioned above, but also based on your BLE parameters. These parameters might be much more specific and might include details that will change the required RAM settings. Hence, when choosing RAM size and start address you should rely on the three last lines. We will try to make it a little clearer in a future SDK release.

RE: RAM adjustment warnings - different addresses provided

Wojtek — Fri, 27 May 2016 09:40:01 GMT

Had the same problem few days ago.

I think this info only counts central/peripheral connections:

RAM START ADDR 0x20004000 should be adjusted to 0x20001FE8
RAM SIZE should be adjusted to 0xE018

this one takes more ble_enable_params (ex. count of vendor specific uuids)

sd_ble_enable: app_ram_base should be adjusted to 0x20002298

So i think the second one is more reliable. But pls some1 from nordic, clarify this.