DA1458X Mass production

Hi Rohit,

For mass production, please check the Production Line Tool (PLT). Up to 16 devices can be connected..

//www.wsdof.com/products/production-line-tool

Are you using this tool for the production?

Thanks, PM_Dialog

Hi Rohit,

Please check section 7.2.4 BD Addresses from the following document.

//www.wsdof.com/sites/default/files/um-b-041_da1458x_da1468x_production_line_tool_4v2.pdf

Could you please clarify what you would like to accomplish with BD address? What is your requirement in production?

Thanks, PM_Dialog

Hi Rohit,

When the PLT is used, the BD address will be programmed into the OTP Header. After that, the device will get the BD address of the OTP Header, so any other BD address in the NVDS or in application code will be ignored. During production, the code will not be affected, but as mentioned before the PLT will write the OTP header with the appropriate BD address. Regarding your last question, could you please clarify it? Please note that the OTP stands for One-Time-Programmable, thus it cannot be written multiple times.

Thanks, PM_Dialog

Hi Rohit,

If you are planning to use the PLT for the production, and in case you want to burn the BD address through the PLT, the BD address will be stored in the appropriate field of the OTP Header. This field can but burnt without the PLT as well, so if you have plenty of boards you can do some tests. You can use the use the SmartSnippets Toolbox to read and write the OTP Header.

>>>And What is the effect If I am using Flash for production?

In case of the BD address is programmed to the OTP Header? So, if I understood correctly you are using a DA14580 and a DA14583 in your design, Do you want to program both through the PLT (assume with different fw) ? And what about the BD address?

Thanks, PM_Dialog

Hi Rohit,

In all cases, if you are using the PLT to burn the BDA, then it will be stored in the OTP Header. Then the DA1458x will start advertising with the BDA from the OTH Header. Please check nvds_read_bdaddr_from_otp(). Do you mean to burn the BDA in the OTP Hader and then read it from you FW?

Thanks, PM_Dialog

Hi Rohit,

If the device BD Address is written in OTP header the CFG_NVDS_TAG_BD_ADDRESS value is ignored. If you check the system_init() function, then you will see the SDK checks and reads the BD address - nvds_read_bdaddr(). If you check the aforementioned function, you will see that :

In case if DA14583, the SDK first checks and reads BD address from DA14583's internal SPI flash - nvds_read_bdaddr_from_da14583_flash().. If no BD address is found in flash, then tries to read BD address from OTP - nvds_read_bdaddr_from_otp().

In case of DA14580, as it does not contain an embedded SPI Flash, the SDK checks only the OTP Header - nvds_read_bdaddr_from_otp().

If you read the source code of nvds_read_bdaddr_from_otp(), you will see how to read the BD Address form the OTP Header which starts from 0x7fd4 address (BDADDR_OFFSET).

Thanks, PM_Dialog

Hi Rohit,

的otp_bdaddr is mem-copied in the dev_bdaddr.

memcpy(&dev_bdaddr, otp_bdaddr, sizeof(dev_bdaddr));

If you search a little bit in the SDK, you will find the following:

/// Device BD address

struct bd_addr dev_bdaddr __attribute__((section("retention_mem_area0"), zero_init));

的otp_bdaddr is already retrieved by the SDK. So, this is up to you – you can use this function or implement you own function based on nvds_read_bdaddr_from_otp(), All you need to do is to read the correct address from the OTP.

Thanks, PM_Dialog

Hi Rohit,

Sorry, bur I am little bit confused, so could you please indicate what you are trying to accomplish? Did you burn the OTP with your firmware, or did you burn the OTP Header with a specific BDA? Just try to connect to the OTP Header from the SmartSnippets Toolbox and burn your BDA.

Still I am not completely sure if I have understood your requirement. If I understood correctly you have 2 different products. The first one in based on DA14580 and the second on the DA14583.

You would like to use the PLT and burn the OTP Header with a specific BDA. For testing purposes, you can use the SST in order to burn the BD address. Did you burn the OTP Header?

Thanks, PM_Dialog

Hi Rohit,

Apologies for the delay. Externign the dev_bdaddr could be a possible approach. The device obtains the bd address during start up, in the nvds_read_bdaddr() function (the device checks from the where the bd address can be obtained either NVDS structure or OTP) and places the obtained value in the dev_bdaddr variable that holds the address of the device.

Can you please clarify #3 step?

>>>in user_peripheral file - using dev_bdaddr->addr[5]; accessed address and assigned in advertising variable

Do you mean that you want to add the bd address in the advertising string?

As I have already mentioned, you should burn the BD Address in the OTP Header. Please use the Smart Snippets toolbox in order to read and burn the OTP Header. You will not need to burn the whole application image into OTP and boot from there

Thanks, PM_Dialog

Hi Rohit,

Sorry, probably I missed your last comment. Do you mean the steps you should follow in order to burn the BDA in the OTP Header through the Smart Snippets Toolbox?

If yes, you could use the CLI in order to burn the BD Address in the OTP Header. The CLI can be found under \5.0.4\binaries\host\windows\prod_test_cmds SDK path. The following command will write the BD Address into OTP:

prodtest -p otp wr_bdaddr

example: prodtest –p 14 otp wr_bdaddr 44:49:41:4c:4f:47

Another option might be to use the SmartSnippets Toolbox in order to burn the BD address in the OTP Header. Generally, for burning the OTP through the SST you should the OTP Programmer. Keep in mind that the latest version of the tool is recommended .

The OTP has 3 areas where the user can burn data:

• The OTP image area, where the user code is placed and mirrors to the sysram at boot.
• 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 burning the OTP, you should make sure that the programming voltage is clean and must not exceed 6.8V. Please refer to the datasheet to find more details for the programming voltage. 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.

在你的情况下,开放对海温和连接the OTP Header. As soon as you are connected, you will see the all the available field in the OTP Header. The PLT will store the BD Address in the following address in “Device unique ID” fields.

So, if you would like to test it, you should burn the BD address in the “Device unique ID” field. Please note that, the most significant (left-most) byte of a word is stored in the smallest address (big-endian). E.g. if a user types 0A0B0C0D for field ‘Device Unique ID’, 0x0A will be written at 0x47FD4 and 0x0D will be written at 0x47FD7.

Thanks, PM_Dialog