Central device is disconnected automatically from "Chromecast Remote" after a few seconds

[ChoonghanLee]

HI , All

I am debugging connection of "Chromecast Remote Controller" with ble_app_interactive.

I am trying to implement ble_app_interactive on nrf52832 as my application.

I followed the next procedures.

1. Change "Chromecast Remote" to Pairing mode.

 1.  Open Serial Terminal and  I type commands like these.

    uart_cli: ~$  scan on

    uart_cli: ~$  devices

uart_cli:~$ connect D8:71:4D:3E:77:C2
<info> app: CENTRAL: Connecting...
Connected to address: D8 71 4D 3E 77 C2
<info> app: CENTRAL: Connected, handle: 0.
<info> app: Data length updated to 128 bytes.
<info> app: Data length updated to 128 bytes.
Current MTU: 247
MTU changed successfully
<info> app: CENTRAL: Disconnected, handle: 0, reason: 0x5
uart_cli:~$

I don't know why to disconnect after a few seconds .

Please help me about this issue.

I have attached a Wireshark file .

chromecast_connect_error_2.pcapng

Thank you.

 

   

[Eugene Yu]

Hi,

It seems to failed pairing.

Have you used "pair" command on CLI?

To use HID service on Mobile OS requires to support the pairing method so, the Google RC may require the same feature on it.

Try with the pair command again.

[ChoonghanLee]

Thank you for your kind answer.

I did think so .

So I tried  testing of  "pair command"  in several times like these.

------------------------------------------->

uart_cli:~$ scan on
Scan started
<info> app: Scanning
uart_cli:~$ connect D8:71:4D:3E:77:C2
<info> app: CENTRAL: Connecting...
Connected to address: D8 71 4D 3E 77 C2
<info> app: CENTRAL: Connected, handle: 0.
<info> app: Data length updated to 128 bytes.
<info> app: Data length updated to 128 bytes.
Current MTU: 247
MTU changed successfully
uart_cli:~$ pair LESC D8:71:4D:3E:77:C2
Start pairing
<info> app: CENTRAL: Disconnected, handle: 0, reason: 0x5
<info> peer_manager_handler: Connection security failed: role: Central, conn_handle: 0x0, procedure: Bonding, error: 4352
uart_cli:~$ scan on
Scan started
<info> app: Scanning
uart_cli:~$ connect D8:71:4D:3E:77:C2
<info> app: CENTRAL: Connecting...
Connected to address: D8 71 4D 3E 77 C2
<info> app: CENTRAL: Connected, handle: 0.
<info> app: Data length updated to 128 bytes.
<info> app: Data length updated to 128 bytes.
Current MTU: 247
MTU changed successfully
<info> app: CENTRAL: Disconnected, handle: 0, reason: 0x5
uart_cli:~$ pair LEGACY D8:71:4D:3E:77:C2
Invalid device address
uart_cli:~$ scan on
Scan started
<info> app: Scanning
uart_cli:~$ connect D8:71:4D:3E:77:C2
<info> app: CENTRAL: Connecting...
Connected to address: D8 71 4D 3E 77 C2
<info> app: CENTRAL: Connected, handle: 0.
<info> app: Data length updated to 128 bytes.
<info> app: Data length updated to 128 bytes.
Current MTU: 247
MTU changed successfully
uart_cli:~$ pair LEGACY D8:71:4D:3E:77:C2
Start pairing
<info> app: CENTRAL: Disconnected, handle: 0, reason: 0x5
<info> peer_manager_handler: Connection security failed: role: Central, conn_handle: 0x0, procedure: Bonding, error: 4352

<--------------------------

The Central device  have been disconnected after sending  pair command in every times.

Please explain whether I did correct procedure or not.
or Could you suggest the other way ?

The next image is ble packet image  after receiving CONNECT_IND  when to pair.

I hope your life happy.

[Eugene Yu]

The error code is this.

It seems to the peripheral device disconnects the link before the complete the pairing or encryption.

According to your sniffer log the peripheral device sent a LL_TEMINATE_IND to central before sends a response for authreq.

Can you check the code of Google RC that what things happened on it?

and try to test with some parameter changes such as IO capabilities or clear with bonding information on both RC and DK.

Thanks.