For got to add that the dongle is running C:\Program Files (x86)\Cypress\CySmart\1.3\dongle\CY5677\BLE_4_2_Dongle_CySmart_256K_psoc.hex
1. Are you seeing this issues on nRF52833-DK device only or on Cypress PSoC BLE devices also? If you have not tested it, can you please test once? You can test with PSoC 4 BLE Find me code example.
2. Thank you for attaching the ellysis air log. If possible, can you please attach CySmart app log also?
I think the logs attached do not match with the statements in the doc. Please confirm that the logs are correct as this capture is only for 11 seconds, but the doc mentions nRF restarting ADV after 40 s?
My apologies for taking so long to respond, I've been fighting another fire that consumed all of my spare cycles.
The CySmart App shows a different issue; a quick disconnect; 0x2a - BLE_HCI_DIFFERNT_TRANSACTION_COLLISION. I pair on the first connection attempt, but following attempts disconnect almost imminently:
[00:54:21.050,781] <debug> nrf_ble_gatt: Requesting to update ATT MTU to 128 bytes on connection 0x0.
[00:54:21.050,781] <debug> nrf_ble_gatt: Updating data length to 132 on connection 0x0.
[00:54:21.050,781] <info> app: BLE_GAP_EVT_CONNECTED
[00:54:21.050,781] <debug> app: conn_handle 0
[00:54:21.050,781] <debug> app: resolved 0
[00:54:21.050,781] <debug> app: addr_type 0
[00:54:21.050,781] <debug> app: peer_addr 0x00-A0-50-D0-61-51
[00:54:21.050,781] <debug> app: min_conn_interval 7 * 1.25ms
[00:54:21.050,781] <debug> app: max_conn_interval 7 * 1.25ms
[00:54:21.050,781] <debug> app: slave_latency 0
[00:54:21.050,781] <debug> app: conn_sup_timeout 10 * 10ms
[00:54:21.052,734] <info> app: PM_EVT_CONN_SEC_PARAMS_REQ
[00:54:21.071,289] <debug> nrf_ble_gatt: ATT MTU updated to 128 bytes on connection 0x0 (response).
[00:54:21.071,289] <info> app: Data len is set to 0x7D(125)
[00:54:21.071,289] <info> app: ATT MTU exchange completed. central 128 peripheral 128
[00:54:21.071,289] <debug> app: BLE_GATTC_EVT_EXCHANGE_MTU_RSP
[00:54:21.098,632] <info> app: BLE_GAP_EVT_DISCONNECTED, reason 0x2A
I've attached new logs and sniffer capture in CySmart2.zip.
When using our own SonicBlue application, a C# Windows application that uses the CySmart Library, we see the LMP Response Timeout 40s after connecting.
We doesn't seem to have any issues when connecting from SonicBlue(CySmart), CySmart 1.3 to a PSoC4 peripheral.
CySmart2.zip 78.7 K
Does the PSoC4 support the LE Data Packet Length Extension (DLE?) If so, how do we enabled it via the CySmart API?
We (Torin) introduced a workaround where we don't change our GAPP Data Length to prevent the LLCP update.
Yes. PSoC 4 BLE supports Bluetooth 4.2 spec which has a provision for Data Length Extension. You can either set this directly in the component GUI as shown below:
Or you can also use the API CyBle_GapSetDataLength() present in page number 106 of the BLE component datasheet obtained from the link below:
For more information please refer the application note:
Thanks and regards