Hi,
We want to burn our BD address on the OTP do we just use the BD address option in the Memory header option in the PLT software?
问候
设备:
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.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
Hi mutahir,
Depending on which version of the PLT sw that you are using you can check the UM-B-041 DA1458x DA1468x Production Line Tool pdf (version 3.0 and 4.0, the title of the document is the same for both versions but there are two different documents for the different versions of the sw), for the latest version please check the 6.2.8.2 paragraph and for the older version please check the 7.8 paragraph.
Thanks MT_dialog
If we enable the "write" option where is the BD address written is it in the OTP parameters or is written as the UNIQUE DEVICE ID field in the OTP header?
Previously we have been writing the Device Unique ID field in the OTP header and the firmware automatically uses that to generate the BLE address.
So is this the same or do we need to enable using this BD address specifically in our firmware?
Hi mutahir,
The SDK when the device has booted and started, it will check the OTP Header (the Device Unique ID field) for a non-zero bd address, if it finds one, it will use this address as the device's address, if not it will get the bd address that is written in the NVDS structure (which can be populated either via the OTP or via the fw). So the bd address is written in the OTP Header in the Device unique ID field, this is where the PLT tool writes the bd address.
Thanks MT_dialog