How is the Bluetooth address programmed and where is it stored (OTP)? Is this something that must be done in production? is there a document that describes the process?
It depends on what kind of address you would like (public, random, which are also devided in other subcategories). The random addresses are generated either by stack or by your application so you dont have to do anything about that (i mean you dont have to set a static value anywhere). Regarding the public addresses, those are static, so you have to hardcode it somewhere in your system. The available places to do this is, the NVDS structure or the OTP Header. For the OTP header you can burn the Device unique ID flag and the SDK will use that to generate its bd address. Regarding the NVDS structure, there are two places to fill in this structure, either via a hardcoded value in your code, at the CFG_NVDS_TAG_BD_ADDRESS definition and the device will use the data from your fw to fill in the NVDS structure (by defining the CFG_INITIALIZE_NVDS_STRUCT), or you can burn the OTP's NVDS structure and fill the NVDS from the OTP by undefining the above definition. There is no document, like a tutorial, to describe this or the procedure, its quite straight forward.
Hi sfullam,
It depends on what kind of address you would like (public, random, which are also devided in other subcategories). The random addresses are generated either by stack or by your application so you dont have to do anything about that (i mean you dont have to set a static value anywhere). Regarding the public addresses, those are static, so you have to hardcode it somewhere in your system. The available places to do this is, the NVDS structure or the OTP Header. For the OTP header you can burn the Device unique ID flag and the SDK will use that to generate its bd address. Regarding the NVDS structure, there are two places to fill in this structure, either via a hardcoded value in your code, at the CFG_NVDS_TAG_BD_ADDRESS definition and the device will use the data from your fw to fill in the NVDS structure (by defining the CFG_INITIALIZE_NVDS_STRUCT), or you can burn the OTP's NVDS structure and fill the NVDS from the OTP by undefining the above definition. There is no document, like a tutorial, to describe this or the procedure, its quite straight forward.
Thanks MT_dialog