Re: WICED Smart BCM92073X OTA Firmware Upgrade (Question)

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

cross mob
Anonymous
Not applicable

Hello,

Per this article: WICED Smart BCM92073X OTA Firmware Upgrade (2)

Thanks for your article. It is really helpful, but we are kind of stuck at a particular position.

The things seem to work fine till we send the firmware length. But when we tried to send the firmware info,  we are getting the call in onCharacteristicWrite() but the value is not getting written to the device.

I am using a BLE device "Anaren A20737A" and connected with it using PUTTY. I am also sharing the debug traces visible in putty.

The correct debug traces should be like -

command == WS_UPGRADE_COMMAND_PREPARE_DOWNLOAD

send_status 0

write_handler: handle ff02, len 5

Command:2 State:1

Active: 0x00000580, Upgrade: 0x00008000, UG length: 0x00007A00

state:2 total_len:29040

send_status 0

write_handler: handle ff05, len 4

ws_upgrade_info 3a19 02 05

WsUpgradeAppInfo 3a19 02 04

where -

3a19 is application id

02 - major version

04 - minor version

OTS issue.png

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

I am using the SDK with secure OTA performed on my tag4 board. I used a 2070x BT dongle together with the win7 peer app to get into the central role. I cannot reproduce your issue and my log is as below:

hello_sensor_write_handler: handle ff03

15:19:03   WriteCb: handle 0000

15:19:03 - hello_sensor_write_handler: handle ff02

15:19:03 - Command:1 State:0

15:19:03 -

15:19:03 - send_status 0

15:19:03 -

15:19:03   WriteCb: handle 0000

15:19:03 - hello_sensor_write_handler: handle ff02

15:19:03 - Command:2 State:1

15:19:03 -

15:19:03 - Active: 0x00000580, Upgrade: 0x00008000, UG length: 0x00007A00

15:19:03 - state:2 total_len:13274

15:19:03 -

15:19:03 - send_status 0

15:19:03 -

15:19:03   WriteCb: handle 0000

15:19:03 - ws_upgrade_info 0118 00 00

15:19:03 -

15:19:03   WriteCb: handle 0000

15:19:03 - ws_upgrade_info 1aa2 00 6c

15:19:03 -

15:19:03   WriteCb: handle 0000

15:19:03 - ws_upgrade_info 0004 00 00

15:19:03 -

15:19:03   WriteCb: handle 0000

15:19:03 - ws_upgrade_info 1700 69 02

15:19:03 -

15:19:03   WriteCb: handle 0000

15:19:04 - ws_upgrade_info 0100 80 02

15:19:04 -

15:19:04   WriteCb: handle 0000

15:19:04 - ws_upgrade_info 1400 11 20

15:19:04 -

15:19:04   WriteCb: handle 0000

15:19:04 - ws_upgrade_info 080a 00 28

15:19:04 -

15:19:04   WriteCb: handle 0000

15:19:04 - send_status 9

15:19:04 -

15:19:04 - ws_upgrade_info 0000 0a 08

15:19:04 -

15:19:04   WriteCb: handle 0000

15:19:04 - hello_sensor_write_handler: handle ff02

15:19:04 - Command:7 State:2

15:19:04 -

15:19:04 - send_status 0

15:19:04 -

15:19:04   WriteCb: handle 0000

15:19:04 - hello_sensor_timeout:90

15:19:05 -

15:19:05 - hello_sensor_timeout:91

This thread appeared to discuss something similar to yours. Let me know if it helps.

Re: OTA issue with new image size and DSx length

Are using the Anaren Atmosphere? I have included airlinepilot_md​ and kgillespie​ here too.

View solution in original post

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

I am using the SDK with secure OTA performed on my tag4 board. I used a 2070x BT dongle together with the win7 peer app to get into the central role. I cannot reproduce your issue and my log is as below:

hello_sensor_write_handler: handle ff03

15:19:03   WriteCb: handle 0000

15:19:03 - hello_sensor_write_handler: handle ff02

15:19:03 - Command:1 State:0

15:19:03 -

15:19:03 - send_status 0

15:19:03 -

15:19:03   WriteCb: handle 0000

15:19:03 - hello_sensor_write_handler: handle ff02

15:19:03 - Command:2 State:1

15:19:03 -

15:19:03 - Active: 0x00000580, Upgrade: 0x00008000, UG length: 0x00007A00

15:19:03 - state:2 total_len:13274

15:19:03 -

15:19:03 - send_status 0

15:19:03 -

15:19:03   WriteCb: handle 0000

15:19:03 - ws_upgrade_info 0118 00 00

15:19:03 -

15:19:03   WriteCb: handle 0000

15:19:03 - ws_upgrade_info 1aa2 00 6c

15:19:03 -

15:19:03   WriteCb: handle 0000

15:19:03 - ws_upgrade_info 0004 00 00

15:19:03 -

15:19:03   WriteCb: handle 0000

15:19:03 - ws_upgrade_info 1700 69 02

15:19:03 -

15:19:03   WriteCb: handle 0000

15:19:04 - ws_upgrade_info 0100 80 02

15:19:04 -

15:19:04   WriteCb: handle 0000

15:19:04 - ws_upgrade_info 1400 11 20

15:19:04 -

15:19:04   WriteCb: handle 0000

15:19:04 - ws_upgrade_info 080a 00 28

15:19:04 -

15:19:04   WriteCb: handle 0000

15:19:04 - send_status 9

15:19:04 -

15:19:04 - ws_upgrade_info 0000 0a 08

15:19:04 -

15:19:04   WriteCb: handle 0000

15:19:04 - hello_sensor_write_handler: handle ff02

15:19:04 - Command:7 State:2

15:19:04 -

15:19:04 - send_status 0

15:19:04 -

15:19:04   WriteCb: handle 0000

15:19:04 - hello_sensor_timeout:90

15:19:05 -

15:19:05 - hello_sensor_timeout:91

This thread appeared to discuss something similar to yours. Let me know if it helps.

Re: OTA issue with new image size and DSx length

Are using the Anaren Atmosphere? I have included airlinepilot_md​ and kgillespie​ here too.

0 Likes