Get disconnection immediately after sending CONNECT_REQ to an Ammicom BLE module from a central

[Manuel Kwong]

Hi, I am designing a  central using nRF51422, SDK V11, S130V2.0.0, modifying the central example to connect to a Ammicom BLE module of a product. After the CONNECT_REQ is sent from the central, it is disconnected with the reason 0x1E or 0x3E.

Attached is the sniffer log of 2 cases :

1. 0003 nrf3.pcapng, at time 38.776922, after it sends out one CONNECT_REQ, it send out immediately one empty PDU packet. But the peripheral just return a empty packet and the central is disconnected. The reason is 0x1E

2. 0003 nrf5 active.pcapng, at time 39.014299, after it sends out one CONNECT_REQ, it sends out 6 empty PDU packets, and then stop. Reason is 0x3E.

Cannot figure what is wrong and then how can I make it connected.

I attached another log, that is using nRF Connect in Android to connect to the peripheral, that is 0005 and.pcapng

the sniffer used is Wireshack V2.6.0 and PCA10028 board

Please kindly help.

0004 and.zip0003 nrf5 active.zip0003 nrf3.zip

[Einar Thorsrud]

Hi,

The 0x1E disconnect reason is BLE_HCI_STATUS_CODE_INVALID_LMP_PARAMETERS.The peripheral device sends an invalid packet with LLID 0x00 in 0003 nrf3.pcapng (#2283), which is reserved for future use and thus not valid. The SoftDevice will disconnect on invalid peer behavior. This should be fixed in the peer device.