FDS Problems in SDK12.1

RE: FDS Problems in SDK12.1

robinvice — Wed, 12 Jul 2017 20:49:43 GMT

OK, Hung Bui, you solved it. sys_evt_dispatch() wasn't calling fs_sys_event_handler(sys_evt). Once I added that, it started working. Thanks for your valuable help.

RE: FDS Problems in SDK12.1

Hung Bui — Mon, 10 Jul 2017 12:19:29 GMT

Hi Robin,

The loop to wait for the write_flag to be set is needed. Note that the write_flag should only be set inside the callback handler you registered, in this case my_fds_evt_handler().

Also make sure this fs_sys_event_handler(sys_evt); is called inside sys_evt_dispatch() so that fstorage can track the callback from the softdevice.

I attached here a project that I write to 2 records instead of one. It worked fine (SDKv12.1).

ble_app_proximity - TestFDS.zip

RE: FDS Problems in SDK12.1

robinvice — Sat, 08 Jul 2017 00:26:14 GMT

I was able to see the header being written only by commenting out the wait that appeared after the call to the write function (as shown below):

    		err_code = fds_test_write();
		APP_ERROR_CHECK(err_code);
		NRF_LOG_INFO("fds_test_write() err_code = %ld\r\n", err_code);	
		//wait until the write is finished. 
//		while (write_flag==0)
//		{
//			write_flag = 1;
//		}

With the while commented out, the error codes returned by the following are all zero:

	err_code = fds_test_init();
	err_code = fds_test_find_and_delete();
	err_code = fds_test_write();
	err_code = fds_read();

When uncommented and allowed to run, the while loop is infinite. The fds_evt_t named p_fds_evt passed to my_fds_evt_handler() contains an id of FDS_EVT_WRITE the first time through. The second time through, it contains FDS_EVT_GC. There are no more calls to it after that, so the write flag never gets set.

RE: FDS Problems in SDK12.1

robinvice — Fri, 07 Jul 2017 16:44:34 GMT

There's a comment at the end of the write_execute() function that says there won't be a callback. I don't know why there isn't a callback, and I don't know how the other members of the switch statement would ever execute without it.

// An operation has either completed or failed. It may have failed because fstorage
// ran out of memory, or because the user tried to delete a record which did not exist.
if (ret != FDS_OP_EXECUTING)
{
    // There won't be another callback for this operation, so update the page offset now.
    page_offsets_update(p_page, p_op->write.header.tl.length_words);
}

return ret;

}

Perhaps p_op remains in the queue, but with its .step value incremented? Can you help me understand this part?

RE: FDS Problems in SDK12.1

Hung Bui — Fri, 07 Jul 2017 14:07:36 GMT

Hi Robin,

I'm not quite sure what the problem you are having ?

Were you able to queue any write after fds_test_write(); ? Note that you need to wait for the callback (in this case my_fds_evt_handler() ) to be sure that the data is written to flash.

If you step through the code, it will crash at any Softdevice API call, because the softdevice stops working when you stepping in the code.