Device unique ID in OTP area

Learn MoreFAQsTutorials

4 posts / 0 new
Last post
Ankit
Offline
Last seen:10 months 2 weeks ago
加入:2017-05-24 07:42
Device unique ID in OTP area

Hi, I am using DA14583 with SDK 5.0.4.

I want to program unique device ID in OPT area. By exploring OTP memory fields, I have two options.
一个独特的设备ID存储在自定义字段s ( 0x47f44 - 0x47f60 )
b.) store unique device ID in Device unique ID ( 0x47fd4 - 0x47fd8 )

My question is if I go for option b.), will there be any other effect? I mean is SDK using unique device ID field of OTP for any other purpose?

Device:
MT_dialog
Offline
Last seen:1 month 2 weeks ago
Staff
加入:2015-06-08 11:34
Hi Ankit,

Hi Ankit,

With option b) and by burning those flags, the SDK reads the OTP in that area in order to obtain the bd address. If those bytes are not equal to zero the device will get the value from the OTP. But since this is a 583 there is a seperate flag (BDADDR_FROM_DA14583_FLASH_DISABLED) in order for the device to obtain the value for the flash (if offcourse you have burned the bd address in the flash with the appropriate header). So in the 583 the device first check the flash for a bd address, if the value read back is not valid the device checks for a value in the OTP, if again that value is not valid then the device takes the bd address from the NVDS data structure.

Thanks MT_dialog

Ankit
Offline
Last seen:10 months 2 weeks ago
加入:2017-05-24 07:42
I am using .addr_src = GAPM

I am using .addr_src = GAPM_GEN_STATIC_RND_ADDR.

MT_dialog
Offline
Last seen:1 month 2 weeks ago
Staff
加入:2015-06-08 11:34
Hi Ankit,

Hi Ankit,

That means that the device wont get the values for the bd address from that field. I only mentioned that in order to be aware that in case you burn that field and you were advertising via a public address the device would obtain the bd address from that field, so you would seeing that number on the air as the bd address of the device. Apart from that i dont see any issues in doing so.

Thanks MT_dialog