OAD partition abnormality

Kuo Austin

Prodigy 110 points

Other Parts Discussed in Thread: CC2650

Hi All

Thousands of my products have been sold.

First time encountering this issue.

Described as follows：

1、I have used OAD to implement OTA to update fw. (Internal flash)

2、I dumped this failed cc2650 flash. (Back from my customer)

3、Compared with normal flash.

4、I found a difference in the OAD partition. (Address：0x0 ~ 0x00b18)

This device works normally at first.

After a few days of use and no OTA update FW.

This device suddenly stopped working.

I'm confused.

My fw should not be able to modify the contents of the OAD partition, right?

over 2 years ago

0 Ryan Brown1 over 2 years ago

TI__Guru**** 222737 points

Hi Kuo,

The zstack_home_1_02_02a_44539 software for the CC2650 does not include an OAD solution, so I assume you developed the OAD code independently. Knowing nothing about your application, it is possible that there are corrupted flash write commands or the supported flash erase cycles before failure has ben exceeded. Notice how one to four bits have been flipped for each instance.

Regards,
Ryan

0 Kuo Austin over 2 years ago in reply to Ryan Brown1

Prodigy 110 points

Thanks for your reply.

Are you meaning that zstack 1.2.2a SDK does not support OAD?

How do users update firmware via OTA?

Are they all developed by themselves?

0 YiKai Chen over 2 years ago in reply to Kuo Austin

Guru 735695 points

OAD is software task. Ryan just tell you TI zstack_home_1_02_02a_44539 software doesn't provide Zigbee OAD example but you still can implement it by yourself.

0 Kuo Austin over 2 years ago in reply to YiKai Chen

Prodigy 110 points

Thanks, I understand.

The latest info.

My customer measured the power of this device before the exception.

Is it possible that measuring power may cause flash data abnormalities?

0 YiKai Chen over 2 years ago in reply to Kuo Austin

Guru 735695 points

Basically, you can use ADC to check if VDD is good enough for flash write before your application does flash write.

0 Ryan Brown1 over 2 years ago in reply to Kuo Austin

TI__Guru**** 222737 points

Power supply fluctuations can certainly cause unexpected device shutdown while actively performing a NV flash write, which could potentially corrupt flash memory. This is why modern solutions on SimpleLink CC13X2 / CC26X2 devices implement a feature which measures the power supply to confirm it is above a threshold, typically at least 2000 mV, before writing to NV memory.

Regards,
Ryan

Zigbee & Thread

Zigbee & Thread forum

OAD partition abnormality