SoftDevice s332 v2.0.0 appears to hang on connection w/Motorola Edge 50

RE: SoftDevice s332 v2.0.0 appears to hang on connection w/Motorola Edge 50

grantrudd — Wed, 27 Nov 2024 16:58:44 GMT

Hi Vidar,

Thanks for the reply. Updating the softdevice is a possibility for us. I'll discuss this with out team and we will reach of if we need further support.

Thanks,

Grant

RE: SoftDevice s332 v2.0.0 appears to hang on connection w/Motorola Edge 50

Vidar Berg — Wed, 27 Nov 2024 09:14:58 GMT

Hi Grant,

Unfortunately, I can confirm that this is a bug in the softdevice. It is correct behavior that it responds with LL_UNKNOWN to the LL_CHANNEL_REPORTING_IND from the phone since it does not implement this feature, but it is not supposed to terminate the link afterward. Is it an option for you to update to a newer Softdevice through DFU? Channel reporting is not a feature which can be disabled in the Android app so I'm afraid there is not other workaround for this interoperability issue.

Vidar

RE: SoftDevice s332 v2.0.0 appears to hang on connection w/Motorola Edge 50

Vidar Berg — Fri, 22 Nov 2024 17:02:53 GMT

Hi Grant,

Thanks for confirming. It seems the issue might be related to the LL_CHANNEL_REPORTING_IND procedure (shown as an unknown control opcode in the WS trace) initiated by the phone. The SoftDevice correctly responds with LL_UNKNOWN since it does not support this procedure, which was introduced in Bluetooth v5.3. But the problem is that the Softdevice terminates the link after sending this response. I will confirm the details with R&D on Monday.

Vidar

RE: SoftDevice s332 v2.0.0 appears to hang on connection w/Motorola Edge 50

grantrudd — Fri, 22 Nov 2024 16:55:59 GMT

Hi Vidar,

Thanks for taking a look! I am getting `BLE_HCI_DIFFERENT_TRANSACTION_COLLISION 0x2A` in the disconnect event.

Grant

RE: SoftDevice s332 v2.0.0 appears to hang on connection w/Motorola Edge 50

Vidar Berg — Fri, 22 Nov 2024 14:12:34 GMT

Hello,

Thank you for providing the sniffer captures. I reviewed them but didn’t notice any obvious specification violations from either side, except that the peripheral (S332) stops responding to the central. Could you please check the disconnect reason reported by the peripheral?

Best regards,

Vidar

RE: SoftDevice s332 v2.0.0 appears to hang on connection w/Motorola Edge 50

grantrudd — Fri, 22 Nov 2024 00:17:03 GMT

I tried this with the ble_app_hrs example using the s332 softdevice and observed similar behavior. The connection made it further this time, but it still appears that the softdevice is hanging in the sample application.

devzone.nordicsemi.com/.../edge_5F00_50_5F00_ble_5F00_app_5F00_hrs.pcapng