The supplied with the BLE Stack documentation(OSAL API.pdf) obviously is obsolete as there are only information which area of MVMem is used by ZigBee/ RF4CE in the Non-Volatile Memory API , but there is nothing what area/ID’s are used from the BLE stack and what left for Applications! Is there any actualized documentation where can see what is used from BLE stack and what left for the user’s data? In the same document all the ranges are given as “ID’s” from 0x0000 to 0xFFFF – what is the “conversion “ from those “ID’s” and the real physical addresses in the NV memory (ID is equal to the address in the top flash bank or something else)?
The supplied with the BLE Stack documentation(OSAL API.pdf) obviously is obsolete as there are only information which area of MVMem is used by ZigBee/ RF4CE in the Non-Volatile Memory API , but there is nothing what area/ID’s are used from the BLE stack and what left for Applications! Is there any actualized documentation where can see what is used from BLE stack and what left for the user’s data?
In the same document all the ranges are given as “ID’s” from 0x0000 to 0xFFFF – what is the “conversion “ from those “ID’s” and the real physical addresses in the NV memory (ID is equal to the address in the top flash bank or something else)?
In the IAR 7.60 the option to save the Secondary IEEE Address unchanged as it is explained in TI_BLE_Software_Developer's_Guide.pdf doesn’t workL - whenever pass through download/debug from IAR and this information is gone :( . (doesn’t matter with or without checked "Retain unchanged memory" which btw in the new 7.60 version is renamed to "Retain unchanged pages") Any idea how could save top flash bank unchanged Or at least secondary IEEE addr and some my data) when pass through IAR download/debug process?
I couldn’t find also information how exactly works the Append option in the SmartRF flash programmer? Can I append some data at defined by me address or the data/code is added immediately after last used address in the flash memory space?
Thanks
Hello,
We may have to beef up our documentation on NV usage. There are nv ranges in bcomdef.h and macros in osal_snv.c which may help. Usually, when I download IAR built image, it doesn't overwrite the secondary address. When using flash programmer, I do write the address afterwards. One thing to do in development until unique promary address are available is to code the address into your init function.
Br,
-Greg