cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Smart Bluetooth

Anonymous
Not applicable

When I open WsOtaUpgrade.exe, a error message occur: "Failed to open the patch file." What's wrong with that?

I can open HelloClient application.

0 Likes
Reply
1 Solution
Employee

Once the download is successful, the device will automatically boot into the new application image.

View solution in original post

0 Likes
Reply
13 Replies
Anonymous
Not applicable

How about drop the FW file(patch) into the application?

Or specifying file name on Command Prompt may work.

0 Likes
Reply
Anonymous
Not applicable

I do ota test as below:

1. download "RAM.ota_firmware_upgrade-BCM920732TAG_Q32 download" into my bcm920732_tag.

2. use command prompt to open WsOtaUpgrade.exe with "hello_sensor-BCM920732TAG_Q32-rom-ram-Wiced-release.ota.bin"

ota1.JPG

3. I can see above picture and click start.

ota2.JPG

4. Then, ota processing is finished, then click "Done".

If hello_sensor-BCM920732TAG_Q32-rom-ram-Wiced-release.ota.bin was running, I can see ble trace message from prm_uart, but the result is nothing at all.

So, when ota is finished, how can user trigger the application running in bcm920732_tag?

0 Likes
Reply
Employee

Once the download is successful, the device will automatically boot into the new application image.

View solution in original post

0 Likes
Reply
Anonymous
Not applicable

I use bcm20732tag and sdk is wiced smart v1.1.0, try it again.

Upgrade is ok and I can see "Success" on the PC's utility, but new application didn't run automation_io-BCM920732TAG_Q32-rom-ram-Wiced-release.ota.bin because I had upgrade it by ota.

I can captured trace information through com port, this is detail when upgrade process began.

hello_sensor_timeout:347

hello_sensor_timeout:348

hello_sensor_timeout:349

hello_sensor_write_handler: handle ff03

hello_sensor_write_handler: handle ff02

Command:1 State:0

send_status 0

hello_sensor_write_handler: handle ff02

Command:2 State:1

Active: 0x000004C0, Upgrade: 0x00008000, UG length: 0x00007B00

state:2 total_len:21022

send_status 0

a2 1a 00 6c 30 00 00 1b 33 00 00 00 00 00 00 14

1e 08 02 b0 04 00 00 00 00 00 00 00 00 72

hello_sensor_timeout:350

hello_sensor_timeout:351

hello_sensor_timeout:352

hello_sensor_timeout:353

hello_sensor_timeout:354

hello_sensor_timeout:355

hello_sensor_timeout:356

hello_sensor_timeout:357

hello_sensor_timeout:358

hello_sensor_timeout:359

hello_sensor_timeout:360

hello_sensor_timeout:361

hello_sensor_timeout:362

hello_sensor_timeout:363

hello_sensor_timeout:364

hello_sensor_timeout:365

hello_sensor_timeout:366

hello_sensor_timeout:367

hello_sensor_timeout:368

hello_sensor_timeout:369

hello_sensor_timeout:370

hello_sensor_timeout:371

hello_sensor_timeout:372

hello_sensor_timeout:373

hello_sensor_timeout:374

hello_sensor_write_handler: handle ff02

Command:3 State:2

ws_verify rcvd:e10a4d4f calculated:e10a4d4f

send_status 0

hello_sensor_timeout:375

a2 1a 00 6c 30 00 00 1b 33 00 00 00 00 00 00 14

1e 08 02 b0 04 00 00 00 00 00 00 00 00 72 06 00

0b 00 00 00 00 01 b3 01

0 Likes
Reply
Anonymous
Not applicable

When ota downloading was finished, not only application didn't run, but also I couldn't download application through hci interface which is traditional way for upgrade.

The only way was to recover this tag, then everything was ok.

0 Likes
Reply
Employee

OTA/uart upgrade divides the EEPROM into roughly two halves as in one of the comments in ws_upgrade.c, and if you look at this layout, it requires an EEPROM larger than 32Kbytes. The 20732 tag board comes with only a 32kbyte EEPROM, which is not enough to store two images (for fail-safe upgrade) and the EEPROM silently wraps around to the lower addresses and so corrupting the image. So use a larger EEPROM (64Kbytes) and it should work for you.

The newer 20736 and 20737 tag boards have 64Kbyte EEPROMs, so you will not have this problem with these tags (and SDK 2.0).

Anonymous
Not applicable

If I use bcm20732s module, can it be solved?

I know that bcm20732s embed an eeprom which is 512kb, 64kB.

0 Likes
Reply
Employee

Yes, the 20732S modules (S03 version that is shipping now) has a 64kbyte EEPROM and updates should wok with it.

0 Likes
Reply
Anonymous
Not applicable

I've replace from 32Kbyte to 64Kbyte EEPROM but It is not working.

Plz,Let me know how to upgrade using EEPROM

1) ws_upgrade_verify() return value is ture after ota.bin was downloaded to EEPROM

2) 20732 is not working

condition>I can't change SDK 2.0. I have to use SDK 1.1.0.

1) const WS_UPGRADE_NV_LOC_LEN nv_loc_len[2] =
{

    {
        /* .ss_loc = */     {0, 256},
        /* .ds1_loc = */    0x4C0,         // ConfigDSLocation
        /* .ds1_len = */    0x7B00,        // ~31KB
        /* .ds2_loc = */    0x8000,
        /* .ds2_len = */    0x7B00,        // ~31KB
        /* .vs1_loc = */    0x140,         // DLConfigVSLocation
        /* .vs1_len = */    0x200,         // DLConfigVSLength
        /* .vs2_loc = */    0,             // No VS2 for EEPROMS
        /* .vs2_len = */    0              // No VS2 for EEPROMS
    },

2) 20732_EEPROM.btp

DLConfigSerialControlBaudRate = 115200

DLConfigEEPROMAccessSpeed = 100

DLConfigVSOffset = 0

ConfigDSLocation = 1216

DLConfigSSLocation = 0

DLConfigIncludeBTWSecurityKey = 0

DLConfigVSLocation = 320

DLConfigVSLength = 512

DLConfigRemoteDeviceCount = 0

DLConfigBD_ADDRBase = "20732A0*****"

DLConfigFixedBD_ADDRFlag = "Can change"

OTAFWUAckAllRecords = 0

OTAFWUUpdateFirmware = 1

OTAFWUUpdateConfig =

0 Likes
Reply
Anonymous
Not applicable

This problem is cleared. I have wrong binary file

Thanks

Anonymous
Not applicable

Hi Sir,

May I ask what's the os you run for this application? Win7 or Win8?

0 Likes
Reply
Anonymous
Not applicable

I have the same error,When I open WsOtaUpgrade.exe, a error message occur: "Failed to open the patch file."

how do you fix it?

0 Likes
Reply
Moderator
Moderator

I created a new thread for this here: Why error occur when I open WsOtaUpgrade.exe?

0 Likes
Reply