• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 386 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

LAUNCHXL-CC3235SF: CC3235SF NVS use

Lemon Wang
Prodigy 190 points
Part Number: LAUNCHXL-CC3235SF
Other Parts Discussed in Thread: CC3235SF, CC3235MODSF

Hi  TI engineer

        Now i test nvs func fail.

My test config 、code and log as show

  In ccs NVS config,need config spi flash instance ,but  CC3235SF only one SPI,and this SPI use to conn spi peripheral,and in CCS can't add other SPI. 

Is the nvs fail reason? 

what should i do?

  • 0
    TI__Mastermind 30140 points

    Hi,

    We don't have an example with NVS because the flash is connected to the NWP on the cc3220 launchpad. Do you have another flash connected on SPI 0?

    Instead, we recommend customers use the NWP's ability to access the flash as a filesystem. Click Filesystem here to read more: https://dev.ti.com/tirex/explore/node?node=A__AO6Uh7Oii5BBfYbgEZ9fGg__com.ti.SIMPLELINK_CC32XX_SDK__fc2e6sr__LATEST 

  • 0 in reply to Sabeeh Khan1
    Prodigy 190 points

    Hi  thanks reply

        The SPI0 had conn a meter ic .  I  thought  nvs can operate application flash ,but can't.,beacause must config extern flash .

         Filesystem operate need 250ms when file open,this time is longer。 I need to store dev param,and this operation is sometimes more frequent,So I want to store param fast.

       The CC3235MODSF have 1M on-chip flash,there have example to operate direct? Or  have  other way  to fast store data ?

  • 0 in reply to Lemon Wang
    Guru 79905 points

    Hi,

    Internal XIP flash is not intended for such own storage. Write can be done via drivelib library, but XIP flash it is not intended for fast and frequent write operation. NWP flash is not intended for frequent re-write as well. You idea to use external memory (flash, FRAM, etc.) is correct.

    Jan

  • 0 in reply to Jan D
    Prodigy 190 points

    Hi  Jan

             Thanks reply！

             Our hardware is complete,so I must use internal flash to store. I will limit the erase number.

             How much the CC3235MODSF  internal flash erase number? Is there have example to operate flash or api? I haven't found it yet.

  • +1 in reply to Lemon Wang
    Guru 79905 points

    Hi,

    Usage of execution XIP flash for user data is very bad idea, you should avoid this. From this reasons:

    • TI does not provide number of guaranteed write cycles into XIP flash, because this is not intended usage
    • At ROM bootloader are routines for XIP flash write. ROM bootlaoder is not under your control. That means at some cases is XIP flash erased by ROM bootlaoder. That means you will lost your user content from XIP flash.
    • In case your code (mcuflashimg.bin file) is bigger than 512kB, things will be even more complicated, because XIP flash have two separate banks only.

    There is no official example how to use driverlib for XIP flash writing. Driverlib for XIP flash access you will find at \source\ti\devices\cc32xx\driverlib\flash.h/.c. Some discussion at this topic you can find at e2e forum. Documentation for driverlib you will find at CC3200 SDK (yes, not a CC32xx SDK).

    Jan

  • 0 in reply to Jan D
    Prodigy 190 points

    Hi  thanks reply

         I will consider the method. Thanks again!