I'm in trouble because I can't get my expected Logs in WireShark with nRF51822.

[kawamoto]

I'm in trouble because I can't get my expected Logs in WireShark with nRF51822.

[Enviroment]
・I use "User Guide v2.2" and I installed according to this document.
・My PC is Win10.
・Paring way is "Just Work"
・The distance from tablet(OS = android) and BLE device is less than 5cm.
(nRF51822 is located between tablet and BLE machine, 3 devices are very near )

[Case in Detail]
Tablet and BLE device can be connected each other.
And tablet can get the data from the BLE device.
But I cannot get my expected logs.

In this process, the follwing ATT logs should be seen in WireShark.
Only No1 Log can be seen, there are no another (No2 ～No6) logs.
(1) Master Read Request ← only this log can be seen.
(2) Slave Read Response
(3) Master Write Request
(4) Slave Write Response
(5) Master Indicate Request
(6) Slave Indicate Response

[sample Log In WireShark]
I'll show you a part of logs below.
in Line 4 , this Master Log stands for "Read Request".

<WireShark Log>
Master_0x1b5a5142 Control Opcode: LL_VERSION_IND
Slave_0x1b5a5142 Control Opcode: LL_FEATURE_RSP
Master_0x1b5a5142 Control Opcode: LL_CONNECTION_UPDATE_REQ
Master_0x1b5a5142 Sent Read By Group Type Request, GATT Primary Service Declaration, Handles: 0x0001..0xffff
Slave_0x1b5a5142 Rcvd Exchange MTU Request, Client Rx MTU: 240
Slave_0x1b5a5142 Rcvd Exchange MTU Request, Client Rx MTU: 240
Slave_0x1b5a5142 Rcvd Exchange MTU Request, Client Rx MTU: 240
Slave_0x1b5a5142 Rcvd Exchange MTU Request, Client Rx MTU: 240
Slave_0x1b5a5142 L2CAP Fragment Start
Slave_0x1b5a5142 L2CAP Fragment Start
Master_0x1b5a5142 Control Opcode: Unknown

[Question]
(1) Why can't I get the Log ?
I have read many website about this issue, but I cannot get any information to solve.
please show me reason and solution.

If you need more information don't hesitate asking to me.
I'll send you information and Logs and so on you need.

(2) In fact, I have one more trouble related with this log problem.
As is often the case with me, I cannot get any ATT Protocol logs even Master Read Request Log.
there are many "bad MIC" logs.
Why is it occured ?

I've tried the same way as I had gotton the log including "Master Read Request".
In most case, it's occured.
Sometime, I've been able to get the "Master Read Request" Log.


<WireShark Log>
Slave_0x129360ad Control Opcode: LL_VERSION_IND
Master_0x129360ad Control Opcode: LL_FEATURE_REQ
Master_0x129360ad Control Opcode: LL_VERSION_IND
Slave_0x129360ad Control Opcode: LL_FEATURE_RSP
Slave_0x129360ad Control Opcode: LL_ENC_RSP
Slave_0x129360ad Control Opcode: LL_ENC_RSP
Slave_0x129360ad Control Opcode: LL_START_ENC_REQ
Slave_0x129360ad Encrypted packet decrypted incorrectly (bad MIC)
Slave_0x129360ad Encrypted packet decrypted incorrectly (bad MIC)
Slave_0x129360ad Encrypted packet decrypted incorrectly (bad MIC)
Slave_0x129360ad Encrypted packet decrypted incorrectly (bad MIC)
Slave_0x129360ad Encrypted packet decrypted incorrectly (bad MIC)
Slave_0x129360ad Encrypted packet decrypted incorrectly (bad MIC)
Slave_0x129360ad Encrypted packet decrypted incorrectly (bad MIC)
Master_0x129360ad Encrypted packet decrypted incorrectly (bad MIC)
Master_0x129360ad Encrypted packet decrypted incorrectly (bad MIC)
Slave_0x129360ad Encrypted packet decrypted incorrectly (bad MIC)

[Finally]
I'm really appreciate for your reading my question.
I hope your reply.
I'm looking forward to get the expected Logs.

[Sigurd]

Hi,

kawamoto said:

(1) Why can't I get the Log ?

What do you mean? You are showing parts of the log in the <WireShark Log> snippet, so you are getting the log ?

kawamoto said:

(2) In fact, I have one more trouble related with this log problem.

You start to get bad MIC after the link is encrypted (LL_START_ENC_REQ). The sniffer need to be present when the peers are bonded the first time. From the sniffer user guide, "The Sniffer needs to have sniffed the pairing procedure if the devices are already paired. ". Delete the pairing bonds on both the devices, and then start the sniffer before you pair/bond again.

[kawamoto]

Thank you for your quick reply.
I'm so sorry that my English is too difficult for you to understand.
Can I add information about Question No 1 ?

About Question No1, what I'd like to say is "Why Can't I get following (1)～(6）Logs ?".
As the Tablet can get BLE data from BLE device, I think following (1)～(6）Logs should be seen.

>Only (1) Log can be seen, there are no another (No2 ～No6) logs.
>(1) Master Read Request ← only this log can be seen.
>(2) Slave Read Response
>(3) Master Write Request
>(4) Slave Write Response
>(5) Master Indicate Request
>(6) Slave Indicate Response

I doubt that I cannnot get above (2)～(6）Logs because of my setting failtures.
I'd like to get above (2)～(6）Logs.

[kawamoto]

20190607_ReadRequest.zip

[kawamoto]

I've uploaded the WireShark Log just now.
sorry too late.

The uploaded logs have been captured
when I got the BLE data from BLE device with the tablet.

>    (1) Master Read Request ← only this log can be seen.
The uploaded logs include "Master Request Read".
(It is line-No 20 in WireShark Log)

If there are any shortages about the uploaded log, please don't hesitate to ask me.
Then I'll capture and upload logs.

[kawamoto]

8400.20190607_ReadRequest.zip

[kawamoto]

By the way, I have one problem that I've not be able to install.
It is according to the document(nRF_Sniffer_UG_v2.2.pdf).
It is about Jlink which is written in Page5. 
(2-2 Install firmware with segger Jlink)

When I've ran Jlink.exe , the following error message has appeared.
 "Connecting to J-Link via USB...FAILED: Cannot connect to J-Link via USB."
Please refer to the attatchment(I've got the hard copies) about detail.

The firmware of my sniffer(nrf51822) is "ver2".
Is it concerned with the problem
 that I cannot get expected (2) ～（6） logs？

[kawamoto]

Page5_2-2_Install-firmware-with-segger-J-link.pdf