CC2640R2F: dose oad impact osal_read?

dsp999

Expert 1495 points

Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2541

I save some data by osal_snv_write, and verified by osal_snv_read.

then I oad, success, run a new bin, then osal_snv_read the same address, strange get 0, correct?

over 4 years ago

0 J Lindh over 4 years ago

TI__Guru 57865 points

Hi,

It's not strange if you also copy over that location in flash.

0 dsp999 over 4 years ago in reply to J Lindh

Expert 1495 points

ok, in CC2541, data is preserved.

I have checked oad document, looks like there is a way to keep the data, isn't it?

0 YiKai Chen over 4 years ago in reply to dsp999

Guru 735455 points

It shouldn’t be overwrite after OAD unless you change memory map.

0 dsp999 over 4 years ago in reply to YiKai Chen

Expert 1495 points

eh....your answer and Joakim's answer are different.

0 YiKai Chen over 4 years ago in reply to dsp999

Guru 735455 points

If you have a look at memory map at http://dev.ti.com/tirex/content/simplelink_cc2640r2_sdk_1_40_00_45/docs/blestack/ble_user_guide/html/cc2640/memory_management.html, SNV shouldn’t be changed by OAD process.

0 J Lindh over 4 years ago in reply to dsp999

TI__Guru 57865 points

Hi,

My comment was more related to the fact that our customers typically modify our sample applications. Based on you response, I suppose you haven't changed/modified the OAD sample code? If so, SNV should be retained but as YK indicates, you should be able to confirm with the map file.

Bluetooth®︎

Bluetooth forum

CC2640R2F: dose oad impact osal_read?