Direct connection after disconnect

RE: Direct connection after disconnect

Edvin — Thu, 31 May 2018 07:08:13 GMT

Also when you connect with your phone?

I ask because when I connected with my phone, it printed the passkey, but when the other device tried to connect, it didn't, and I see that it doesn't print the passkey most of the times in your error log. Can you please try to turn off bluetooth on the phone, and see if you still get the fatal errors?

Either way. Did you try to move the m_conn_handle = BLE_CONN_HANDLE_INVALID; to after sd_ble_gap_disconnect()?

BR,

Edvin

RE: Direct connection after disconnect

RYYoo — Thu, 31 May 2018 00:54:58 GMT

Thanks for the reply. I get the same result. But it takes too long to disconnect. It takes about a few minutes ... Is this normal?

RE: Direct connection after disconnect

RYYoo — Thu, 31 May 2018 00:18:54 GMT

Thanks for the reply...! I tried it. But I have the same address for every connection it repeats.

RE: Direct connection after disconnect

RYYoo — Thu, 31 May 2018 00:17:39 GMT

Thanks for the reply. I get the same result. But it takes too long to disconnect. It takes about a few minutes ... Is this normal?

RE: Direct connection after disconnect

Edvin — Wed, 30 May 2018 08:54:56 GMT

Hello RY Yoo,

I tested this in the office, and I see the same behavior as you, I think. Try the following with the ble_app_gls example from SDK12.3.0:

Can you please try to add the following in your "BLE_GAP_EVT_CONNECTED" event:

Change the line:

NRF_LOG_INFO("Connected\r\n");

NRF_LOG_INFO("Connected to %x:%x:%x:%x:%x:%x\r\n", p_ble_evt->evt.gap_evt.params.connected.peer_addr.addr[0],
p_ble_evt->evt.gap_evt.params.connected.peer_addr.addr[1],
p_ble_evt->evt.gap_evt.params.connected.peer_addr.addr[2],
p_ble_evt->evt.gap_evt.params.connected.peer_addr.addr[3],
p_ble_evt->evt.gap_evt.params.connected.peer_addr.addr[4],
p_ble_evt->evt.gap_evt.params.connected.peer_addr.addr[5]);

Then you should be able to see the address of the device that is trying to connect it.

See if it is the same when you repeatedly get the error as it is when you connect with your phone.

In my case, there is something else in the office that is trying to connect to it, and not my iPhone. See if it is the same for you.

If it is another device that is trying to connect, this should still not cause the device to get a fatal error (which it does in the unmodified example).

Go to your preprocessor defines, and add the define: "DEBUG". Also turn off optimization (set it to -O0).

Then add a breakpoint on line 76 in app_error.c (app_error_fault_handler(NRF_FAULT_ID_SDK_ERROR, 0, (uint32_t)(&error_info));)

See if it stops there. It should tell you where it stops, and what err_code it stops because of. I suspect it is in main.c, line number 228 (if main.c is not modified above this). The err_code is 12290 (= 0x3002).

This means that it is trying to disconnect with an invalid connection handle. This is because the m_conn_handle is set to BLE_CONN_HANDLE_INVALID before sd_ble_gap_disconnect(...);

Try to move the line

m_conn_handle = BLE_CONN_HANDLE_INVALID;

to after sd_ble_gap_disconnect(...);

and see if that helps.

Best regards,

Edvin

RE: Direct connection after disconnect

JustinLee — Wed, 30 May 2018 08:16:56 GMT

I think that this is a phone issue.

I checked this issue with iPhone 7 and iPhone 8.

I got same behavior with iPhone 8+.

They are using same version of nRF Connect.

In case of iPhone 8, an iPhone 8 sends GATT negotiation packets continuously.

It means that a phone sends packet to a board, so that connection is kept.

This is not Nordic BLE problem.

Justin

RE: Direct connection after disconnect

JustinLee — Wed, 30 May 2018 06:50:04 GMT

In my side, it's working properly.

An Apple device is iPhone 7.

APP:INFO:Bonds erased!
APP:INFO:GLS Start!
APP:INFO:Fast advertising
APP:INFO:Connected
APP:INFO:Failed to secure connection. Disconnecting.
APP:INFO:Failed to secure connection. Disconnecting.
APP:INFO:Passkey: 008920
APP:INFO:Failed to secure connection. Disconnecting.
APP:INFO:Disconnected
APP:INFO:Disconnected, reason 8
APP:INFO:Fast advertising

And, I think that it's a mobile app problem because an Android device doesn't have any issue.

Please check that out again.

Justin

RE: Direct connection after disconnect

RYYoo — Wed, 30 May 2018 04:41:26 GMT

