API unique to HTS designs configured as a GATT Client role.
A letter 'c' is appended to the API name: Cy_BLE_HTSC_
|
cy_en_ble_api_result_t | Cy_BLE_HTSC_SetCharacteristicValue (cy_stc_ble_conn_handle_t connHandle, cy_en_ble_hts_char_index_t charIndex, uint8_t attrSize, uint8_t *attrValue) |
| This function is used to write the characteristic (which is identified by charIndex) value attribute in the server. More...
|
|
cy_en_ble_api_result_t | Cy_BLE_HTSC_GetCharacteristicValue (cy_stc_ble_conn_handle_t connHandle, cy_en_ble_hts_char_index_t charIndex) |
| This function is used to read a characteristic value, which is a value identified by charIndex, from the server. More...
|
|
cy_en_ble_api_result_t | Cy_BLE_HTSC_SetCharacteristicDescriptor (cy_stc_ble_conn_handle_t connHandle, cy_en_ble_hts_char_index_t charIndex, cy_en_ble_hts_descr_index_t descrIndex, uint8_t attrSize, uint8_t *attrValue) |
| This function is used to write the characteristic descriptor to the server, which is identified by charIndex and descrIndex. More...
|
|
cy_en_ble_api_result_t | Cy_BLE_HTSC_GetCharacteristicDescriptor (cy_stc_ble_conn_handle_t connHandle, cy_en_ble_hts_char_index_t charIndex, cy_en_ble_hts_descr_index_t descrIndex) |
| Gets the characteristic descriptor of the specified characteristic of the service. More...
|
|
◆ Cy_BLE_HTSC_SetCharacteristicValue()
This function is used to write the characteristic (which is identified by charIndex) value attribute in the server.
As a result a Write Request is sent to the GATT Server and on successful execution of the request on the server side, the CY_BLE_EVT_HTSS_WRITE_CHAR event is generated. On successful request execution on the server side, the Write Response is sent to the client.
- Parameters
-
connHandle | The connection handle. |
charIndex | The index of the service characteristic. |
attrSize | The size of the characteristic value attribute. |
attrValue | The pointer to the characteristic value data that should be sent to the server device. |
- Returns
- A return value of type cy_en_ble_api_result_t.
Error Codes | Description |
CY_BLE_SUCCESS | The request was sent successfully. |
CY_BLE_ERROR_INVALID_PARAMETER | Validation of the input parameter failed. |
CY_BLE_ERROR_INVALID_OPERATION | Operation is invalid for this characteristic. |
CY_BLE_ERROR_GATT_DB_INVALID_ATTR_HANDLE | The peer device doesn't have the particular characteristic. |
CY_BLE_ERROR_INVALID_STATE | Connection with the server is not established. |
CY_BLE_ERROR_MEMORY_ALLOCATION_FAILED | Memory allocation failed. |
- Events
- If execution is successful (return value = CY_BLE_SUCCESS), these events can appear:
If a HTS service-specific callback is registered with Cy_BLE_HTS_RegisterAttrCallback():
Otherwise (if a HTS service-specific callback is not registered):
◆ Cy_BLE_HTSC_GetCharacteristicValue()
This function is used to read a characteristic value, which is a value identified by charIndex, from the server.
- Parameters
-
- Returns
- A return value of type cy_en_ble_api_result_t.
Error Codes | Description |
CY_BLE_SUCCESS | The Read Request was sent successfully. |
CY_BLE_ERROR_INVALID_PARAMETER | Validation of the input parameter failed. |
CY_BLE_ERROR_INVALID_OPERATION | Operation is invalid for this characteristic. |
CY_BLE_ERROR_INVALID_STATE | Connection with the server is not established. |
CY_BLE_ERROR_MEMORY_ALLOCATION_FAILED | Memory allocation failed. |
CY_BLE_ERROR_GATT_DB_INVALID_ATTR_HANDLE | The peer device doesn't have the particular characteristic. |
- Events
- If execution is successful (return value = CY_BLE_SUCCESS) these events can appear:
If the HTS service-specific callback is registered (with Cy_BLE_HTS_RegisterAttrCallback):
Otherwise (if a HTS service-specific callback is not registered):
◆ Cy_BLE_HTSC_SetCharacteristicDescriptor()
This function is used to write the characteristic descriptor to the server, which is identified by charIndex and descrIndex.
Internally, Write Request is sent to the GATT Server and on successful execution of the request on the server side, the following events can be generated:
- Parameters
-
connHandle | The connection handle. |
charIndex | The index of the service characteristic. |
descrIndex | The index of the service characteristic descriptor. |
attrSize | The size of the characteristic value attribute. |
attrValue | The pointer to the characteristic descriptor value data that should be sent to the server device. |
- Returns
- A return value of type cy_en_ble_api_result_t.
Error Codes | Description |
CY_BLE_SUCCESS | The request was sent successfully. |
CY_BLE_ERROR_INVALID_PARAMETER | Validation of the input parameter failed. |
CY_BLE_ERROR_INVALID_OPERATION | Operation is invalid for this characteristic. |
CY_BLE_ERROR_GATT_DB_INVALID_ATTR_HANDLE | The peer device doesn't have the particular characteristic. |
CY_BLE_ERROR_INVALID_STATE | Connection with the server is not established. |
CY_BLE_ERROR_MEMORY_ALLOCATION_FAILED | Memory allocation failed. |
- Events
- If execution is successful (return value = CY_BLE_SUCCESS), these events can appear:
If a HTS service-specific callback is registered with Cy_BLE_HTS_RegisterAttrCallback():
Otherwise (if a HTS service-specific callback is not registered):
◆ Cy_BLE_HTSC_GetCharacteristicDescriptor()
Gets the characteristic descriptor of the specified characteristic of the service.
- Parameters
-
connHandle | The connection handle. |
charIndex | The index of the service characteristic. |
descrIndex | The index of the service characteristic descriptor. |
- Returns
- A return value of type cy_en_ble_api_result_t.
Error Codes | Description |
CY_BLE_SUCCESS | The request was sent successfully. |
CY_BLE_ERROR_INVALID_PARAMETER | Validation of the input parameter failed. |
CY_BLE_ERROR_INVALID_OPERATION | Operation is invalid for this characteristic. |
CY_BLE_ERROR_INVALID_STATE | Connection with the server is not established. |
CY_BLE_ERROR_MEMORY_ALLOCATION_FAILED | Memory allocation failed. |
- Events
- If execution is successful (return value = CY_BLE_SUCCESS), these events can appear:
If a HTS service-specific callback is registered (with Cy_BLE_HTS_RegisterAttrCallback):
Otherwise (if a HTS service-specific callback is not registered):