⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
2 posts / 0 new
Last post
Mon, 2017-06-26 02:45
#1
guxiang
Offline
Last seen:1 week 3 days ago
加入:2017-05-12 04:18
OTP function

hi , dialog
We want to store some data into OTP region of DA14681.
1. Can we write data to the OTP specific address , and erase the same specific address and then write it again for many times? If we can , how many erase/program cycles they have?

2. How to operate the OTP ? with SDK or some external program tools?

3.According to the datasheet , there is 64KB OTP in da14681. Is that mean we can erase/write any address between 0x7F80000~0x7F90000? And is there any specific region in OTP which stored some system important data that we can't erase?

Device:
DA1468x
Mon, 2017-06-26 15:36
MT_dialog
Offline
Last seen:2 months 2 weeks ago
Staff
加入:2015-06-08 11:34
Hi guxiang,

Hi guxiang,

1. OTP stands for one time programmable, that means you can only program it one time and not multiple times. After the OTP is burned you can only turn the 0's to 1's

2. You can burn the OTP via the Smart Snippets tools, there is an OTP burner tool, but there is no implementation from the SDK side to read custom data from the OTP, the SDK uses only flash in order to read custom data.

3. As mentioned above the OTP stands for one time programmable, you can only burn it once, you can not erase it or re-write it. There is the OTP header where it is designed to hold important data for the system, trim values, configurations etc, but not customer specific data. And in general for code and data storage the flash is being used and not the OTP.

Thanks MT_dialog