Hello @Harish_R,
Thanks for reaching out to us once again. That is a good question, in cases where the information in the NVM was lost, the SAF code does not define how the system should react. If you check the following functions, you can see that the reaction will depend on your implementation of the function to read the NVM:
in Std_ReturnType mSel_StorePreservedNvmData(), the real NVM read is done by mSel_NvmWrite():
alejandro_e_0-1758577805593.png
And in the SAF demo you can see that the mSel_NvmWrite() function is left for the developer to implement:
alejandro_e_1-1758577904923.png
You will need to decide the return value of mSel_NvmWrite(), either E_NOT_OK or E_OK. this will define the behavior in Std_ReturnType mSel_StorePreservedNvmData().
Let me know if you have more questions