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
  • Hi Hung, I noticed I was erasing a whole flash page using sd_flash_page_erase() and after that, I called sd_flash_write() getting err_code 17. is there any alternative to use sd_flash_x when we are using peer manager? could it be a conflict between peer manager and a different method to write the flash?.

    Update:

    if I call only sd_flash_page_erase my program get stuck in somewhere. If I remove the sd_flash_x my program works fine with peer manager. but I still need use erase and write the flash

Reply
  • Hi Hung, I noticed I was erasing a whole flash page using sd_flash_page_erase() and after that, I called sd_flash_write() getting err_code 17. is there any alternative to use sd_flash_x when we are using peer manager? could it be a conflict between peer manager and a different method to write the flash?.

    Update:

    if I call only sd_flash_page_erase my program get stuck in somewhere. If I remove the sd_flash_x my program works fine with peer manager. but I still need use erase and write the flash

Children
No Data
Related