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

Fatal error when using Peer Manager, multiple timers and Queue

Hi all,

I am experimenting an issue similar to this guy --> devzone.nordicsemi.com/.../

But I have my project in two different branchs one using Peer manager and multiple timers, and one using Peer Manager and Queue, both working perfectly.

When I merge one on each other I got fatal error after call

err_code = pm_init();
APP_ERROR_CHECK(err_code);

err code 255,

would it be something related to RAM size or ROM size?

Used FLASH: 106KB out of 512KB (20%)
Used RAM: 9088 bytes out of 64KB (13%)

I am using a NRF52 and SDK13.

Thanks

Parents
  • After you call sd_flash_page_erase() you should wait for NRF_EVT_FLASH_OPERATION_* event back before you execute more operation. Error code 17 means NRF_ERROR_BUSY

    Please read the API documentation before using it.

    Also since the peer manager uses fstorage, you should also use fstorage, you shouldn't use the sd_flash_* directly. You can register your own fstorage user to access flash. We have some example here.

Reply
  • After you call sd_flash_page_erase() you should wait for NRF_EVT_FLASH_OPERATION_* event back before you execute more operation. Error code 17 means NRF_ERROR_BUSY

    Please read the API documentation before using it.

    Also since the peer manager uses fstorage, you should also use fstorage, you shouldn't use the sd_flash_* directly. You can register your own fstorage user to access flash. We have some example here.

Children
No Data
Related