About the "BLE_GAP_EVT_DISCONNECTED" event nRF52832

[KURODA ELECTRIC]

Hello.

After pairing with a tablet or computer, if you leave it for a few seconds without operating it

I wrote out the cause of the disconnection by debugging.

"Error 34 (0x22): GATT CONN LMP TIMEOUT"

What are the possible causes and countermeasures?

[KURODA ELECTRIC]

Einar san

Thank you very much for your help.

≫Android version are you using?

Answer os ver. for tablets and Bluetooth Ver.

Android 7.0

Bluetooth 4.0

 

Above, thank you.

[Einar Thorsrud]

Hi,

I see. Can I ask you which specific tabled model you are using as well? Also, I am very interested to know if you are able to reproduce this issue with other devices, or if it is only that specific model?

Br,

Einar

[KURODA ELECTRIC]

Einar san

We become indebted to.

I recognized that the table model is the model number of the tablet, so
I will answer as follows.

Model: PC-TE507 JAW

Also, since it was reproduced on a Windows 10 notebook PC,
I will send you the log.
No3754: Pairing
No4646: Disconnect

Disconnect_Win10.pcapng


We have another question.
nRF Connect v3.6.1 --I am writing software using Programmer.
Is it possible to get and display "CRC" or "checksum"?
I would like to use it at the time of production to check whether the software can be written normally.

I'm sorry, but please tell me.

[Einar Thorsrud]

Hi,

The sniffer trace with the Windows 10 master shows that the computer disconnects two times first at #3802, then at #4546. In both cases the disconnect reason is 0x13 (remote user terminated connection), which in itself is not an error. Did you get an error on the nRF side in this case as well?

Can you share your code which causes this behavior? Is it possible to reproduce this on a DK?

Regarding programming there is no support for calculating and displaying a checksum of the flash of using the programmer app in the programmer app. The closest you get with Nordic tools is the --verify option of nrfjprog, where you must supply a hex file and the flash of the target is compared with the hex file.

Einar

[KURODA ELECTRIC]

Einar san

We become indebted to.
Thank you for your contact.

For 0x13 disconnection
I understand that it is not an error in itself.

If you check it again,
BLE_GAP_EVT_DISCONNECTED occurred in Reason22.
This phenomenon is caused by connecting another company's application on our board and tablet.
It is occurring. (Not reproduced in DK)

We will send you the following, so please give us your opinion.

1. 1. BLEControl.c source code
(Excerpt so as not to include product information)
2. 2. BLEControl_log.txt Soft log (disconnection occurred at L53)
3. 3. Disconnect.pcapng Wireshark packet capture (disconnection occurred in No3592)

When the source code L50 is enabled, the above phenomenon does not occur.

Thank you fDisconnect_log.zipor your cooperation.