Where can I get the doc AN-B-020  DA14580 End product testing and programming guidelines.pdf

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 https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
2 posts / 0 new
Last post
Last seen: 2 years 4 months ago
Joined: 2019-06-27 07:57
Where can I get the doc AN-B-020  DA14580 End product testing and programming guidelines.pdf

I built a hex file to download to OTP, but the hex file is not corret.

I need followed document. Where can I get this doc?

AN-B-020 DA14580 End product testing and programming guidelines.pdf

Last seen: 6 months 3 weeks ago
Joined: 2018-02-08 11:03
Hi louwy001,

Hi louwy001,

The AN-B-020 document is quite old and is not available any more on our support website. If you are starting a new design, we would recommend to start with the DA14585 – the SDK and the documentation is much improved, we have a lot of code examples, and there is also software roadmap support on the DA14585 to our next generation device that is announced 5th November.

In general, the procedure you should follow in order to burn the OTP is the following:

You should you the OTP Programmer from the SmartSnippets toolbox (latest version is recommended) .

  1. The OTP has 3 areas where the user can burn data:
  2. The OTP image area, where the user code is placed and mirrors to the sysram at boot.
  3. The OTP NVDS area, where the NVDS structure is populated with the OTP at boot.

The OTP Header area, where flags and specific values that define the operation of the device are placed (more information regarding the values of the OTP Header can be found in the Smart Snippets User guide).

When the user tries to burn the OTP he have to make sure that the programming voltage is clean and must not exceed 6.8V. Also the 6.8V can only be applied to VPP after the VBAT3V is supplied and must be removed from VPP before the VBAT3V is removed, otherwise the chip could be damaged.

In order to burn the OTP with the most common configuration please follow the below instructions:

  1. Open Smart Snippets either via JTAG or UART and hit open.
  2. From the tool bar button choose the OTP programmer in order to open 3 different tabs, one for each OTP area.
  3. Choose the OTP image tab and on the left tab browse to the .hex file you would like to burn and hit Burn.

As soon as the last step is complete you will have burned your custom's board OTP. Some additional configurations are required in order for your device to boot from it.

  1. Go to the OTP Header tab.
  2. Change both of the application flags to YES (this is required in order to start the booting from OTP, when one does that the primary bootloader is disabled - scan of the peripherals for valid image, the user can reprogram his board using JTAG only).
  3. Hit the burn Button in order to burn the configuration to the OTP Header.
  4. The above steps are enough in order for the user to program the OTP

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 sysram though via JTAG as long as the OTP header field called JTAG enable flag stays Enabled.

NOTE: If the application flags are burned and the JTAG enable flag is Disabled then the device becomes inaccessible.

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.

Thanks, PM_Dialog