How to verify SDK data and application in NCS CONNECT SDK v1.9.1?

[hiteshk014]

Hi,

We are using NCS Connect SDK v1.9.1 with nRF52833. 

We wanted to verify the application and SDK data region. Can you please suggest ways to verify. 

[Amanda Hsieh]

Hi, 

What application and SDK data would you verify?

May I know more detail about your application?

Regards,
Amanda

[vim_nordic]

Hi AmandaH, 

Our Requirement is to validate the whole SDK area. Is SDK partition data is valid or got corrupted before initializing any application module?

Are we handling this validation in SDK already? If yes, where and how?

if No, how we can handle this?

Thanks

Vimal

[Amanda Hsieh]

Hi, 

Do you mean the verification running on the chip? If so, we think MCUBOOT can do some integrity checks before starting the application. If the image is not valid, it should not boot

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/mcuboot/design.html#integrity-check

-Amanda

[vim_nordic]

Hi AmandaH, 

I am wanted to verify the "storage_partiontion" which is storing the SDK data like provisioning/un-provisioning, sequence number, IV index, RPL messages etc. on device bootup not the image. 

Thanks 

Vimal

[Amanda Hsieh]

Hi, 

From Non-Volatile Storage (NVS):

During initialization NVS will verify the data stored in flash, if it encounters an error it will ignore any data with missing/incorrect metadata.

Is this what you are looking for?

From the note in the Settings page: 

As of Zephyr release 2.1 the recommended backend for non-filesystem storage is NVS. 

-Amanda