This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nrf51822 32KB version goes to 0xFFFFFFFE

Hi, 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_base is equal to ram_start (= 0x200022D8: obviously, this is the same number entered in IRAM in project options). The softdevice_enable returns with NRF_SUCCESS.

Following are my configs in project options/Target IROM1: 0x1B000 size: 0x25000 IRAM1: 0x200022D8; size: 0x4FC0

Parents
  • 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: devzone.nordicsemi.com/.../ 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 : devzone.nordicsemi.com/.../ to address just this issue.

Reply
  • 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: devzone.nordicsemi.com/.../ 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 : devzone.nordicsemi.com/.../ to address just this issue.

Children
No Data
Related