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

Smart Bluetooth

huangj
Level 4
5 likes given First like received First like given
Level 4

The OTA upgrade can't work in the WIndows 10. The following is my setting:

OS: Windows 10 Version 1703

Hardware: Tag 3 EVB

Project: sample code - ota_secure_firmware_upgrade

I also disable the power save in the power management panel.

connect.png

Here are my steps:

1. Create OTA signed file: The OTA signed file can create by WsRsaSign.exe

2. WsRsaSign command: WsRsaSign rsa.pri BLE_LVDT_NEW-BCM920737TAG_Q32-rom-ram-Wiced-release.ota.bin 3A20 1 0

    The OTA app ID(0x3A20) is same in the hello_sensor.c.

     The rsa.pri is create

3. Start OTA procedures

未命名.png

The OTA firmware upgrade stuck in the "Transfer step". The OTA step and command is working in my computer before the Windows automatically updates.Any help is appreciated.

0 Likes
1 Solution
Anonymous
Not applicable

We have noted that there is an issue with OTA update with Windows 10 version 1703 and later versions. We are fixing it.

View solution in original post

12 Replies
huangj
Level 4
5 likes given First like received First like given
Level 4

The connection request is in the 19664212 µs. I cant' see any data exchange between 19701160µs(Connection establishment) and 57321846µs in the connection.

未命名.png

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

Let me list down the steps for secure OTA:

1) Copy WsRsaKeyGen.exe, WsRsaSign.exe and WsSecOtaUpgrade.exe into a working folder

2) Execute WsRsaKeyGen.exe to generate rsa.pri and rsa_pub.c

3) Copy rsa_pub.c into the application folder in which the app will be compiled

4) Ensure the following line in makefile.mk:

    APP_SRC = application.c ws_sec_upgrade_ota.c ws_upgrade.c rsa_pub.c

5) After compiling of the application, copy "XXX.ota.bin" from the build folder into the working folder of (1)

6) Sign the image with WsRsaSign.exe, taking note of the requirement for app_ID, and major/minor IDs

7) Execute WsSecOtaUpgrade.exe on "XXX.ota.bin.signed" and perform the OTA

You must have used a BT dongle. Did you use the Widcomm SW that come with it? Does removing it help?

OTA step under Windows 10

huangj
Level 4
5 likes given First like received First like given
Level 4

Hi boont,

Thanks for your comment.

BT dongle: BCM20702A

Did you use the Widcomm SW that come with it?

=>The Widcomm is the BT dongle driver. I pair the TAG3 with Windows 10 Bluetooth interface. The Windows 10 Bluetooth interface and WsSecOtaUpgrade.exe worked fine before 2 months ago.

I try the OTA step like you say. But it still stuck in the "Transfer step". I save the log on attachments.

15:41:57 - hello_sensor_write_handler: handle ff03          =>BT dongle(Master) send data to the TAG3(Slave)

15:41:57   WriteCb: handle 0000

15:41:57 - hello_sensor_write_handler: handle ff03          =>BT dongle(Master) send data to the TAG3(Slave)

15:41:57   WriteCb: handle 0000

15:41:58 - hello_sensor_write_handler: handle ff02          =>BT dongle(Master) send data to the TAG3(Slave)

15:41:58 - Command:1 State:0

15:41:58 -

15:41:58 - send_status 0

15:41:58 -

15:41:58   WriteCb: handle 0000

I can't see any data exchange after 15:41:58(hello_sensor_timeout:16) in the log.

The following are possible problems:

1. BT dongle or TAG3 disconnect  

=> I can't see the disconnect in the log.

2. BT dongle or TAG3 can't send message

=> The BT dongle sends 3 write requests to the TAG3

3. The WsSecOtaUpgrade.exe is incompatible with Windows 10

=> The OTA cloud work with my Windows 10 computer. When my computer performs the Windows update, the OTA can't work with the Windows 10 of new version.

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

I tried out the ota process on a win10 64bit machine and experienced the same thing as you. Everything was ok until the actual upgrade execution and it hanged there during the "Transfer".

Please create a case in MyCase so that we can investigate this.

0 Likes
huangj
Level 4
5 likes given First like received First like given
Level 4

Hi boont,

I also do the same thing in my Windows7 laptop with same setting(e.g. *.signed, WsSecOtaUpgrade.exe and BT dongle). The OTA procedure can work in my W7 laptop, but it can't work in my W10 PC. It seems that this program does not support Windows 10.

Please create a case in MyCase so that we can investigate this.

=>Where can I found "MyCase"?

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

You may go to the following to click on the "Create a Cypress Support Case"

Support & Community | Cypress Semiconductor

Same here, I have no issue on my win7 PC. It seemed that it only happened recently with the latest windows update.

If possible, carry out your development on win7 for the time being.

0 Likes
Anonymous
Not applicable

Has there been any update on the status of this issue? We are having the same problem. OTA was working previously on a Window 10 1607 machine but after an automatic Windows update  to 1703 the process broke. We are having the same behavior. The module connects fine but hangs on the transfer step. We do not have any Windows 7 machines to test against.

0 Likes
huangj
Level 4
5 likes given First like received First like given
Level 4

Hi droghio,

The issue is still exist. I'm also waiting response from Cypress.There are two solutions in the moment. One is Windows 7, and the other is Android APP.

Best regards,

Jack

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

This issue is still being investigated. It is taking a little bit of time because of other priorities. At the mean time, Win7 is still the current recommended way of doing OTA.

0 Likes
Anonymous
Not applicable

We have noted that there is an issue with OTA update with Windows 10 version 1703 and later versions. We are fixing it.

huangj
Level 4
5 likes given First like received First like given
Level 4

Hi yssu,

It's very happy to hear the bug fix. Do I need to install new SDK or Utility?

Best regards,

Jack

0 Likes
Anonymous
Not applicable

Hey Jack,

I will let you know. It will mostly be a new utility, not a new SDK.