https://devzone.nordicsemi.com/f/nordic-q-a/23700/nrf51822-32kb-version-goes-to-0xfffffffeHi, I ran the ble central example code on nrf51822 16KB ram version without any problem. But when I run the same code in nrf51822 32KB version, the program flow goes to 0xFFFFFFFE and stays there forever. In both the chips, in sd_ble_enable, app_ram_baseen-USTelligent Community 13Sun, 23 Jul 2017 20:11:26 GMThttps://devzone.nordicsemi.com/thread/93190?ContentTypeID=1Sun, 23 Jul 2017 20:11:26 GMT137ad170-7792-4731-bb38-c0d22fbe4515:00a46406-1a8a-4ab5-b456-27e3ce45b8bbnordicdev<p>Yes, I flashed the correct softdevice. The problem was for nrf51822 32 KB chip, when peer_manager_init(true) is called, it returns an error code NRF_ERROR_STORAGE_FULL, but the same code works fine when using 16KB chip (I have erased the full chip and flashed the right softdevice before doing this test separately in both the chips). I got the idea from: <a href="https://devzone.nordicsemi.com/question/158610/failed-pm_peers_delete-causes-nrf_error_storage_full-error-from-pm_conn_secure/">devzone.nordicsemi.com/.../</a> Now, I call peer_manager_init(false) instead of true, and the problem has gone away. But, in the future, I would need to use peer_manager_init(true)... Hence, I have created another question in : <a href="https://devzone.nordicsemi.com/question/159324/peer_manager_inittrue-returns-nrf_error_storage_full/">devzone.nordicsemi.com/.../</a> to address just this issue.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/93189?ContentTypeID=1Sun, 23 Jul 2017 11:34:08 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6a001f3b-c3ca-40c6-b5e7-077bcc4f8f94Turbo J<p>Did you flash in the correct softdevice first?</p><div style="clear:both;"></div>