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 fromhttp://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?
Hi igotit,
The DSPS has no problem if you change the advertising data, you can test it for yourself, but the same doesn't apply for SUOTA. The application waits for SUOTA's UUID in order to be recognized, finally i dont think that the DISS service has anything to do with SUOTA.
Thanks MT_dialog
@igotit,
I believe that the DISS profile presents to the SUOTA app, the Manufacturer/Model/Software Version/Firmware Version. If the DISS profile is not implemented then the SUOTA app will not display the above details.
Hi klim9531,
Thats correct, the DISS profile just populates the fields that you mention, when there is no DISS profile there will be no data for the SUOTA app on those fields but the application will update the fw and it will work properly, there is no dependance between the two services.
Thanks MT_dialog
HELLO
I started to use the board DA14580 with the sdk 3.0.10.1, I want to implement the SUOTA in this version of SDK, is there some tutorial or information of how to implement SUOTA in this sdk?
Thank you for your time and help
regards
Hi PALAKAS,
There is no tutorial how to add the SUOTA profile in the SDK 3, dialog recommends to move into the latest SDK which is SDK 5. If you insist on keep working with SDK3, what you can do, is follow the proximity reporter project that includes the SUOTA profile as a reference to include the profile into your project.
Thanks MT_dialog
thanks