DA14580 OTP

OTP programming using DA-14585 basic dev kit

Mon, 2020-12-14 11:41 -- Hassan


I have two questions:

1. Can use a DA-14585 basic dev kit to program (OTP) a custom board which is using a DA-14580 chip (via JTAG)?

2. I have added a jumper to the J8 pins which is done for OTP programming, but when I check the voltage at TP2 (which is meant to be 6.8V) it is 0V, am I missing something? Do you know what could be the issue that I am not getting my 6.8V? Has the TP which outputs the 6.8V changed from the DA-14580 basic dev kit? (I had one and the voltage was output at TP2).


Firmware configuration for OTP

Tue, 2018-04-17 17:07 -- tonyb


I have a firmware project in Keil that I need to generate a hex file from for OTP burning. I am confused about the configuration in the firmware, namely what changes (if any) are required for OTP. I have found the following variable in da1458x_config_advanced.h:


Does this variable need to be defined in order to burn the firmware to OTP? Are there any other changes that need to be made? The firmware has been developed from ble_app_peripheral from the DA14580 SDK.



Fri, 2017-06-02 11:00 -- chanmi168


I have successfully burned DSPS firmware to DA14580. My iOS app can successfully connect to it (I can discover the services and three characteristics), but I do not see any change in DA14580 P0.3 (UART RTS). During development, I could see a LOW signal every ~100ms before connection and every ~25ms after connection. Have you guys seen anything similar to this behavior?

The area whehe user can set data in OTP header area.

Thu, 2016-03-10 08:56 -- Coral0310

Dear Sirs,

I have a question about OTP header area.

I want to set the data which size total is 17 bytes on the OTP header area.
I know, it is usable from 0x47F54 to 0x47F60, but the chip maker said following area can not use.

-0x47FDC to 0x47FF0

If so, it is 9 bytes short.
I'm looking for the another memory address which can freely set data.

Could you tell me memory address or another solution?

Best Regards.


Wed, 2016-01-06 09:17 -- vikramtheone

I would like to understand what would happen if I have #undef READ_NVDS_STRUCT_FROM_OTP in my application and burn my application into the OTP.

To put it in other words, I would like to understand if we are burning an application into OTP is it a MUST to have READ_NVDS_STRUCT_FROM_OTP defined?

I'm in the middle of understanding how to:
1. Go about with loading an application into SRAM from OTP.
2. Booting from OTP (Normal mode)

Ho to write a new OTP default Header

Mon, 2016-01-04 15:45 -- fontamiHw

Hi Dialog.
I'm using a DA14580 Development Kit - Expert with DA15480_CB_PXI_WLCSP...

I wrote an Otp Header with the address 0x47f00 and 0x47f0a with YES value.
From that point I alway have in the SmartSnippet tool that value grayed, and not possible to change.
I lost also the functionalities of the "Booter" tab via UART, because it does not detect the pressing of the reset button.

I think because the OTP configuration remove the Bootmode.

Subscribe to RSS - DA14580 OTP