• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 51 subscribers
  • Views 145 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.

Original question:

CC2652R7: Remove NPI Interface from BLE Peripheral Example

CC2652R7: Remove NVS interface from BLE Peripheral example

Madhusudhan K
Prodigy 200 points
Part Number: CC2652R7
Other Parts Discussed in Thread: SYSCONFIG

Hi,

I'm using BLE peripheral example and I have removed the NVS interface from the sysconfig and all related code. But still I'm getting below error while building. I also see that the NV folder is getting created in Release/Drivers folder. Please help me on this. 

undefined first referenced
symbol in file
--------- ----------------
NVS_config C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc26x2x7.a<NVS.om4f>
NVS_count C:/ti/simplelink_cc13xx_cc26xx_sdk_5_40_00_40/source/ti/drivers/lib/ticlang/m4f/drivers_cc26x2x7.a<NVS.om4f>

Regards,

Madhusudhan

  • 0
    TI__Mastermind 25810 points

    Hey Madhusudhan,

    Taking a step back, I do want to highlight one thing from the Bluetooth LE perspective. Please read the following related post: https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1028703/cc2642r-how-to-remove-nvs_config-and-nvs_count-references-while-building-peripheral-firmware .

    Below are my initial thoughts, this isn't something we recommend or have tried, but I will do my best to help.

    On to your question, it looks like the provided libraries have references to the NVS driver. I'm not sure fully removing references to this will be possible without rebuilding these libraries to remove the dependencies. You could unlink the library reference, but you'll have to resolve other errors associated with doing so. You may run into roadblocks if the necessary drivers you require are not made available in the SDK (and only made available in the provided library). This could also impact your memory consumption since you are no longer referencing items that are stored in ROM and placing it in Flash. Again, I'm not entirely sure this will be possible, but you can try.

    At a high level, what is your primary motivation to remove NVS?

  • 0 in reply to Ammar N
    Prodigy 200 points

    Hi Ammar,

    The post was very helpful. We too are not using NVS driver in our project so thought of removing it. But now understood the situation, thanks for your help.