1 of 1 people found this helpful
The DLE function is enabled by the BLE Component during BLE initialization if either of CY_BLE_CONFIG_LL_MAX_TX_PAYLOAD_SIZE or CY_BLE_CONFIG_LL_MAX_RX_PAYLOAD_SIZE macro (in BLE_config.h) is configured by the user to a value greater than 27 octets.
Regarding to set data length command, there is two APIs -
Cy_BLE_SetDataLength / Cy_BLE_SetSuggestedDataLength.
Successful completion of controller operation issued by the two APIs would be informed through 'CY_BLE_EVT_SET_DATA_LENGTH_COMPLETE' event and 'CY_BLE_EVT_SET_SUGGESTED_DATA_LENGTH_COMPLETE' respectively.
That's strange -- neither of the API functions you mentioned are in the PDL docs, but I tried them out in my PSoC Creator project and they do work. My documentation must be out of date or just incomplete. Anyway, thanks!
It's possible the PDL you involved in your project is old version. Please select PDL3.1.0 as the target library by setting under Tools -> Options -> PDL v3 location in PSoC Creator.
I'm still using PDL 3.0.1 because 3.1 breaks debugging (Debug the CM4 core -- falsely marked as solved) but for the record, even the latest PDL 3.1 documentation (v 126.96.36.19973) is missing the Cy_BLE_SetDataLength / Cy_BLE_SetSuggestedDataLength functions.
yes, PDL3.1.0 has CM4 debugging problem for some P6 parts. This might be fixed in next release.
I checked the PDL3.1.0 middleware BLE files and Cy_BLE_SetDataLength / Cy_BLE_SetSuggestedDataLength existing in cy_ble_stack_host_main.h