CCS/LAUNCHXL-CC1352R1: Question for ZED Examples. Does these use NVS External driver?

Hi Ryan,

Thank you for your great response. The link that you gave really helped me understand on how NVS Drivers being used on zstack examples.

By the way I have one last question, as I dig into the use of NVS Driver in zed example, I am curious on where the values of NVOCMP_NVS_INDEX being derived? By default it has a value of 0. Does this mean it is using internal flash, and if I set it to 1, will it use external flash?

Regards,

Jonathan

Hi Jonathan,

No, NVOCMP_NVS_INDEX controls which NVS_config indice is used to initialize the NVS.  External flash is only purposed for OTA download images and does not pertain to the NV flash memory operation of Z-Stack.  I understand that this is confusing given the acronyms and naming conventions used.

Regards,
Ryan

Hi Ryan, 

Sorry for the late response, I just got back on this task of mine to solve the issue with NVS _Flash.

I am a little bit confused, because in nvs_external examples, the first parameter of the nvs_open() is the name of instance of nvs external flash in the sysconfig.

bool flash_open(void)
{
    if (!isOpen)
    {
        nvsHandle = NVS_open(Board_NVSEXTERNAL, &nvsParams);
        if (nvsHandle != NULL)
        {
            isOpen = true;
            // Also read the region's attribute
            NVS_getAttrs(nvsHandle, &regionAttrs);
        }
    }

    return (isOpen);
}

But how come that in zstack example, it was used in different way? instead of using nvs external/internal instances from sysconfig in its first parameter, it uses NVOCMP_NVS_INDEX instead?

Hi Jonathan,

This is just the name of the NVS instance, as described in SysConfig: This name is declared in the generated ti_drivers_config.h file so applications can reference this instance symbolically. Additionally, this name is used to declare an 'extern const' which allows libraries to define symbolic names for required driver configurations without needing to rebuild library source files. The 'const' identifier is declared as the same name with a _CONSTsuffix. The name can be set to any globally unique name that is also a valid C/C++ identifier.

Regardless, either are defined as zero to be used as index for NVS_open

/*!
 *  @brief  Open an NVS region for reading and writing.
 *
 *  @pre    NVS_init() was called.
 *
 *  @param  index         Index in the #NVS_Config table of the region
 *                        to manage.
 *
 *  @param  params        Pointer to a parameter region.  If NULL, default
 *                        parameter values will be used.
 *
 *  @return  A non-zero handle on success, else NULL.
 */
extern NVS_Handle NVS_open(uint_least8_t index, NVS_Params *params);

Regards,
Ryan