iPhone won't connect: Unknown Opcode [v14.2 + S132 v5.1.0]

RE: iPhone won't connect: Unknown Opcode [v14.2 + S132 v5.1.0]

SRA — Wed, 24 Jan 2018 03:03:59 GMT

Martin, the migration document was helpful thanks again.

RE: iPhone won't connect: Unknown Opcode [v14.2 + S132 v5.1.0]

MartinBL — Tue, 23 Jan 2018 09:36:02 GMT

Hi @SRA, I think it would be best if you open a new thread regarding Wireshark 2.5.

RE: iPhone won't connect: Unknown Opcode [v14.2 + S132 v5.1.0]

David Edwin — Tue, 23 Jan 2018 08:34:38 GMT

unfortunately the 2.5.x with nRF Sniffer is a bit glitchy for me as well, but it settled down so I can use it, but since it is unreleased it may have other issues. Can you open a separate case for the 2.5.x WS being unstable and add more specifics so it can be re-produced.

RE: iPhone won't connect: Unknown Opcode [v14.2 + S132 v5.1.0]

SRA — Mon, 22 Jan 2018 21:43:08 GMT

Well, Wireshark 2.5 works to open the old capture. Now I'm having trouble getting the sniffer to work with 2.5.

RE: iPhone won't connect: Unknown Opcode [v14.2 + S132 v5.1.0]

SRA — Mon, 22 Jan 2018 17:34:23 GMT

David, thanks! You're right, 2.5 does show it correctly as LL_PHY_REQ, it seems to indicate that Nordic's SD prefers 2Mbit connection, and the iPhone8 seems to hang up on this. I'll follow Nordic's advice as an answer and see, but having (unreleased) Wireshark 2.5 did help.

RE: iPhone won't connect: Unknown Opcode [v14.2 + S132 v5.1.0]

David Edwin — Mon, 22 Jan 2018 14:15:31 GMT

Wireshark 2.5.x should have the Bluetooth 5 opcode changes. so it interprets the opcodes correctly.

RE: iPhone won't connect: Unknown Opcode [v14.2 + S132 v5.1.0]

MartinBL — Mon, 22 Jan 2018 13:49:47 GMT

Hi,

The opcode probably shows up as "Unknown" because Wireshark doesn't support the new BLE 5.0 opcodes yet. If you look at your packet in question you can see that it is a link layer opcode. If you go further and look up the LL opcode 0x16 in the Bluetooth Core Specification you will see that this is the LL_PHY_REQ opcode. Here is a quote from the Spec (BLUETOOTH SPECIFICATION Version 5.0 | Vol 6, Part B, 5.1.10 PHY Update Procedure):

The PHY Update Procedure, when supported, is used to change the transmit or receive PHYs, or both. The procedure can be initiated either on a request by the Host or autonomously by the Link Layer. Either the master or the slave may initiate this procedure at any time after entering the Connection State. Link Layer PHY preferences may change during a connection or between connections and, therefore, they should not be cached by the peer device.

When this procedure is initiated by the master, it sends an LL_PHY_REQ PDU. The slave responds with an LL_PHY_RSP PDU....

In your log it seems like your iPhone 8 sends an LL_PHY_REQ wanting to update the physical layer used in the link. However, you can also see that the nRF52 never responds. Hence, I'm wondering whether your contractor forgot to implement the handling of phy requests in the project. Please refer to the Migration Document for S132 v5.0.0 (no such document exist for v5.1.0) to see how this should be implemented.

The quote from the spec mentions that a phy request might be sent either on a request from the Host or autonomously by the Link Layer, so I suppose your Samsung S8 and iPhone 6 doesn't send any phy requests autonomously and hence there's no problem.

RE: iPhone won't connect: Unknown Opcode [v14.2 + S132 v5.1.0]

SRA — Fri, 19 Jan 2018 16:53:58 GMT

If there is a way to directly attach a file, I don't see it. So here is the whole wireshark cap: s000.tinyupload.com/index.php