Hi Dialog,
I'm trying to test the SUOTA service with a mobile device with the pxp_reporter demo. I followed the instructions from UM-B-056 (Chapter 9-10). After I have copied the image to an android tablet and used the erase_qspi_jtag_win and the suota_initial_flash_jtag_loader scripts, I couldn’t scan for the device, neither in the SUOTA App nor in the LightBlue App.
一旦SUOTA测试将会成功,我’d like to implement the SUOTA Service in the multi-link demo. Is this possible?
Thanks in advance,
Mario
Device:
Hi Mario,
You can check via the power profiler if the device is advertising or not, after you 've burned the memory on the device, have you presses the RESET button in order for the device to start running ?
Regarding implementing the SUOTA application on different projects, yes, it is possible, you will have to place the SUOTA implementation in your custom project (from the proximity reporter the code that its inserted to the project if the dg_configSUOTA_SUPPORT is defined). After doing that you will have to build the image for the 0x20000 memory offset, check in the custom_config_qspi_suota.h the #define dg_configIMAGE_FLASH_OFFSET (0x20000).
Thanks MT_dialog
Hi Dialog,
thanks for your answer. Yes, I did press the RESET button. Now, after some new attempts I’m able to see the device in the SUOTA APP, but the update process stays at 0%. I’m using the basic development kit. Could this be a problem?
Thanks Mario
Hi Mario,
There is no issue in running the SUOTA application on the basic kit (just tested it), the SUOTA on the proximity reporter should operate the same regardless the dev kit. What you are experiencing should be either a mis-configuration of the demo, or perhaps something wrong with the installation of the application.
Thanks MT_dialog
Hi Dialog,
I’m still trying to implement the SUOTA service in my ble_multi_link project.
At first I imported the custom_config_qspi_suota.h and the sw_version.h file to my project. Afterwards I added the SUOTA code from UM-B-056 to ble_multi_link_task.c. Is it necessary to import the initial_flash.bat, initial_flash.sh, mkimage.bat and the mkimage.sh file into the project folder? And what is about the config files: platform_nvparam.h and platform_nvparam_values.h?
I tried to build the ble_multi_link project with the Release_QSPI_SUOTA configuration, but there was no such configuration to select.
Is there anything to consider when I’m using the DA14681 instead of the DA14680?
Thanks,
Mario
Hi Mario,
不它不是nessecity移动这些文件给你current project, if you use the suota_initial_flag_jtag_win script then, on your console, you should see the operations that the script does, the .bat files that you report just invoke the corresponding script from the scripts folder. Regarding the platform_nvparam.h and platform_nvparam_values.h those files are included in the config file in order for the user to overlap the current configuration of the nv parameters, for example, identical files are also located in the/sdk/adapters/include and if you run the program_qspi_serial_win the files that are going to be used are going to be the default values taken from those files, if you replicate those file in the config folder with some custom values then the script is going to use the files from the config folder and burn them to the qspi. Regarding the configurations and SUOTA enabled images (in the SDK only the prox reporter has a SUOTA configuration). The proximity project has two configuration files the custom_config_qspi_suota.h (for the SUOTA configuration) and the custom_config_qspi (for the non SUOTA configuration), when you select an active build essentially you are switching between those two configuration files, so in order to create a new Configuration that will include the SUOTA you will have to create a new configuration:
Thanks MT_dialog