updated UM1755 doc?

philippe1 · ‎2015-02-02

Posted on February 03, 2015 at 08:49

Hi everyone,

I was wondering if there is an updated version for the UM1755 which (partially) describes the commands available for the BlueNRG chipset. I can't find decoding scheme for the VS HCI events for example.

Thank you.

marchese.graziella · ‎2015-02-23

Posted on February 23, 2015 at 14:43

Hi,

as soon as possible, we will update the UM1755 doc. Anyway if you have any doubts about any command/event, don't hesitate to ask us.

Regards,

Graziella

philippe1 · ‎2015-02-26

Posted on February 26, 2015 at 16:26

Thank you for your answer.

Could you please help me with this frame ?

Thank you.

0x04-0xff-0x10-0x02-0x08-0x01-0x08-0x0b-0x12-0x0c-0x08-0x00-0x50-0x00-0x20-0x03-0x01-0x00-0xe8.

marchese.graziella · ‎2015-02-27

Posted on February 27, 2015 at 12:36

Hi,

here below the description:

0x04- EVENT_TYPE;

0xff - HCI_VENDOR;

0x10-Parameter Total Length;

0x02 0x08- EVT_BLUE_L2CAP_CONNECTION_UPDATE_REQ - The event code for connection update request event;

0x01- 0x08- Connection_Handle: Handle of the connection for which the connection update request has been received. The same handle has to be returned while responding to the event with the command Aci_L2CAP_Connection_Update_Resp.;

0x0b- Event_Data_Length: Length of the data to follow. The data will be the L2CAP connection update request received;

0x12- Identifier: This is the identifier which associates the request to the response. The same identifier has to be returned by the upper layer in the command Aci_L2CAP_Connection_Update_Resp.;

0x0c-0x08-L2CAP_Length: Length of the L2CAP connection update request;

0x00-0x50-Interval_Min: Value as defined in Bluetooth 4.0 spec, Volume 3, Part A 4.20;

0x00-0x20-Interval_Max: Value as defined in Bluetooth 4.0 spec, Volume 3, Part A 4.20;

0x03-0x01- Slave_Latency: Value as defined in Bluetooth 4.0 spec, Volume 3, Part A 4.20;

0x00-0xe8 -Timeout_Multiplier :Value as defined in Bluetooth 4.0 spec, Volume 3, Part A 4.20,

The EVT_BLUE_L2CAP_CONNECTION_UPDATE_REQ event is given by the L2CAP layer when a connection update request is received from the slave. The upper layer which receives this event has to respond by sending a Aci_L2CAP_Connection_Update_Resp command to the BlueNRG.

Regards,

Graziella

Thank you for your answer.

Could you please help me with this frame ?

Thank you.

0x04-0xff-0x10-0x02-0x08-0x01-0x08-0x0b-0x12-0x0c-0x08-0x00-0x50-0x00-0x20-0x03-0x01-0x00-0xe8.

philippe1 · ‎2015-02-27

Posted on February 27, 2015 at 13:08

Thank you !

philippe1 · ‎2015-04-10

Posted on April 10, 2015 at 18:48

I need help with this frame.

This is a GATT Read by Group Response.

Length of each field looks to be 6, but how de we decode the data ?

04-ff-12-0a-0c-01-08-0d-06 0e-00-10-00-04-18 11-00-ff-ff-0f-18.

Thank you.

charles23 · ‎2015-04-10

Posted on April 10, 2015 at 23:15

Most of the commands and responses that are not documented in UM1755 can be found by searching the Bluetooth specification itself. It is not always easy to find this, though. You can/should also refer to the source code in BlueNRG Development kit (e.g. bluenrg_hci.c) - in some cases the description of parameters in UM1755 differ from the source code (i.e. in error).

marchese.graziella · ‎2015-04-13

Posted on April 13, 2015 at 10:21

Hi,

The Read By Type Request is used to obtain the values of attributes where the attribute type is known but the handle is not known. The responses of the procedure are given through the EVT_BLUE_ATT_READ_BY_TYPE_RESP event. The end of the procedure is indicated by a EVT_BLUE_GATT_PROCEDURE_COMPLETE event.

The struct of EVT_BLUE_ATT_READ_BY_TYPE_RESP is:

#define EVT_BLUE_ATT_READ_BY_GROUP_TYPE_RESP (0x0C0A)

typedef __packed struct _evt_att_read_by_group_resp{

uint16_t conn_handle;

uint8_t event_data_length;

uint8_t attribute_data_length;

uint8_t attribute_data_list[VARIABLE_SIZE];

} PACKED evt_att_read_by_group_resp;

Therefore for raw packet: 04-ff-12-0a-0c-01-08-0d-06 0e-00-10-00-04-18 11-00-ff-ff-0f-18

0x04- EVENT_TYPE;

0xff - HCI_VENDOR;

0x12 - Parameter Total Length;

0x0C0A - code for EVT_BLUE_ATT_READ_BY_GROUP_TYPE_RESP;

0x0801 - Connection_Handle;

0x0D - Event_Data_Length

0x06 -Attribute Data Length;

#first block of 6 bytes

0x000e - Start Handle;

0x0010 - End Handle;

0x1804 - UUID

#second block of 6 bytes

0x0011 - Start Handle;

0xffff - End Handle;

0x180f - UUID

For details, please see the documentation of BlueNRG DK ( 'BlueNRG Bluetooth LE Stack Application Command Interface (ACI) doxygen documentation' in the :BlueNRG Development kit for BlueNRG documentation version 1.7.0.0''

In any case, if you download the latest version of BlueNRG DK, in the scrip tab there is the feature ''Discovery Services and Characteristics'' that performs the discovery of services and characteristics and you can see how the events are parsed.

Regards,

Graziella

Most of the commands and responses that are not documented in UM1755 can be found by searching the Bluetooth specification itself. It is not always easy to find this, though. You can/should also refer to the source code in BlueNRG Development kit (e.g. bluenrg_hci.c) - in some cases the description of parameters in UM1755 differ from the source code (i.e. in error).

philippe1 · ‎2015-04-13

Posted on April 13, 2015 at 11:57

Thank you for the info.

I was using the 1.6 version.

Now I'm using he 1.7 version and it looks it answers most of my questions.

Regards.

marchese.graziella · ‎2015-04-13

Posted on April 13, 2015 at 12:05

you are welcome,

regards,

Graziella