• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 85 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2642R: Non-Volatile Storage in Flash area

Akihiko Fujinaka
Expert 3005 points
Part Number: CC2642R
Other Parts Discussed in Thread: LAUNCHXL-CC26X2R1, SYSCONFIG

Tool/software:

Hello expert,

Environment  LAUNCHXL-CC26X2R1

SDK:simplelink_cc13xx_cc26xx_SDK_7_40_00_77base

Example:ble5stack(simple_peripheral_oad_onchip)

I have a question about the "Non-Volatile Storage" area in Flash.

Is it possible to implement "osal_snv_read/write" and "NVS_read/write" functions at the same time?

In the environment, the default setting of sysconfig is (Internal Flash) Region Base:0x34000 Region Size:0x4000.

For example, is it possible to set the Region Size to half 0x2000, then the region 0x34000-0x36000 uses OSAL SNV to manage memory,

also  0x36000-0x38000 uses NVS_read/write to read and write non-volatile memory with addressing?

 

Regards,

A.Fujinaka

  • 0
    TI__Guru**** 209677 points

    Hello A.Fujinaka,

    I do not recommend that you reduce the amount of space reserved for the BLE stack within simple_peripheral_oad_onchip CONFIG_NVSINTERNAL.  Instead, I encourage you to consider using customer NV items reserved in the OSAL SNV.  If this is not suitable then you should leave the original CONFIG_NVSINTERNAL and create a new NVS partition inside of SysConfig which has a Region Base 0x32000 and Region Size 0x2000.  You will need to modify CONFIG_NVSINTERNAL1 accordingly to compensate, and there should be enough remaining room for other application expansions in the main flash area.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    TI__Expert 3005 points

    Hello Ryan,

    Thanks for your reply.

    I understood your recommendation,  but could you please answer for 2 questions , by Yes or No?

    1. Is it possible to implement "osal_snv_read/write" and "NVS_read/write" functions at the same time?

    2. Is it possible to set the Region Size to half 0x2000, then the region 0x34000-0x36000 uses OSAL SNV to manage memory,

    also  0x36000-0x38000 uses NVS_read/write to read and write non-volatile memory with addressing?

    Regards,

    A.Fujinaka

  • 0 in reply to Akihiko Fujinaka
    TI__Guru**** 209677 points

    1. Yes, there is no issue with using both in your application especially considering the regions are separately partitioned in SysConfig

    2. No, you should maintain the original OSAL SNV memory area reserved by the example and reducing by half could introduce stack issues.
    Ryan