OTA Transfer Freeze: BCM20736

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

cross mob
lock attach
Attachments are accessible only for community members.
hachc_2293006
Level 2
Level 2
First like received First like given
Random OTA transfer Freeze
Hello,
I could able to perform OTA transfer for 20736 chipset. But there is random freeze in transfer.
But whenever , the transfer is through OTA is successful.

Setup:
- using WsOtaUpgrade.exe
-
Satechi USB 4.0 Bluetooth Adapter  [BCM20XXX]
- Generated ota bin file.

Scenario:
- Perform Fresh down load of initial version software 0.6
- Initiate ota transfer from PC version 0.7
- First transfer happens properly.
- Again after Reset, revert back to 0.6 thourgh OTA. This goes fine.
- Then, subsequent ota trasnfer creates random freeze in between transfer.
- The sequence was repeated again and again with reset to target hardware. After 10 reset and restart the ota goes through complete sucessfully.
- then all subssequent ota transfer are with freeze.at random point of transnfer.

Attached debug message from both cases.
0 Likes
1 Solution

Thanks for your valuable support.

Found  issue; we need to disable "Allow the computer to turn off this device to save power" in ‘Power Management’ for dongle.

I referred follwing Re: Why error occur when I open WsOtaUpgrade.exe?

Now can perform OTA for mor ethan 8 times , by switching between version without glitch.

I also retaitned the PAtCH in make file.

THanks again

haric

View solution in original post

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

In your code, did you include any checks to ensure that the new version number must be always be higher than the current one?

BoonT_56
Employee
Employee
500 likes received 250 likes received 100 likes received

And what is the respective size of your 0.6 and 0.7 FW?

0 Likes

Size is around 15.5Kb. Also I use 64KB EEPROM

0 Likes

I tried a few times on my tag boards, back and forth on the versions, but were not able to reproduce the issue. You are not using the sip module and so the setup should be quite similar to my tag. Did you make any modification to ws_upgrade_ota.c and ws_upgrade.c? Can you try using them stock?

Can you also add the below to the makefile?

APP_PATCHES_AND_LIBS += thread_and_mem_mgmt.a

Thanks,

There were no modifications made to ws_upgrade_ota.c and ws_upgrade.c files.

Also tried the patch.

Still the same result.

Also tried "OTA firmware upgrade " example on TAG4 board. I did experience same issue.

0 Likes

Let me just outline a little:

Tools: tag3, 20702 based dongle, and WsOtaUpgrade.exe on win7 32-bit PC

1) Using the stock ota_fw_upgrade app, download default FW with minor version as 1

2) Assume bt dongle is connected to tag

3) execute "clean" follow by a "build"-only of the same app, with minor version changed to 2. I also changed the broadcast name

from "Broadcom" to "Broadcon".

4) Cut and save the generated BIN file to a folder, along with WsOtaUpgrade.exe

5) Execute in win console (with admin rights): WsOtaUpgrade.exe xxx.bin

6) Observe a UI appeared, and "Start" it

Then I go back to "1" and then "2", and I had success for 6 times. I noted

that in the sixth time, the download did not start, but that's because the

RF link was down. From the Bluetooth Manager, I removed and added my tag

again, and I was able to proceed with the download.

BoonT_56
Employee
Employee
500 likes received 250 likes received 100 likes received

Correction: The default broadcast name was "Hello" and I changed it to "Helle". And NOT Broadcom as I stated above.

0 Likes

Thanks for your valuable support.

Found  issue; we need to disable "Allow the computer to turn off this device to save power" in ‘Power Management’ for dongle.

I referred follwing Re: Why error occur when I open WsOtaUpgrade.exe?

Now can perform OTA for mor ethan 8 times , by switching between version without glitch.

I also retaitned the PAtCH in make file.

THanks again

haric

0 Likes