pstorage handle never called

RE: pstorage handle never called

kimbring2 — Sun, 22 Nov 2015 04:32:19 GMT

I solve it by adding the 100ms delay after the store function. It works well to me.

pstorage_store(&block_0_handle, source_data_0, 16, 0); 
nrf_delay_ms(100);
while(pstorage_wait_flag) { 
    //simple_uart_putstring((const uint8_t *)" \n\r Wait \n\r");
    //nrf_delay_ms(10);
}

Please don't forget to register the sys_evt_dispatch() to the ble_stack_init(). I spent a lot of my time to find my fault.

static void sys_evt_dispatch(uint32_t sys_evt) {
    pstorage_sys_event_handler(sys_evt);
}

RE: pstorage handle never called

joc — Sat, 20 Jun 2015 16:36:50 GMT

I searched a lot. Only your solution works for me. Thank you! Also, nordic should make these pstorage functions use scheduler by default, maybe.

RE: pstorage handle never called

Alev — Mon, 20 Apr 2015 13:35:55 GMT

Had the same problem. Just have solved it by moving erase/store calls from the event context to the main loop. So, as I see, one should not use this time-costs functions in the BLE event handler or other interrupt context. Maybe will useful for somebody.

RE: pstorage handle never called

damien5606 — Wed, 11 Mar 2015 17:59:35 GMT

ok I see, thank you I'll follow your advices !

RE: pstorage handle never called

Hung Bui — Wed, 11 Mar 2015 11:20:04 GMT

@Damien: As you can find in our examples in the SDK v7.x+. We have a check for pending flash operation before starting advertising. The reason for that is we may miss a connect request when we are doing a flash operation (and advertise). So my suggestion is to stop advertising when you do a flash operation and start it back again after that.

RE: pstorage handle never called

damien5606 — Wed, 11 Mar 2015 07:32:10 GMT

Hi, thank you for your answer !

I actually solved my problem a few days ago, At this time I didn't know that the time to store data to the flash is approximately 23ms, so it takes to much time to do it when we are in communication with a central. So I store the data after the communication, while I'm advertising (with an advertising interval>23ms) and it works !

Regards, Damien

RE: pstorage handle never called

Hung Bui — Mon, 09 Mar 2015 17:00:13 GMT

Hi Damien,

Could you try and test this example.

I modified the ble_app_template and added some simple pstorage operation such as erase, write and read. You can find the 16 byte data written into flash is readout and added in the advertising packet (scan response packet) and also the LED1 will blink when the pstorage call back is called.

Please notice that you need to added pstorage_sys_event_handler() in sys_evt_dispatch(). Also you need to align the address of the input data to 32bit word address.

The example is from SDK v7.2 and tested on PCA100028 board, S110 v7.1

ble_app_template - pstorage.zip

RE: pstorage handle never called

Kyu — Mon, 02 Mar 2015 12:22:03 GMT

I debugged this again. it doesn't call cmd_process() because m_cmd_queue.flash_access is not false.

RE: pstorage handle never called

damien5606 — Fri, 27 Feb 2015 08:27:04 GMT

Bill, yes it's a NRF_SUCCESS but it doesn't mean that the data is stored and that you can read it, you've to wait a while, when the storage is finish it should call the handler (but in my case it doesn't), then you're sure that the operation is done. asma, yes I guess we can just add delays, but I don't know if it's the best way to do it, I really don't know why pstorage_store doesn't call the handler Anyway, thank you for your anwsers !

RE: pstorage handle never called

asma — Fri, 27 Feb 2015 07:18:51 GMT

I also have same problem. To resolve it i just add for loop like this

pstorage_block_identifier_get(&handle, 0, &block_0_handle);
pstorage_clear(&block_0_handle, 16);                     //Clear 48 bytes		
pstorage_wait_handle = block_0_handle.block_id;    //Specify which pstorage handle to wait for
pstorage_wait_flag = 1;                        //Set the wait flag. Cleared in the example_cb_handler

		//Store data to block. Wait for the last store operation to finish before reading out the data.
pstorage_store(&block_0_handle, source_data_0, 16, 0);     //Write to flash, only one block is allowed for each pstorage_store command
//while(pstorage_wait_flag) { power_manage(); }              //Sleep until store operation is finished.
for(i=0; i < 1000;i++)
	{
	}

its just a work around.

RE: pstorage handle never called

Bill Siever — Fri, 27 Feb 2015 02:34:09 GMT

Is the return value on pstorage_store NRF_SUCCESS?

RE: pstorage handle never called

damien5606 — Fri, 27 Feb 2015 02:04:09 GMT

Hello!

When I initialize my led I turn it on, "nrf_gpio_pin_set(LED_4);" turn my led off, So my led turn off when pstorage failed to initialize or when the handler is called successfully, both of those events never happens.

Like you Kyu, pstorage_load function call the handler but not pstorage_store... I need the handler call to be sure that the store operation is done...

RE: pstorage handle never called

Bill Siever — Fri, 27 Feb 2015 00:42:47 GMT

I'm assuming that "set" of LED_4 turns it on. Is that correct?

The code above seems to set LED_4 when there is an error. Have you tried using a debugger (or commenting out one of the two places that turn it on) to identify where/why it comes on?

Also, the example_cb_handler above sets LED_4 as well. There doesn't appear to be any place that clears it. So there isn't anything to distinguish an error from successful completion.

RE: pstorage handle never called

Kyu — Thu, 26 Feb 2015 23:43:57 GMT

me too.

I enter the pstorage callback handler when I do pstorage_load function. However, if I do pstorage_store and clear function, it is not call the call_back_handler.