nRF51 persistant storage of characteristics data

[Johan Dahlgren]

What is the best way to store the values of my attribute data? With my current code, from the tutorials, the read, write and notify works fine. But I need to store the data in a more persistant way so the data is availble after a restart.

Have looked at some examples an how to use the PManager and Flash Manager but I don´t understand how to use it with my attribute data.

Kindly regards, Johan Dahlgren

[endnode]

Sorry but now you are mixing two things: BLE link and exchange of data over higher layers like GATT and local persistent data storage inside the FW. They have nothing in common except that you need to somehow store the data while BLE stack is in operation (if it is the case) and that you also inside your FW logic use these persistent data inside GATT protocols.

Now which part you are asking in your last question? If persistent storage then it should be clear from my description. If you ask how the data get transported over BLE GATT then it's completely different story (and explained in many tutorials and Q&S on this forum). If you ask how to use these persistently stored data on GATT Server side to initialize GATT structures (like GATT Characteristic values) then the answer is obvious: the exact same ways as any other (non-persistent) data!;)))

[Johan Dahlgren]

Sorry if i´m unclear :) But what I´m asking, or trying to, is where and how I get the data when it changes. That is, when my writable attribute recevies a change of it´s value. Then I can store it in some storage if my choise, but that is another storyjust as you said. Right now I just need to understand and figure out how to catch the data :) And that I can´t find here on the forum, probably searching the wrong way...

[endnode]

Oh yes, you will get events for any BLE related action from the stack. See sequence diagrams here (you probably want to handle GATTS Write Command without Authorization but if your counterpart doesn't have specified which GATT Client methods can be used then you might need to handle more of Write events including Queued ones).

[Johan Dahlgren]

Thank you! That was the push in the right direction! :)