嗨对话框，
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:
嗨马里奥，
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
嗨对话框，
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
嗨马里奥，
在基本套件上运行Suota应用程序（刚刚过测试），近距离记者的辅助应该不管DEV套件运行相同。您所在的遇到内容应该是演示的错误配置，或者在安装应用程序时可能出现问题。
Thanks MT_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?
谢谢，
Mario
嗨马里奥，
否将这些文件移动到当前项目的不一致，如果使用suota_initial_flag_jtag_win脚本，那么，在控制台上，您应该看到脚本所做的操作，您报告的.bat文件只能从中调用相应的脚本脚本文件夹。关于platform_nvparam.h和platform_nvparam_values.h那些文件包含在配置文件中，以便用户重叠NV参数的当前配置，例如，相同的文件也位于 / sdk /适配器/包括和运行program_qspi_serial_win将使用的文件将是从这些文件中取出的默认值，如果在具有某些自定义值的配置文件夹中复制这些文件，则脚本将要使用文件配置文件夹并将其刻录到QSPI。关于配置和辅导启用的图像（在SDK中，仅PROX报告器具有拟议配置）。邻近项目有两个配置文件Custom_Config_qspi_suota.h（对于upota配置）和custom_config_qspi（对于非子发配置），当您基本上选择一个活动构建时，您正在在这两个配置文件之间切换，因此才能创建一个新配置将包含upota，您必须创建新配置：
Thanks MT_dialog