Hi dialog!
I have some problems while testing SUOTA with smartsnippets.
I use connection manager to initiate a develop board as peripheral(SUOTA receiver) and start to advertise.Then use smartsnippets to open another board as SUOTA Initiator.
1.After choosing COM port and press"connect" button, it always alert " COM X port is externally used". But I am pretty sure that the com port is not used outsite.
2.after that , below log info show up,and the initiator could not scan the receiver successfully.
3.Is there some work has to be done before doing this test, like secondary bootloader should be programed into OTP?Could you show me the correct steps to test SUOTA?
Looking forward to receive you help.
Best regards.
[INFO @15-01-14 14:19:03] Loading firmware, please wait...
[INFO @15-01-14 14:19:07] Firmware loaded successfully.
[INFO @15-01-14 14:19:07] Connecting to COM10
[INFO @15-01-14 14:19:07] COM10 successfully opened.
[INFO @15-01-14 14:19:07] Scanning for devices...
[INFO @15-01-14 14:19:22] Target device has been disconnected. Please try to re-establish link.
[INFO @15-01-14 14:21:24] Loading firmware, please wait...
[INFO @15-01-14 14:21:27] Firmware loaded successfully.
[INFO @15-01-14 14:21:27] Connecting to COM10
[INFO @15-01-14 14:21:28] COM10 successfully opened.
[INFO @15-01-14 14:21:28] Scanning for devices...
[INFO @15-01-14 14:21:43] Target device has been disconnected. Please try to re-establish link.
Hi Terry,
First I have got ask which Development board you are using and if you have got FLASH connected to the DA14580?
Secondly Connection manager doesnt support SUOTA so you should use two Basic kits or go to the app store or play store and download the SUOTA application (DIALOG SUOTA).
Regards
TN
Dear TN_Dialog,
To you question , I am using two Basic kits. the problem of scaning device fail is solved , it seems that we had to connect both JTAG port and COM port both while testing SUOTA.Now I can scan the recceiver successfully which is runing the "fh_proxr_sdk.uvproj".
But another problem came up, after choosing the fireware file to be download and the spi memory type, witch value should be filled in "block size"?
I try the size of fireware bin file, the block size of SPI flash W25X20CL(32768, 65536), and the log keep showing that:SPOTAR_PATCH_LEN_ERR.
Did dialog has a document about how to test SUOTA?
[INFO @15-01-15 15:34:44] Scanning for devices...
[INFO @15-01-15 15:34:46] Found device with address 80:EA:CA:00:00:01, Public. Device does not support the SPOTA service.
[INFO @15-01-15 15:34:51] Scanning completed.
[INFO @15-01-15 15:34:55] Establishing Link with target device...
[INFO @15-01-15 15:34:56] Link with target device has been established.
[INFO @15-01-15 15:34:56] Characteristics discovery started.
[INFO @15-01-15 15:34:57] Characteristics discovery finished.
[INFO @15-01-15 15:35:14] Firmware download started...
[INFO @15-01-15 15:35:14] SPOTAR_IMG_STARTED
(信息@15-01-15 15:35:14)内存信息:
0 bytes
[ERROR @15-01-15 15:35:15] SPOTAR_PATCH_LEN_ERR
[INFO @15-01-15 15:35:15] Firmware download failed.
[INFO @15-01-15 15:34:55] Establishing Link with target device...
[INFO @15-01-15 15:34:56] Link with target device has been established.
[INFO @15-01-15 15:34:56] Characteristics discovery started.
[INFO @15-01-15 15:34:57] Characteristics discovery finished.
[INFO @15-01-15 15:35:14] Firmware download started...
[INFO @15-01-15 15:35:14] SPOTAR_IMG_STARTED
(信息@15-01-15 15:35:14)内存信息:
0 bytes
[ERROR @15-01-15 15:35:15] SPOTAR_PATCH_LEN_ERR
[INFO @15-01-15 15:35:15] Firmware download failed.
And there is another favor to ask, since we could not get access to GOOGLE PLAY appstore in China and I could not find it on internet, could you send me a copy of (DIALOG SUOTA)?
thanks a lot, my mail issuperwht@126.com.
best regards.
Hello Terry,
SUOTA APK is now available on our support site under Reference Design Software & Additional Releases
BR JE_Dialog
thank you very much. I have found it.
Hello Terrry, please note we are generatign an apps note on SUOTA : we will have this in approx 2 weeks from now.
BR JE_Dialog
Where we can find SUOTA app note?
Best regards
Shiva
Hi
I have basic questions on SUOTA.
1) I wish to get the SUOTA work with my project which is based on SDK5.0.3->ble_app_peripheral. Please guide me get this done?
2) Is there any document/appnote which talks about porting of SUOTA changes on to a custom project? (I build a project which contains only few custom services, now I wish to port SUOTA changes on to this project.).
Br,
Gotta
Hi ggotta,
1) proximity_profile SDK中有一个例子implementation of the SUOTA on the new SDK5, you can check this in order to see the modifications that are required in order to implement it on your custom project.
2) The only available document regarding SUOTA is the AN-B-010 which includes the guidelines how to handle SUOTA. You dont need anything specific in order to place the profile in your custom project, just add the SUOTA profile (include the spoter.h in the user_profiles_config), check if the following files app_spotar_task and app_spotar exist in your project, add the SUOTA UUID in your advertising string and you should be ok.
Thanks MT_dialog
Hi,
I did try this, the proximity reporter is working fine. When I tried to include this profile in my custom project, it just stops basic advertising functionality. There are some issues related to with memory, I need investigate further.
On the other-hand, I have another project build based SDK5.0.3->ble_app_peripheral which got end-up with some compilation issues if include spotar.h. Then I tried to build fresh SDK5.0.3 unziped code with spoter.h included in the user_profiles_config.
(1) I am getting the same error as below,
..\..\..\..\..\sdk\app_modules\src\app_spotar\app_spotar.c(305): error: #20: identifier "user_profile_callbacks" is undefined.
(Not sure what all the changes w.r.t user_profile_callbacks and on_spotar_status_change)
(2) May I ask you provide more details on "add the SUOTA UUID in your advertising string", can copy a code snippet for reference.
Br,
Govind.
Did you find time to look into this?
Hi ggotta,
Sorry for the delayed response, if when including the profile you are not able to advetise then the advertising should not be valid, before executing the advertising procedure the string goes through a validation check from the stack and if the advertising string isn't valid the advertising stops. Regarding the compilation issue when including the spotar profile (in the user_profiles_config.h) you have to add the nessecary callbacks (please check the proximity reporter in the user_callback_config.h) and you have to add the sdk profile (the spotar.c and the spotar_task.c in your sdk_profiles file) and also you have to add the on_spotar_status_change() function (what the device should do during START and STOP conditions). And one last thing, go to the user_modules_config.h file and make sure that the EXCLUDE_DLG_SPOTAR is set to 0 and not 1 otherwise the spotar wont work.
Regarding the advertising string and including the SUOTA in the ble_app_peripheral example you can try the following:
#define USER_ADVERTISE_DATA ("\x05"\
ADV_TYPE_COMPLETE_LIST_16BIT_SERVICE_IDS\
ADV_UUID_DEVICE_INFORMATION_SERVICE\
ADV_UUID_SPOTAR_SERVICE\
"\x11"\
ADV_TYPE_COMPLETE_LIST_128BIT_SERVICE_IDS\
"\x2F\x2A\x93\xA6\xBD\xD8\x41\x52\xAC\x0B\x10\x99\x2E\xC6\xFE\xED")
Thanks MT_dialog