DA14585 Unique ID and OTP Programming

⚠️
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.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
2 posts / 0 new
Last post
Wed, 2020-02-05 06:28
#1
ltdev
Offline
Last seen:2 months 1 week ago
加入:2018-11-12 09:19
DA14585 Unique ID and OTP Programming

Hi;

1-) Is there DA14585 chip has unique ID (chip id)? How can i access it?

2)我们如何佛罗里达州h da14585 otp memory.

3-) can the otp header be rewritten?

Best Regards...

Device:
DA14585
Thu, 2020-02-06 13:22
PM_Dialog
Offline
Last seen:2天4分钟前
工作人员
加入:2018-02-08 11:03
Hi btdev,

Hi btdev,

  1. Please used the SmartSnippets Toolbox (SST) to connect and read the OTP Header. As you can see, there isn’t any available unique chip ID place in the OTP Header. The SST is available on our support website. We recommend the latest version of the too; (version 5.0.10). If you are not familiar with SST, please refer to theUM-B-083 SmartSnippets Toolbox User Manual (HTML). Unique ID can be achieved during run time enabling security in the code. Please check default_app_generate_static_random_addr() function.
  2. You should use the SST for OTP programming. In the OTP header you should change both of the application flags to YES. The application image should be burnt into in the “OTP Image” tab.
  3. Keep in mind that OTP stands for One Time Programmable, thus you can’t erase and re-write the OTP multiple times, but you can only flip the bits that are still set to 0 and turn them to 1. When the OTP is burned and the application flags on the OTP header are also burned, the primary bootloader is disabled so the scanning procedure doesn't take place, thus you will not be able to boot from the SPI or UART or I2C. You will be able to directly burn your SystemRAM though JTAG as long as the OTP header field called JTAG enable flag stays Enabled. If the application flags are burned and the JTAG enable flag is Disabled then the device becomes inaccessible.

Generally, if you are starting a new design, we would strongly recommend to move into DA14531 product and our newest SDK6.0.12, as it is much more improved.

//www.wsdof.com/products/connectivity/bluetooth-low...

Thanks, PM_Dialog