Hi, Dialogs,
I was developing a remote controller based on the DSPS-HOST project. the remote controller can be switched from a central role to a peripheral role by a button press so to support OTA.
I have done some modification on a DSPS-Device project and it can be OTA successfully, so I made the same change on the host project.
Now I the device can be in a peripheral role when the button pressed and the SUOTA Andriod apps can detect the device, but when I connect to it , an error occured.Like this:
An error occurred. The remote device does not support SUOTA.
So what' wrong ? How can I debug this issue, I think I need the android apps souce code so that I can debug, if the apps can't get some information it wants?
Some other info: when the deive is switched to a peripheral role, I just start the advertising and doesn't creat a app db, and I can use other BLE debug tool such as nRF master control, and just two service discovered： Generic access and generic attribute. Does I need to do something else, so that de Android Apps can recognize the device as OTA supported device.
⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
Tue, 2017-04-25 02:51
#1
SUOTA error on DSPS project
Device:
Hi chris0409,
Well, it depends if you have properly applied the SUOTA service to the device when the device switches from central to peripheral, when the switch to a peripheral role is done, does the peripheral have the SUOTA service ? You can check that by connecting to a generic BLE central application and check the services that the peripheral device exposes. The SUOTA android application tracks a SUOTA supported device via the advertising string but that doesn't mean that the service is available, so if the discovery from the central starts but its not able to find the SUOTA characteristics, i suspect that this is the error message that should occur (also this can happen because you have altered the UUID of the characteristics). So please check if the SUOTA service is available when the device switches roles. Also please have a look at the FAQ section in the software implementation section and check the "How to add the SUOTA profile to my application".
Thanks MT_dialog
Hi, MT_dialog
your guidance really help me. I have missed the db create procedure when switch to a peripheral role, so the app can't find OTA service when doing service discovery after connected. Thank you very much!