PERSISTENT STORAGE MANAGER - Invalid opcode and result

[Geoffrey OMWAVE]

Hi,

I am having a hard time with the permanent storage.

I got it to work with updating a 24 bytes long struct in a persistant block of 32 bytes. I noticed that the pstorage_ntf_cb callback was called with opcode 0x14 which is not referenced in the Api doc. Is that normal? The result value is NRF_SUCCESS and I have verified by reading after a reset that the value was correctly stored.

I tried increasing the length of my struct to 26 bytes and now the callback is called with opcode 0x10 (still unknown) and the result is NRF_ERROR_INVALID_ADDR.

Any idea on what is happenning here?

Edit: I attached a capture of the call stack which shows that the opcode passed to the CB is 16 (decimal) instead of 5, which is the case in the context of app_notify... This is very strange!

Note: I am using nRF51 SDK v5.2.0.39364

Capture.PNG

[Geoffrey OMWAVE]

I found the answer in the documentation for pstorage_update, on the size parameter: "[in] size Size of data to be stored expressed in bytes. Should be word aligned."

My size parameter was 26, which is not a multiple of 4. Increasing my struct size to 28 did the trick. Shouldn't the pstorage_update function perform this verification?

Also, I still don't understand the opcodes passed to pstorage_ntf_cb.