Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I discover that OTA upgrades are unavailable in Wiced 3.0: core functions (platform_load_ota_app ...) emptied and apps/waf/ota_upgrade sample app removed!
Will such an important feature be available back soon ?
Furthermore, we would like to implement OTA in a different way, a bit like how apps/waf/sflash_write does: The new firmware would be downloaded and written to the SPI flash, then the boot-loader would copy it to internal MCU flash at next reboot (not at the end of download).
I've been looking at the sflash_write app code but I can't figure out how it works because it is driven by an external TCL script ( openOCD). Any help would be appreciated.
The procedure is for version2.4.1. But, it should be work in Wiced 3 also and it is using different file name.
The step can be like this.
1. you should have the new firmware ready in the external flash.
2. you can use the platform_copy_external_to_internal(), copy from external to internal. But, the function should be done none since the inside is not finished yet. You can just copy it from external to internal and start the app. (Remark: we are working on BCM9WCDUSI09 module)
If everything is OK, no jtag is needed to program the external flash.
Yes, you are right. Therefore, we have customized our OTA version instead of original one.
void platform_upgrade_app( void )
static uint8_t rx_buffer; /* API Function will not return, so it is safe to declare static big buffer */
I think that the 'new firmware' detection in the bootloader is for firmware written in spi flash by the apps/waf/sflash_write app, and this app is not actually involved in any firmware upload process, even jtag.
So we are free to modify the bootloader without breaking compatibility with any wiced firmware upgrade method. Am I right ?