This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
we are developing with the SensorTag as base a product to track movement of people, the sensor get's pinned under their seat and with the old SensorTag we had some success and the base features worked as planned.
Now we switched to the new CC2650, as it has an external flash memory, the movement sensor is already a combined sensor (on CC2541 we changed the accelerometer and gyroscope to a 6 axis mpu) and some other points. Hardware development is done by another company by our definitions, we only do the firmware changes.
With Android every BLE-Device will get identified by a unique identifier that won't change, think it's the device address.
On iOS the BLE CentralManager i use in my App creates a UDID for every Bluetooth Device when it discovers it first, but it wil not always stay the same after Bluetooth restarting, or phone shutdown.
So i wanted to add the device address to advertising data, like it is in the device information block. But my first try resulted in a bricked SensorTag, which i only could repair using the stock firmware with Flash Programmer.
So far i guessed i should have to use "GAP_ADTYPE_LE_BD_ADDR" and wanted to add it using the same code as for device info
I'm a learned software programmer, this is now my first hardware programming project, mostly before i did websites and mobile apps.
--PS. Thank you for clicking This resolved my issue below if this answered your question!
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Aslak N.:
static uint8_t advertData =
// Flags; this sets the device to use limited discoverable
// mode (advertises for 30 seconds at a time) instead of general
// discoverable mode (advertises indefinitely)
0x02, // length of this data
DEFAULT_DISCOVERABLE_MODE | GAP_ADTYPE_FLAGS_BREDR_NOT_SUPPORTED,
// service UUID, to notify central devices what services are included
// in this peripheral
0x03, // length of this data
GAP_ADTYPE_16BIT_MORE, // some of the UUID's, but not all
// Manufacturer specific advertising data
0x00 // Key state
This is the current Code for advertising data, we would not need something to keep our tags unique only, but every single tag should have its own unique id,that's why i thought of the device address.
It can happen, that a customer has like 10 of our tags in the office and i want to add to the user settings in the app, what's the tag of the current person.For that i wanted to have a unique id in the advertising data.
In the current SensorTag advertisement data is the manufacturer data as "0d000300 00"
In reply to Stephan Maier:
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.