Hi,
how to prevent ROM automatically adding Flags to the advertisement packet when advertising as connectable ("The Flags data type are added by the ROM")?
I am aware that this is not by the specs (there is similar question How to remove flags from advertisement packet but that one is for Non-connectable advertising), however there must be some way to have full control over the advertisement packet payload - which is possible using HCI.
Thank you,
Bojan
Hello Dialog_Support,
I am using beacon mode to broadcast advertising data string. If i want to send some dynamic data then i changed the manufacturer data string and broadcast. At the mobile application side they are receiving advertising data but not getting the byte i have changed. BLE Scanner is able to receive data in form of raw data.
Mobile App is receiving 0 at data field so can you tell me where is the data field located in advertising data? Can you suggest any App other then ble scanner which can able to receive advertising data string?
Thanks and Regards,
Ruchi Patel
Hi there,
Our customer wants to change advertising data by mobile phone, so I add a function to receive data from mobile.
I use the function - "app_easy_gap_update_adv_data" to set adv data, however, if the data from mobile is wrong, I found DA14585 will hang up and be reset by watch dog.
For example, if mobile send "FF FF FF FF FF" and I set the data to "app_easy_gap_update_adv_data", DA14585 will hang up and be reset.
How can I prevent this status? write a parser to confirm the data? Does there any rules or formats for advertising data?
Thanks.
Hello,
Is it possible with SDK5 to change the advertising data packets dynamically during the life of the application?
If yes, how?
Thanks for your help.,
Andrea
Hi,
Now I'm working to implement the SUOTA functionality into DSPS reference peoject.
#1. Target Board : DA14580 Development Kit-PRO.
#2. base project : DSPS ref. preoject from http://support.dialog-semiconductor.com/reference-designs
#3. SUOTA example code : prox_reporter.upprojx from the SDK 3.0.10.1
My starting project is above #2 and implement the SUOTA and DISS. The code modification is fully based on the above #3 source codes.
At final stage, the ambiguity is occurred.
Question1.
The DSPS's Advertising Data (as following) is mandatory to work with DSPS Central ? i.e. If I change the advertising data something different, the android DSPS application can not communcate with my DSPS device?
// DSPS's advertising data.
#define APP_DFLT_ADV_DATA "\x11\x07\xb7\x5c\x49\xd2\x04\xa3\x40\x71\xa0\xb5\x35\x85\x3e\xb0\x83\x07"
#define APP_DFLT_ADV_DATA_LEN (18)
Question2.
The SUOTA's Advertising Data(as following) is mandatory to work with android's SUOTA ? ex. if the advertising data is different, the android's SUOTA can not find my device ?
// SUOTA example prox_reporter's advertising data.
#if (BLE_SPOTA_RECEIVER)
#define APP_ADV_DATA "\x09\x03\x03\x18\x02\x18\x04\x18\xF5\xFE"
#define APP_ADV_DATA_LEN (8+2)
#else
Question3.
If the both question1 and question2 ' s answer is yes, how can I make the advertising data which can be used for both DSPS and SUOTA ?
Question4.
The DISS is mandatory for SUOTA ?
If the DISS is not implemented to my device, the android's SUOTA can not work with my device? ex. If my device without DISS, the android's SUOTA can not find my device or can not update new software?