[Current Time Service not found, device Reset, why?]

RE: [Current Time Service not found, device Reset, why?]

Hung Bui — Wed, 14 Sep 2016 08:43:05 GMT

@Ana: Do you know why you received the PM_EVT_CONN_SEC_SUCCEEDED event twice ?

I assume you received 2 times the PM_EVT_CONN_SEC_SUCCEEDED because the phone updated the encryption key (which is quite rare) . You can use the procedure flag pm_evt.params.conn_sec_succeeded.procedure to distinguish if it's the first encryption (PM_LINK_SECURED_PROCEDURE_BONDING) or it's the updated encryption (PM_LINK_SECURED_PROCEDURE_ENCRYPTION)

Or you can simply use your own flag to mark if it's the first time so you only do service discovery once. Or you can also just ignore the error code busy.

RE: [Current Time Service not found, device Reset, why?]

annapalu — Wed, 14 Sep 2016 07:59:05 GMT

Hi, the question now, is : What is the better moment to starts the db_discovery? Because in my example i use a peer manager ( in the example cts use a device manager). I understand that the problem of reset is: app send two times the event PM_EVT_CONN_SEC_SUCCEEDED, and so the code execute twice the ble_db_discovery_start(), the second time is busy and starts the reset::

RE: [Current Time Service not found, device Reset, why?]

annapalu — Tue, 13 Sep 2016 13:41:11 GMT

Thank you so much. It's very useful,. In understand that is' the db discovery that is busy.Now i must understand i resolve the problem to void that the watchdog starts.

RE: [Current Time Service not found, device Reset, why?]

Hung Bui — Tue, 13 Sep 2016 12:57:37 GMT

You may want to have a look here. You simply need to add the breakpoint inside the app_error_handler() to find out the file name and line and error code. Also checking out what happens after you do service discovery and couldn't find the service you expecting, would it trigger an assertion and then to a reset ?

RE: [Current Time Service not found, device Reset, why?]

annapalu — Tue, 13 Sep 2016 12:48:11 GMT

I see that the same behavior, it's present if run only the ble_cts_service. First time connected and log that the cts is not present, second time reset the board.

RE: [Current Time Service not found, device Reset, why?]

annapalu — Tue, 13 Sep 2016 10:48:02 GMT

Hi hung bui,

i use the example ble_app_gls_s132 and add the cts service, using example the ble_cts_s132. The first one the connection be successful, and the log inform me that the app doesn't have the cts service. If i disconnected and try to connect again the board reset. And i don't understand why, i try to use a breakpoints but they don't help me, if i press F10 to go on inside the code, the board reset,maybe, for the timer that are started!

thanks, Anna

RE: [Current Time Service not found, device Reset, why?]

Hung Bui — Tue, 13 Sep 2016 10:26:45 GMT

@Anna: What exactly profile are you implementing ? You based on our example or you wrote your own ? The chip resets most likely because of an assertion. I would suggest you to add a break point in the app error handler and see what cause assertion, which line, and which error code.