PStorage behaviour changed from sdk v8 to v10

RE: PStorage behaviour changed from sdk v8 to v10

codezork — Sat, 05 Mar 2016 10:30:16 GMT

Accidently I changed the size of the buffer to store to a non-multiple of 4 bytes. It is important to check the result in the storage_callback_handler. It tells you a lot about what you are doing wrong.

RE: PStorage behaviour changed from sdk v8 to v10

Kenneth — Wed, 10 Feb 2016 07:54:55 GMT

I don't understand why this has worked earlier, but if you are in an interrupt callback waiting for a 'pstorage_wait_flag' to be updated from an interrupt with the same priority, then that won't work. It's not possible for an interrupt of same priority to preempt an already running interrupt of same priority.

RE: PStorage behaviour changed from sdk v8 to v10

codezork — Tue, 09 Feb 2016 19:37:12 GMT

Both are default what is APP_PRIORITY_LOW. Pstorage.c and .h didn't change between versions, so it must be s.th. else. I'll come back when I find it. The only thing is the NRF52 switch in nrf.h included in pstorage_platform.h. Thank you for your care.

RE: PStorage behaviour changed from sdk v8 to v10

Kenneth — Mon, 08 Feb 2016 13:35:48 GMT

What interrupt priority is the 'pstorage_wait_flag' updated and what interrupt priority is app_timer using?

RE: PStorage behaviour changed from sdk v8 to v10

codezork — Sat, 06 Feb 2016 00:10:34 GMT

No, I read the migration stuff. This is the start of the module:

#define LOCALIZER_LEN						16
#define MAX_LOCVAL_LEN					10

// storage of metadata
static uint8_t 					pstorage_wait_flag = 0;
static pstorage_block_t 				pstorage_wait_handle = 0;
static pstorage_handle_t       			m_localizerHandle;
static uint8_t						m_localizer[LOCALIZER_LEN];						
static uint32_t					m_result;

APP_TIMER_DEF(m_store_timer_id);	
#define APP_TIMER_PRESCALER             0
#define STORAGE_DELAY			        APP_TIMER_TICKS(100, APP_TIMER_PRESCALER)

I have no more ideas. With the storage clear command I already omitted the waiting on the callback and it clears somehow. But no callback as no event reaches my event loop. I'll try to pump up the pstorage module with printfs to see what happens...

RE: PStorage behaviour changed from sdk v8 to v10

Kenneth — Fri, 05 Feb 2016 11:35:21 GMT

Can it in some way be related to devzone.nordicsemi.com/.../

RE: PStorage behaviour changed from sdk v8 to v10

codezork — Mon, 01 Feb 2016 22:56:01 GMT

The context is a app_timer context according to the following sequence called from a ble_evt dispatched write of an indication service:

uint32_t localizer_new_value(uint8_t* data, uint8_t data_len, ble_loc_t * p_loc)
{
	uint32_t err_code;
	
	memcpy(&m_localizer, data, data_len);
	err_code = app_timer_start(m_store_timer_id, STORAGE_DELAY, p_loc);
	if (err_code != NRF_SUCCESS)
	{
		return err_code;
	}
	return NRF_SUCCESS;
}

And the timer does:

static void store_localizer_handler(void * p_context)
{
	uint32_t err_code;
	err_code = localizer_store();
	if (err_code != NRF_SUCCESS)
	{
		return;
	}
	ble_loc_value_send((ble_loc_t *)p_context);
}

RE: PStorage behaviour changed from sdk v8 to v10

Øyvind Karlsen — Mon, 01 Feb 2016 14:39:57 GMT

There haven't been any changes in the API that should induce this kind of behavior. In what context are you calling your functions?