Hello, Dialog.
In the explanation of memory management explained in Tutorial 6, I do not know if there are places that users can freely use.
According to the previous question, 0x1E000 ~ 0x1EFFF is answered that there is no problem even if it is used, but in programs that can handle SUOTA and security like ble_app_all_in_one, it is used as 0x1E000 ~ saving area of bonding data I will.
app_bond_db.h
#define APP_BOND_DB_DATA_OFFSET (0x1E000)
When using the secondary boot loader and security, is there a FLASH area that I can freely use?
If possible, I want space that is available in units of sectors (4096 bytes).
Device:
Hi sogabe,
Which parts of the flash for custom data can be used depends on the flash that you are using, for example in the case where the 0x1E000 is used in order to store bonding data we are aware that the second image (the one that its stored in the 0x13000 offset) will not co-exist with the bonding data since as the SDK is can support up to a 32K image. If you would like your data not to interfiere between the images you can use the space in the flash that is right under the product header and its relative data of course.
Thansk MT_dialog