- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a WICED-Smart Board and I am trying to SOTAFU but stop in the Sign the SOTAFU Image step .I got the outcome as the image below.Please help me .
Solved! Go to Solution.
- Labels:
-
Over The Air Upgrades - OTA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had previously asked the developers about using the x32 tool under x64 Windows and they ran a test under x64 Windows; it worked as designed with no issues.
Couple of tips:
- Make sure you run the utility from a command prompt
- Make sure that the correct parameters are entered
- If the wrong parameters are entered, the tool displays the usage and then crashes on exit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is not easy to pin point the issue from above. Did you have a chance to review this doc?
WICED Secure Over-the-Air Firmware Upgrade Application Note (SDK 2.x and TAG3 Board)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes,I did follow the description of the doc and everything is OK until I did the Sign the SOTAFU Image step
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is possible that it is because my system is win64 bytes but the WsRsaKeyGen.exe and WsRsaSign.exe is for win32?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you verify that your BIN file is in the same directory that you invoke WsRsaSign.exe?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yes, I did
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I had previously asked the developers about using the x32 tool under x64 Windows and they ran a test under x64 Windows; it worked as designed with no issues.
Couple of tips:
- Make sure you run the utility from a command prompt
- Make sure that the correct parameters are entered
- If the wrong parameters are entered, the tool displays the usage and then crashes on exit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just fixed the problem.
It was because after I copyed the command "WsRsaSign.exe rsa.pri ota_secure_firmware_upgrade-BCM920737TAG_Q32-rom-ram-Wiced-release.ota.bin 3A19 1 1" to the cmd window, it changed to "WsRsaSign.exe rsa.pri ota_secure_firmware_upgrade-BCM920737TAG_Q32-rom-ram-Wicedrelease.ota.bin 3A19 1 1" so the issue appeared.
Anyway,Thanks a lot!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sounds good! In future, use "Tab" for long file names at the cmd console.