Configuration of gzp_dynamic_pairing project for device in segger embedded studio environment 3

[astella]

12_12_2020.zip

To the kind attention of Nordic support team,

after some months I gave a look to the segger toolchain configuration for the device host example using the secured gazell library you kindly provide.

I uploaded in the zip file the device and host projects. If it is feasible and not much trouble for you, could you please give a look at them? Do you also think

they are working? Please let me know if you experience any trouble in compiling them, should it be the case I'll provide the exact files needed inside the folder.

Right now, those folders are inside C:Nordic SDK (15.2) examples proprietary_rf gzll gzp_dynamic_payring in my local machine.

I uploaded the device in an PCA10040 standard board - the master project has been uploaded in a custom nRF52840 board (even if the folder refers to a PCA10040).

Thank you for your precious advises

[Kenneth]

Unfortunately we don't have resources to review code, but if you have specific issues we can help to debug. A quick glance at the code it looks you have control over the api and usage.

Best regards,
Kenneth

[astella]

Thank you, encypted communication seems to be ok. But I noticed that gzp_erase_pairing_data is commented in the code. Whenever the comment is cancelled

void gzp_erase_pairing_data(void)
{
// Erase database flash page so that it can be later written to.
nrf_nvmc_page_erase((uint32_t)database);

}

database has got a strange address (0x6F64)

even if /*static const*/ const uint32_t database[GZP_DEVICE_PARAMS_STORAGE_SIZE / 4] __attribute__((at(GZP_PARAMS_DB_ADR)))

and I'm experimenting putting #define GZP_PARAMS_STORAGE_ADR 0x0009000  in nrf_gzp_config.h and        <ProgramSection alignment="4" load="No"  name=".GZP_PARAMS_STORAGE_ADR" start="0x09000" size="4096" /> in flash_placement.xml 

[astella]

I cancelled the gzp_erase_pairing_data comment.

Then in nrf_gzp_device.c I had to put static  const uint32_t database[GZP_DEVICE_PARAMS_STORAGE_SIZE / 4] __attribute__((at(0x9000/*GZP_PARAMS_DB_ADR*/)))

#define GZP_NV_STORAGE_DISABLE to avoid parameters restore

Then void gzp_erase_pairing_data(void)
{
// Erase database flash page so that it can be later written to.
nrf_nvmc_page_erase((uint32_t)0x9000/*database*/);

}

and     <ProgramSection alignment="4" load="No"  name=".GZP_PARAMS_STORAGE_ADR" start="0x09000" size="4096" /> in flash_placement.xml.

It seems that flash is erased at 0x9000 correctly.