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.

CC2640: CC2340R5 - Skipping sectors during programming

Part Number: CC2640
Other Parts Discussed in Thread: CC2340R5, UNIFLASH, SYSCONFIG

Hi everyone,

I am working on a CC2340R5 application using NVS memory. I would like to skip NVS sectors while programming the device to retain the data.

Either with CCS or UniFlash, it is not working.

CCS:

Uniflash:

No error, sectors are just not skipped.

I wanted to know if I am doing something wrong or if this feature is not available yet?

Plan B is reading the NVS memory and saving it before programming, which works fine, but it's not the ideal solution.

Regards,

  • Hi,

    Thank you for reaching out.

    I would recommend to first verify if the sectors are erased or not. Based on the screenshot you have provided, I would expect they are erased as you have selected the option "Chip Erase". It seems the option "Chip Erase (Retain sectors specified in CCFG)" should be selected instead. Of course, selecting this option suggests you have properly setup the Erase/Retain sectors in the CCFG using SysConfig:


    Assuming the sectors are not erased (but written), I would check (for sanity) whether the sector numbers should be separate by a coma and a white-space.

    I hope this will help,

    Bets regards,

  • Hi Clément,

    Thanks for your answer, I was definitely missing the SysConfig part!

    Here is my configuration:

      

    As I was fearing it when you suggested using the "Chip Erase (Retain sectors specified in CCFG)" option, I am running into problems I already had when trying to flash the unit either with CCS or UniFlash.

    Uniflash:

    CCS:

    This does not happen when using the "Chip Erase" option.

    Any idea what's going on?

    Regards,

  • Hi,

    I'll have to consult experts in a different team. Please allow me a week to reply back.

    Thanks and regards,

  • Hi,

    Could you please specify the Uniflash and CCS versions used here?

    Our experts also ask whether you have the possibility to use Uniflash's CLI (command line interface). If yes, they suggest to try using the parameter "--mode noConnectFlash" in DSLite command as part of flashing.

    Best regards,

  • Hi Clément,

    Sorry for my late response. I am using CCS version 12.1.0.00007 and Uniflash version 8.2.0.4220.

    I tried using Uniflash's CLI and got similar results with the default --mode flash:

    And with --mode noConnectFlash:

    I generated the package using the Standalone Command Line tool.

    Hope this will help identify the issue.

    Regards,

  • Hi,

    I would suggest to run a quick test using Uniflash 8.3 and CCS 12.3.

    If it still does not help, I would recommend to go with the workaround you have suggested in the first place (i.e. reading the memory before flashing, and then re-write it).

    I have requested the team to look more in the use case described to make sure our support is improved.

    Best regards,