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.

CCS/CC2564MODA: CC2564MODA - Problem adding NVS to existing Bluetopia Sample project

Part Number: CC2564MODA
Other Parts Discussed in Thread: MSP432P401R, , CC256XMS432BTBLESW

Tool/software: Code Composer Studio

Hello there,

I recently start using the MSP432P401R LaunchPad  with the BOOST-CC2564MODA plug-in module.

I'm testing some of the examples (SPPLEDemo for instance) provided by the Bluetooth Stack (CC256XMS432BTBLESW). The first "problem" I found was that the previous paired devices are not stored after power off the module. So, I started planning to develop some code using the NVS API already provided by the SimpleLink SDK. And there I reached a blocking problem.

I'm trying to include the TI Driver for NVS  in the Bluetopia Sample Project "SPPLEDemo". But I got error when building.

What I did was:

- Added Simplelink SDK in Project properties > General > Products

- Include NVS.h header the SPPLDemo.c file and made functions calling methods like NVS_init(), NVS_read(...), etc...

But when I build, I encounter 5 errors:

Can someone tell me why this happens and how to fix it?

Can I use Simplelink SDK in Bluetopia ?

Thank you very much,

João Freire

  • It appears, you may need to add the NVS library and the library path in your linker declarations..

  • Hi Hari. Thank you for answering.
    What do you mean with NVS library? Is there any library file for NVS (and every other Simplelink driver)?
  • Since, your linker complaining about missing symbols. I suggested you may be missing corresponding libraries during linking.. Are, you taking this NVS header file from TI-RTOS distribution?

    Anyways, i suggest you take a look at below thread for storing and retrieving link keys for pairing..

  • Hi Hari,

    Not from TI-RTOS distribution but from NoRTOS. I took my "inspiration" from the following example available in SimpleLink examples:

    And for the project I'm editing, I'm just using the following linked resources and code:

    And my testing code is this right now: 

    Do you see anything missing?

    Thank you.

    Best regards,


  • João,

    Is it necessary that you use NVS to achieve your goal? As Hari mentioned above, there is a way to store link keys only using the driverlib included with the existing SDK without having to bring Simplelink into the mix.

    The general idea of this solution is that the struct LinkKeyInfo stores all the information from links in RAM, and thus does not retain it upon power cycling. However, the solution suggests that you write this data to flash using the built in driverlib functions, and upon startup copy these values from flash back to RAM.

  • Hi DFZ,

    Well, that thread will certainly help to achive this. Thank you very much, Hari and DFZ
    No, I really don't care if its NVS or Flash (But just to be clear, I see them as the same thing.. Maybe just different library names or structure of functions? If it's Flash, it should be in Non-volatile Flash, correct? ). As I explained, I want to save the necessary information needed for pairing after power cycling.
    By the way, what is the purpose of having driverlib and Simulink drivers? I'm a new user of TI development tools..

    Thank you.