- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yesterday I upgrade from WICED 2.2.1 to WICED 2.2.3.
My apps OTAFU works well in WICED 2.2.1.
I found OTA FW algorithm changed in WICED 2.2.2 and 2.2.3. So I modified my apps to use OTAFU algorithm in WICED 2.2.3. I tried to use Windows ota_firmware_upgrade peer apps to upgrade my device and it abort.
OS: Windows 10
BT USB Dongle: Plugable USB Bluetooth 4.0 Low Energy Micro Adapter
Board:BCM20737tag
FW in board: ota-firmware-upgrade(WINCED 2.2.3)
FW to be upgrade to: My ota bin apps(around 31KB, size is OK, still under limit)
I did 2 tests.
--------------------------------------------------------------
Test 1: Use 2.2.3 Windows WsOtaUpgrade apps to upgrade to my ota bin. Aborted.
Tag got an Abort cmd from Apps.
10:48:29 - Command:7 State:5
Test 2: Use 2.2.1 Windows WsOtaUpgrade apps to upgrade to my ota bin. WsOtaUpgrade tell me Aborted. But from the log, upgrade succeed.
--------------------------------------------------------------
Each test I tried multiple times.
I feel the issue is in 2.2.3 Windows WsOtaUpgrade apps. It didn't handle large file well and will send abort cmd to the device.
One question: If I use WICED 2.2.3 but keep using OTAFW algorithm in WICED 2.2.1, will it cause any issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I think you'll find this post by cliff@rayman.com helpful: Re: OTA issue with new image size and DSx length
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
mwf_mmfae:
Cliff solved a different issue, image size check. I appreciate you point it to me.
In my case, image size is OK. The Issue I believe is in 2.2.3 Windows WsOtaUpgrade apps.