Its the default dehaviour of Smart Snippets, since the SDK reads the bd address from the OTP header first and then from the OTP NVDS. Since you burn the OTP you should burn the OTP header as well, therefore store the bd address to the OTP header in the Device unique ID field instead of the OTP NVDS.
I dont get what you mean "What is the Unique ID format" If you want your device to have this address, this is what you should burn at the specific field. If you would like your device to show in your phone as 12:34:56:78:90:AB you should place the values in the field in the following way:
正如上面提到的,the SDK will check the OTP Header for an available bd address and if it doesn't find anything (zeros) it tries to get the bd address from the NVDS. Now since you have programmed the OTP header the SDK will never look at the NVDS for a bd address. So if you burn the bd address in the OTP header you dont have to burn it to the OTP NVDS. You can burn it and check it while you are in development mode without burning the image in the OTP or the application flags, just Device id field.
Hi MT_dialog, I have a doubt that wether i can modify the fields of NVDS(such as NVDS_TAG_BD_ADDRESS, NVDS_TAG_APP_BLE_ADV_DATA ...) in my program dynamicly, even if firmware burned.
Hi daniel59,
Its the default dehaviour of Smart Snippets, since the SDK reads the bd address from the OTP header first and then from the OTP NVDS. Since you burn the OTP you should burn the OTP header as well, therefore store the bd address to the OTP header in the Device unique ID field instead of the OTP NVDS.
Thanks MT_dialog
What is the Unique ID format? If I want to let my chip bd address 12:34:56:78:90:AB ?
Hi daniel59,
I dont get what you mean "What is the Unique ID format" If you want your device to have this address, this is what you should burn at the specific field. If you would like your device to show in your phone as 12:34:56:78:90:AB you should place the values in the field in the following way:
0x47FD4 AB:90:78:56
0x47FD8 34:12:00:00
Thanks MT_dialog
So i dont have to change the value in OTP NVDS?
Hi danilel59,
正如上面提到的,the SDK will check the OTP Header for an available bd address and if it doesn't find anything (zeros) it tries to get the bd address from the NVDS. Now since you have programmed the OTP header the SDK will never look at the NVDS for a bd address. So if you burn the bd address in the OTP header you dont have to burn it to the OTP NVDS. You can burn it and check it while you are in development mode without burning the image in the OTP or the application flags, just Device id field.
Thanks MT_dialog
Hi MT_dialog,
I have a doubt that wether i can modify the fields of NVDS(such as NVDS_TAG_BD_ADDRESS, NVDS_TAG_APP_BLE_ADV_DATA ...) in my program dynamicly, even if firmware burned.
Hi zuma,
Please check you other posthttps://support.dialog-semiconductor.com/using-nvdsputregarding your question.
Thanks MT_dialog