UICR writing issue

[IMRAN]

Hi team,

I am using nRF5_SDK_15.3.0_59ac345 and nrf52832 controller. I am using nRF5_SDK_15.3.0_59ac345/examples/ble_peripheral/ble_app_uart example code and the hardware contains a button on long-press we need to write button status in the UICR register for the future purpose. 

I disabled softdevice with nrf_sdh_disable_request(); but I am stuck there itself I am not able to get what is happening over there. can you please help me out with this problem. the below code snippet I am using. if possible can you please send me an example snippet.

void on_button_press_write()

{

nrf_sdh_disable_request();

uint32_t sleep_state_read = 0;

uint32_t sleep_state_write = 1;

NRF_NVMC->CONFIG = NVMC_CONFIG_WEN_Wen << NVMC_CONFIG_WEN_Pos;

nrf_delay_ms(100);

while (NRF_NVMC->READY == NVMC_READY_READY_Busy){}

nrf_delay_ms(100);

*(uint32_t *)0x100010E8 = sleep_state_write ;

nrf_delay_ms(100);

NRF_NVMC->CONFIG = NVMC_CONFIG_WEN_Ren << NVMC_CONFIG_WEN_Pos;

nrf_delay_ms(100);

while (NRF_NVMC->READY == NVMC_READY_READY_Busy){}

nrf_delay_ms(100);

sleep_state_read = *(uint32_t *)0x100010E8;

sd_nvic_SystemReset();

}

[tesc]

Hi,

Is the call to nrf_sdh_disable_request() returning any status code? Have you done a debug session to see where the application gets stuck?

Please note that the UICR is intended for configuration of the device, and not for repeated writes during normal operation. The way flash works is you can erase a full flash page to all bits being 1, and then you can write to individual addresses in flash by flipping bits that are 1 into 0. This means if you write several times to the same flash location in a row, any bit set to a 0 at any point will stay a 0. Any bit set to 0 will stay 0 until you erase the full page.

If you want to store a piece of information in flash, and be able to change that data, a better option is to use the Flash Data Storage (FDS) library from the SDK. With FDS, data is written to flash as "records", an update is writing a new record (and invalidating the old one by setting a field in the header of the record to all 0), and a read gets you back the valid record. That way you do not need a full flash erase/write cycle every time you write one record, and you do not need to rewrite the whole flash page every time you need to update a value. FDS does not use the UICR page.

Regards,
Terje

[IMRAN]

Hi, Tesc 

Thanks for the response. I will use FDS in my application.

please close this issue.

Thank you.