weird behavior of pstorage_update function

RE: weird behavior of pstorage_update function

Stefan Birnir Sverrisson — Fri, 21 Oct 2016 13:48:04 GMT

Hi Samo

This is the check in the pstorage_update function that checks the word alignment and potentially throws the NRF_ERROR_INVALID_ADDR error.

if ((!is_word_aligned(p_src))                    || 
    (!is_word_aligned((void *)(uint32_t)offset)) || 
    (!is_word_aligned((uint32_t *)p_dest->block_id)))
{
    return NRF_ERROR_INVALID_ADDR;
}

Is it thrown from this code in the pstorage_update function in pstorage.c file? If so, set breakpoint there and check what is causing it. If not, where is the NRF_ERROR_INVALID_ADDR error thrown?

RE: weird behavior of pstorage_update function

samo — Wed, 19 Oct 2016 11:34:57 GMT

Hi Stefan

As you can see from code above this is not the case (retval = pstorage_update(&block_0_handle, m_mass.histroy_last, 80, 76); ). I do not understand why pstorage_update throws error only if the m_mass.history array is declared among the last variables in ble_mass_t struct otherwise everything works fine.

RE: weird behavior of pstorage_update function

Stefan Birnir Sverrisson — Wed, 19 Oct 2016 11:06:43 GMT

Hi Samo

When using pstorage, you need to have writes/updates word aligned, i.e. 4,8,12,16,... bytes. Perhaps that is causing the address error.

RE: weird behavior of pstorage_update function

samo — Wed, 19 Oct 2016 10:47:42 GMT

Hi Stefan

Thanks for reply. I make this. I used pstorage file from SDK 10. It should be noted that I changed config file as well. Unfortunately, I got the same weird behavior such as presented in my first post. Do you have any other ideal what can be reason for my problem.

Thanks in advance

RE: weird behavior of pstorage_update function

Stefan Birnir Sverrisson — Wed, 19 Oct 2016 09:07:33 GMT

Hi Samo

To start with, I would recommend to update your pstorage module to SDK 9.0.0 or more recent. Pstorage was refactored in SDK 9.0.0. There is a bug in pstorage of SDK 8 and older that can cause race condition and weird behavior. pstorage module is not dependent on any other modules so it should be relatively easy just to copy pstorage.h, pstorage.c and pstorage_platform.h files from SDK 9+ into your current project and start using it.

RE: weird behavior of pstorage_update function

samo — Tue, 18 Oct 2016 10:13:02 GMT

Hi Stefan

thanks for your fast reply. I am using SDK 7.2 together with softdevice S110 7.3.0 (88kB). I tested program on PCA10028 board and custom-made board as well, but I came across the same problem. The compatibility between SDK and SofDevice was checked according to the following instructions infocenter.nordicsemi.com/index.jsp. It is worth mentioning if array is declared in main.c file then everythink works well. Due to this fact I think that the problem is related to location of array.

Thanks for help in advance

RE: weird behavior of pstorage_update function

Stefan Birnir Sverrisson — Tue, 18 Oct 2016 09:52:40 GMT

Hi Samo

Can you share what SDK version you are using, what softdevice and what IC?