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-CC26X2R1: 2642 After storing the data, re-burn the file and the stored data will be lost.

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: UNIFLASH

Hi Team,

Use osal_snv_write or NVS_write to write data. You can read and write normally under normal use. You can also read out the stored data normally after restarting the device. However, after using the Uniflash tool to burn the bin, the previously recorded data will be lost. The bin file is 352kb. The stored data configuration is as follows picture.

When compiling using IAR compilation software, check the bin generated by Raw binary in output format.

Best Regards,

Galaxy

  • Hi Galaxy,

    There are no holes in a binary image, and since the CCFG is stored in the last page of flash your NV memory is getting overwritten with padding to fill the gap between the application and CCFG.  To avoid this, you can use a hex image which allows for holes in memory or remove the CCFG from being used or built by your project.

    Regards,
    Ryan

  • Hi Ryan,

    Should I move the nv storage address forward? Can it be prevented from being overwritten?

    How to build CCFG?

    Best Regards,

    Galaxy

  • Moving your NV storage address will not affect this outcome.  Your options include:

    • Removing the .ccfg section from being built inside the *.cmd file. 
      • The CCFG need only be programmed once, and you can choose to retain this information on future device flashing
      • You can read the CCFG on a valid device and save the information as a hex/bin file to program in later sessions
    • Skip the NV sectors during program load
      • Uniflash: Settings & Utilities -> Flash Page
      • CCS: Debug Configuration -> Target -> Flash Settings -> Skip Sectors during Program Load

    Regards,
    Ryan