Hi,
I am implementing an OTA with WiRa SDK 10.440.8.6. I am implementing OTA over WiFi (via another WiFi module).
I am using the pxp_reporter code as the base which implements the OTA over BLE.
I have the following questions
1. Is there any implementation of a generic OTA example which can used across Wi-Fi, BLE or any other mechanism?
2. When we build the Dialog binary (.img) for transferring and flashing, will it contain the Product Header as shown in Sec 5.2.35. User Guides — DA1469x Software Platform Reference UM-B-092 (dialog-semiconductor.com)?
3. Is it required to build different firmware for different partition, FW1 and FW2 or is the build agnostic of which partition it will be flashed on?
Thanks and Regards,
Subbu
Device:

Hi Subbu,
谢谢你的问题。
Thanks, PM_Dialog
Hi,
Sorry, if I was not clear enough.
1. I am implementing an OTA over WiFi solution. So, its not over BLE.
2. Okay. Thanks.
3. In some MCUs, we need to build different OTA images for different paritions. I want to check if for Dialog MCU, do we need to build multiple images or will one image can be flash in either partition ?
Regards,
Subramanyan
Hi Subramanyan,
The DA1469x supports SUOTA that can be achieved over BLE.
When a project is built for SUOTA configuration, then the corresponding partition table will be used. In case of pxp_reporter, the application will take the sdk/config/4M/suota/partition_table.h . The SUOTA partition table should contain the NVMS_FW_EXEC_PART and the NVMS_FW_UPDATE_PART
所以,当SUOTA is implemented, an additional partition is required so that both the current and the updated image can be stored.
NVMS_FW_EXEC_PART : This entry is used during a SUOTA enabled application for storing the application image
NVMS_FW_UPDATE_PART : This entry is used during a SUOTA enabled application and contains the new updated firmware version.
The current and the new firmware should have the same partitioning.
Thanks, PM_Dialog
Thanks a lot for your answers. It helped.