cant access flash when bootloader is present

[p_t]

i am trying to use flash to store and read data. I am able to do that when there is only softdevice and application. but when there is bootloader code get stuck. softdevice using is s130 2.0.1. i used keil to generate hex . softdevice and bootloader(buttonless) hex are loaded with nrfgo then app is loaded using nrfconnect(dfu). to give command to flash data given by uart(pin 0.1 and p0.2) . ble_flash.c function i am using to access flash.

NRF_NVMC->CONFIG = (NVMC_CONFIG_WEN_Een << NVMC_CONFIG_WEN_Pos);

this is line used before erasing the page. i had put two led turn on instructions before and after this line and came to the conclusion that after this line execute code seem stuck somewhere.

cant figure out why?. because without bootloader ,code works.

[Vidar Berg]

Are you performing the flash operations before you enable the softdevice? Note that it is not possible to access NVMC directly when the softdevice is enabled. Also, what flash pages are you erasing? 

[p_t]

i am performing flash access after enabling softdevice. i have read that direct flash access is resticted when softdevice is active.but is there any way to do that then.. should i have to disable softdevice before performing flash access?

[p_t]

(NRF_UICR->BOOTLOADERADDR/NRF_FICR->CODEPAGESIZE) - 2

This page i am trying to erase....

I read in bootloader about application reserve data too which data doesnt get erased while ble dfu.

I have set  it to this,

#define DFU_APP_DATA_RESERVED               CODE_PAGE_SIZE * 100

[Vidar Berg]

I see that you made a new thread: https://devzone.nordicsemi.com/f/nordic-q-a/48051/cant-access-flash-memory-after-ota. Lets continue the discussion there.

[p_t]

old thread was made when i was was working on non-connectible application and new thread is which i am working on now, its connectible NUS ble service . I will make you the example to test.

sd_flash_page_erase()  generate event which should be processed by sd_evt_get().

so add that code suggested here,

https://devzone.nordicsemi.com/f/nordic-q-a/48074/sd_flash_page_erase-error-code-success-but-flash-erase-fail/190421#190421

err_code_ = sd_flash_page_erase(erase_page);

while (1)
{
sd_evt_get (&evt);
if (evt == NRF_EVT_FLASH_OPERATION_SUCCESS || evt == NRF_EVT_FLASH_OPERATION_ERROR)
break;
}

i never get the event ,

[Vidar Berg]

The events may get consumed by the Softdevice Handler before being read in your main loop. You should register a callback for SoC events at the end of ble_stack_init instead.

/**@brief Function for dispatching a system event to interested modules.
 *
 * @details This function is called from the System event interrupt handler after a system
 *          event has been received.
 *
 * @param[in] sys_evt  System stack event.
 */
static void sys_evt_dispatch(uint32_t sys_evt)
{
    //TODO: check sys_evt
}

/**@brief Function for initializing the BLE stack.
 *
 * @details Initializes the SoftDevice and the BLE event interrupt.
 */
static void ble_stack_init(void)
{
    ...

    // Register with the SoftDevice handler module for SoC events.
    err_code = softdevice_sys_evt_handler_set(sys_evt_dispatch);
    APP_ERROR_CHECK(err_code);
}

[p_t]

added this in ble_stack_init

err_code = softdevice_sys_evt_handler_set(sys_evt_dispatch);
APP_ERROR_CHECK(err_code);

then,

static void sys_evt_dispatch(uint32_t sys_evt)
{
if(sys_evt == NRF_EVT_FLASH_OPERATION_SUCCESS)
{
printf("\r\nerased\r\n");
}
else if(sys_evt == NRF_EVT_FLASH_OPERATION_ERROR)
{
printf("\r\nerror\r\n");
}

}

when erase execute,

err_code_ = sd_flash_page_erase(NRF_FICR->CODESIZE - 20);

i get, 

err_code = NRF_SUCCESS  and  event of NRF_EVT_FLASH_OPERATION_SUCCESS

but at   

err_code = sd_flash_write((uint32_t *)(NRF_FICR->CODESIZE) - 20,data_32_1,2);

i get,

err_code = NRF_ERROR_FORBIDDEN and no event in sys_evt_dispatch

why i get forbidden error while writing and not in erase?

for source i am using  

uint32_t const data_32_1[6] = {'@','@','@','@','@','@'};

[p_t]

ok ...so in the sd_flash write it was memory address instead of page number.

err_code = sd_flash_write((uint32_t *)((NRF_FICR->CODESIZE - 20)*NRF_FICR->CODEPAGESIZE),data_32_1,2);

with this i get , err_code = NRF_SUCCESS and  NRF_EVT_FLASH_OPERATION_SUCCESS in sys_evt_dispatch

with pointers ..able to read data direclty from address...

[p_t]

it works with bootloader also  ...

i am now doing sd_flash_write while i am connected via NUS service...its  woking now...but do you suggest to do this way?

[Vidar Berg]

It's ok to use the sd flash API directly. Although I prefer using fstorage/fds modules on top of the SD flash API when I have flash data needs to be updated frequently.