Discovery service dosen't work always

RE: Discovery service dosen't work always

ToTo — Tue, 07 Mar 2017 09:30:09 GMT

Yah, that is what i meant. Thank you.

RE: Discovery service dosen't work always

Hung Bui — Tue, 07 Mar 2017 09:27:49 GMT

What did you mean by "data manager" , you meant "device manager" ? "Device manager" needed only if you want to do DFU with bonding forwarded. If not you don't need device manager.

RE: Discovery service dosen't work always

ToTo — Mon, 06 Mar 2017 16:17:51 GMT

Thanks for your help, All I did to avoid this problem is to added

				case BLE_GATTS_EVT_SYS_ATTR_MISSING:
					// No system attributes have been stored.
					sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0, 0);
			 
			break;

to the function :

static void on_ble_evt(ble_evt_t * p_ble_evt)

and now it is ok.

another question, if you can help, is the data manager mandatory for the DFU ?

RE: Discovery service dosen't work always

Hung Bui — Mon, 06 Mar 2017 15:12:06 GMT

Yes you have to "handle the event BLE_GATTS_EVT_SYS_ATTR_MISSING and call that function under it". But this is only applied if you don't store bond information and system attribute belong to that central. If you store bond information and want to re-init the system attribute (for example remember and automatically allow notification when the same central re-connect) you need to use the correct data instead of NULL. Other than that you can use NULL. Please look for BLE_GATTS_EVT_SYS_ATTR_MISSING event in the ble_app_uart to see how we handled it.

RE: Discovery service dosen't work always

ToTo — Mon, 06 Mar 2017 14:57:55 GMT

You are right, it is because of that. I find that that event is handled under the dm_manager event handler. So can you please tell me how can I avoid that? I mean , I should use sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0, 0); in the main and it is ok ? or i have tohandle the event BLE_GATTS_EVT_SYS_ATTR_MISSING and call that function under it ?

RE: Discovery service dosen't work always

Hung Bui — Mon, 06 Mar 2017 13:47:23 GMT

If you don't use devicemanager, have you handled BLE_GATTS_EVT_SYS_ATTR_MISSING event ? This is needed in the case that the CCCD is not initialized. Usually you can call err_code = sd_ble_gatts_sys_attr_set(m_conn_handle, NULL, 0, 0); Please follow what we do in the ble_app_uart example.

If you already handled that even could be that the device crashed, could you check if there if it still run after that ? If it didn't crash, could you tell which disconnected reason it is ? (inside DISCONNECTED event check for the reason inside p_ble_evt)

RE: Discovery service dosen't work always

ToTo — Mon, 06 Mar 2017 13:20:53 GMT

Yah , i do have pstorage init in other function when i comment this one. I edited my question, you can see the error in the image attached

RE: Discovery service dosen't work always

Hung Bui — Mon, 06 Mar 2017 12:16:52 GMT

Hi,

What do you see when discovery service doesn't work ? Which error ? Note that if you use pstorage you need to call pstorage_init(). If you remove vMain_iInitDeviceManager_Exe then the pstorage_init() is not called.