LAUNCHXL-CC3235SF: CC3235SF data saving issue

Hi,

Please read SWRU455 chapter 8 where are described how can be saved data into external SPI flash (sFlash). But be carefully that SPI flash have limited number of write cycles. Often re-writing sFlash will cause failure of this flash.

Jan

Do you recommend using an external flash?

Hi,

External SPI flash chip is mandatory for proper function of CC3235SF devices. This SPI flash is managed by NWP (network co-processor) and is used as storage of system data, web files, and user files. User files you can save using sl_ Filesystem APIs (chapter 8 of SWRU455). But as I said there are limitation of number write cycles.

Your question is not clear what you asking for.

Jan

The user can change the ssid himself, I want to save this last value with every change. In this way, the device will connect to the current location every time it is turned on.

I want to do this with NVS, but when I open NVS in sysconfig, I get an error as in the image.

I haven't tried doing it with NVP. Is there a setting needed in sysconfig for NVP? Also, is there an example about NVP?

Thank you for your interest. 

Hi,

You cant access SPI flash directly (or using NVS driver) . This is prohibited. For saving data into sFlash you need to use sl_ filesystem APIs. Sl_ filesystem APIs are same APIs as other sl_ APIs (e.g. socket) which you are using inside your code. This have nothing to do with Sysconfig. 

Jan

Is there any sample code related to this topic?

Hi,

For example OTA examples use sl_ filesystem APIs or Wi-Fi Secure File System example in SimpleLink academy or just check SWRU455 chapter 8.

Jan

Thank You