Burning OTP Device Unique ID

Learn MoreFAQsTutorials

4 posts / 0 new
Last post
Anonymous (not verified)
Burning OTP Device Unique ID

Hi,
We are trying to create unique BD address for our DUTs. In the forums it is said to program the Device Unique ID value in the OTP header.
If we burn the Device Unique ID from smart snippets can we burn other otp values (other than Device Unique ID) later on? Also how long should this be (in bytes)?
Do we have to change anything in out firmware?

Device:
IM_Dialog
Offline
Last seen:3 days 20 hours ago
加入:2016-12-06 22:25
Hi,

Hi,

The BD address programmed into OTP in 6 bytes in length. Once this is programmed it will be automatically used, no need to change anything in your firmware. You can program the BD address in the OTP and then later program other fields.

Best regards

IM_Dialog

mutahir (not verified)
Thanks for the reply the BD

Thanks for the reply the BD address in the OTP you are talking about is the Device unique ID field? or is it something else?

WI_Dialog
Offline
Last seen:2 days 6 hours ago
Staff
加入:2014-01-03 16:21
Hi,

Hi,
To be clear, BD address field refers to the data bytes stored at OTP offset starting address at 0x7fd4. The Device Unique ID field refers to the offset starting at 0x7f54 which is defined as "Customer Specific Field" for holding customer's defined information. The usage of this field is up to customers' firmware.
Read-Modify-Wri更新任何OTP头。te" approach is employed in Smart-Snippets software so as to avoid writing to un-intended field by accident. The sequence is to: Read the OTP header, write the intended field and then update the OTP header. OTP bit can only turn from '0' to '1, not the other way round.
Regards,