PM0237 datasheet(80/88 Pages) STMICROELECTRONICS

80 / 88 page

Design an application using BlueNRG, BlueNRG-MS ACI APIs

PM0237

80/88

DocID027104 Rev 2

evt_gatt_attr_notification *evt = (evt_gatt_attr_notification*)blue_evt-

>data;

evt_gatt_attr_notification data:

evt->conn_handle: connection handle;

evt->event_data_length: length of attribute value + handle (2 bytes);

evt->attr_handle: handle of the notified characteristic;

evt->attr_value[]: characteristic value.

Add user code for handling the received notification based on the

application scenario.

........

}

break;

}/* switch(blue_evt->ecode)*/

}/* switch(evt->subevent)*/

}/* end HCI_Event_CB() */

3.8

Basic/typical error conditions description

On BlueNRG, BlueNRG-MS ACI framework, the tBleStatus type is defined in order to

return the BlueNRG, BlueNRG-MS stack error conditions. The status and error codes are

defined within the header file “ble_status.h”.

When a stack API is called, it is recommended to get the API return status and to monitor it

in order to track potential error conditions.

BLE_STATUS_SUCCESS (0x00) is returned when the API is successfully executed. For a

detailed list of error conditions associated to each ACI API refer to the UM1755 and

UM1865 user manuals, on Section 4: References.

3.9

BlueNRG-MS simultaneously Master, Slave scenario

BlueNRG-MS device stack supports multiple roles simultaneously. This allows the same

device to act as Master on one or more connections (up to eight connections are supported

on Stack Mode 3), and to act as a Slave on another connection.

The following pseudo code describes how a BlueNRG-MS device can be initialized for

supporting Central and Peripheral roles simultaneously:

uint8_t role = GAP_PERIPHERAL_ROLE | GAP_CENTRAL_ROLE;

ret = aci_gap_init(role, 0, 0x07, &service_handle,

&dev_name_char_handle, &appearance_char_handle);

A simultaneous Master and Slave test scenario can be easily targeted as follows:

PM0237 Datasheet(PDF) 80 Page - STMicroelectronics