Sorry..! It was my mistake. I tried again. But not disconnect and It's connected.

APP:INFO:GLS Start!
APP:INFO:Fast advertising
APP:INFO:Connected
APP:INFO:Failed to secure connection. Disconnecting.
APP:INFO:Failed to secure connection. Disconnecting.
APP:INFO:Passkey: 126067
APP:INFO:Failed to secure connection. Disconnecting.

RE: Direct connection after disconnect

JustinLee — Wed, 30 May 2018 04:25:46 GMT

I got same error before modifying.

Did you modify correctly?

"Fatal" message came from APP_ERROR_CHECK(err_code).

I think something wrong.

Please check them out again.

Justin

RE: Direct connection after disconnect

RYYoo — Wed, 30 May 2018 04:20:22 GMT

Thanks. I tried. But the same problem repeats.

APP:INFO:Connected
APP:INFO:Failed to secure connection. Disconnecting.
APP_ERROR:ERROR:Fatal
APP:INFO:GLS Start!
APP:INFO:Fast advertising
APP:INFO:Connected
APP:INFO:Failed to secure connection. Disconnecting.
APP_ERROR:ERROR:Fatal
APP:INFO:GLS Start!
APP:INFO:Fast advertising
APP:INFO:Connected
APP:INFO:Failed to secure connection. Disconnecting.
APP_ERROR:ERROR:Fatal
APP:INFO:GLS Start!
APP:INFO:Fast advertising
APP:INFO:Connected
APP:INFO:Failed to secure connection. Disconnecting.
APP_ERROR:ERROR:Fatal
APP:INFO:GLS Start!
APP:INFO:Fast advertising
APP:INFO:Connected
APP:INFO:Failed to secure connection. Disconnecting.
APP_ERROR:ERROR:Fatal

RE: Direct connection after disconnect

JustinLee — Wed, 30 May 2018 04:11:27 GMT

Hi, RY Yoo.

I don't why this issue is detected with only an Apple device.

Anyways,

In your code, when secure connection failed, gap_disconnect is called.

However, it doesn't need to call.

In GAP, disconnect will happen.

I think that this code influence to Bluetooth code of an Apple device.

So, please do that with below code.

        case PM_EVT_CONN_SEC_FAILED:
        {
            NRF_LOG_INFO("Failed to secure connection. Disconnecting.\r\n");
//m_conn_handle = BLE_CONN_HANDLE_INVALID;
//err_code = sd_ble_gap_disconnect(p_evt->conn_handle,
// BLE_HCI_REMOTE_USER_TERMINATED_CONNECTION);
//APP_ERROR_CHECK(err_code);

} break;

Justin

RE: Direct connection after disconnect

RYYoo — Wed, 30 May 2018 02:52:08 GMT

Thank you for answer. Please understand that I am inexperienced in English...
The same problem happens in the GLS example. Android is normal and only appears on the iPhone. (I checked an iPhone 5, iPhone 8 with an Apple App(nRF Connect))

You can check in the following order.

1. After entering the passkey, connect and disconnect normally. (In this case, after disconnect , it normally advertises)

2. bond erase in device (keep the phone's bond information intact)
- In this case, you need to modify the GLS example code slightly.
- In my case, I modified the [peer_manager_init(erase_bonds);] in the main door to [peer_manager_init(true);],
downloaded it again and bond erased it.

3. Then, if you make a connection, repeat the connection and disconnect. This is my log.

APP:INFO:Failed to secure connection. Disconnecting.
APP:INFO:Disconnected
APP:INFO:Fast advertising
APP:INFO:Connected
APP:INFO:Failed to secure connection. Disconnecting.
APP:INFO:Disconnected
APP:INFO:Fast advertising
APP:INFO:Connected
APP:INFO:Failed to secure connection. Disconnecting.
APP:INFO:Disconnected
APP:INFO:Fast advertising
APP:INFO:Connected
APP:INFO:Failed to secure connection. Disconnecting.
APP:INFO:Disconnected
APP:INFO:Fast advertising
APP:INFO:Connected
APP:INFO:Failed to secure connection. Disconnecting.
APP:INFO:Disconnected
APP:INFO:Fast advertising

RE: Direct connection after disconnect

JustinLee — Wed, 30 May 2018 00:04:10 GMT

Hi RY Yoo,

Could you please upload whole project for your problem?

I can't compile with only main.c you attached due to you modified several functions.

And, please let me know about below questions.

1. How to check your problem?

With nRF Connect Apps or something else?

Please describe in detail.

2. Were this problem also detected with an Andrond App(nRF Connect) if you used nRF Connect App for an Apple?

When I checked this issue with GLS example, I could not detect this issue.

I checked an Apple device and an Android device both.

Justin