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: NVOCMP and NVS as dependencies of BLE5 on CC26XX

Part Number: CC2642R
Other Parts Discussed in Thread: SYSCONFIG

It seems that BLE5 depends of NVOCMP and NVS. I have tried to remove NVOCMP in the simple_peripheral example but I get the following error:

NVOCMP_loadApiPtrsMin simplelink_cc13x2_26x2_sdk_5_20_00_52/source/ti/ble5stack/libraries/cc26x2r1/StackWrapper.a<osal_snv_wrapper.o>

Similarly, I can't remove NVS from syscfg without getting error.

I would like to know if BLE5 really uses NVOCMP and NVS. It could be fine but having NVS flash pages is more or less problematic.

Q1. Are NVS flash pages really used by BLE5?

Q2. Can I use this NVS area for my own means?

Q3. Or can I at least change the address of the NVS area? (By default, it's 0x48000).

  • Hi,

    You may want to refer to the User's Guide section dealing with Non-Volatile Storage Architecture.

    Q1- Yes, the BLE5Stack uses NVS flash storage.

    Q2- Yes. You can either declare a new NVS region or use the NV IDs left for customer (see here). The second option is generally advised as it requires less work and consumes less resources. The first option is mainly suggested for cases where large amount of data is stored or with a different logic (e.g. storage by address and not by ID).

    Q3- The address of the NVS area can be changed using SysConfig.

    I hope these will help,

    Best regards,

  • Thank you. Can I reduce the size of the NVS dedicated to BLE5? It's 0x4000 right now.