https://devzone.nordicsemi.com/f/nordic-q-a/3124/use-of-pre-incrementer-in-flashwrite-exampleHello All, I was looking at the flash writewrite_example and the starting address is defines as: addr = (uint32_t *)(pg_size * pg_num); Later in the code, the example writes to flash using the following function call: flash_word_write(+en-USTelligent Community 13Wed, 23 Jul 2014 14:33:38 GMThttps://devzone.nordicsemi.com/thread/11573?ContentTypeID=1Wed, 23 Jul 2014 14:33:38 GMT137ad170-7792-4731-bb38-c0d22fbe4515:58785523-a826-45ad-a670-81a92d16e2f9Matt Leising<p>pstorage seems to be the better route. Thanks, it would be nice to see a little more documentation and/or examples on it though. Thanks for your help</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/11572?ContentTypeID=1Mon, 14 Jul 2014 20:29:51 GMT137ad170-7792-4731-bb38-c0d22fbe4515:39a4fd48-18a7-4ad1-abbf-de8301ac282dJohn<p>I believe that the code that implemented flash_word_write and related functions for that example stored a &quot;magic number&quot; as the first thing in each flash page written as an error check. So the pre-increment is probably a way of stepping over that.</p> <p>That said, if you are using one of the newer SDKs like 5.2.0, you should consider using the pstorage API to store and recover information from the flash. It hides a lot of the complexity for you.</p> <p>I do not know enough about the bond manager to help you with that question.</p><div style="clear:both;"></div>