SWRA475A January 2015 – October 2016 CC2540 , CC2540T , CC2541 , CC2541-Q1
When using Manufacturer-Specific Data, the 0xFF flag is used to indicate so. The first two bytes of the data itself should be a company identifier code.
| Byte | Value | Description |
|---|---|---|
| 0 | 0x03-0x1F | Length of this data |
| 1 | 0xFF | Manufacturer-Specific Data Flag |
| 2 | 0x0D | Company ID |
| 3 | 0x00 | (Example, 0x000D – Texas Instruments) |
| 4 - 31 | - | User Defined Data (optional) |
The Bluetooth low energy packet format allows a device to broadcast 25 Bytes of Manufacturer-Specific Data if the advertisement is of the type Connectable undirected advertising (ADV_IND) or Scannable undirected advertising event (ADV_SCAN_IND) as Discoverable Mode flags are required. For non-connectable undirected advertising (ADV_NONCONN_IND) maximum length of the Manufacturer-Specific Data is 28 bytes. The Manufacturer-Specific Data can contain any user-defined information.
The broadcasted data can also be formatted in a standardized way. At the time of writing this application report there are a couple of standards, such as iBeacon from Apple and AltBeacon, from Radius Networks. iBeacon is protected by the MFi license and is interoperable with all iOS devices. AltBeacon is an open standard and the specification can be downloaded at http://altbeacon.org/. This application note describes how to use the TI Bluetooth low energy stack for an iBeacon. Eddystone, from Google, is an open source beacon standard, and is covered in an application note on the Bluetooth low energy wiki page.