Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

Smart Bluetooth Forum Discussions

Anonymous
Not applicable

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 .
10.png

0 Likes
1 Solution

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

View solution in original post

0 Likes
8 Replies
BoonT_56
Employee
Employee
500 likes received 250 likes received 100 likes received

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)

0 Likes
Anonymous
Not applicable

Yes,I did follow the description of the doc and everything is OK until I did the Sign the SOTAFU Image step


0 Likes
Anonymous
Not applicable

It is possible that it is because my system is win64 bytes but the WsRsaKeyGen.exe and WsRsaSign.exe is for win32?

0 Likes

Did you verify that your BIN file is in the same directory that you invoke WsRsaSign.exe?

0 Likes
Anonymous
Not applicable

yes, I did

2.png

0 Likes

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
0 Likes
Anonymous
Not applicable

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!!

0 Likes

Sounds good! In future, use "Tab" for long file names at the cmd console.

0 Likes