Same UUID for different daughterboards

⚠️
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.wsdof.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
2 posts / 0 new
Last post
ghschwab
Offline
Last seen:6 months 2 weeks ago
加入:2016-07-25 10:54
Same UUID for different daughterboards

Hi,

we are developing different applications for the Dialog DA14681 and are experiencing some issues.
We are using the same kind of daughterboard for the different developments, but the software on my iPhone detects either of the daughterboards without being able to distinguish them. This must have to do with the devices UUID. How do we change the UUID so the daughterboards appear as different entities?
Also, how does this work later in production? Where do we obtain a valid UUID and how do we program the devices?

Thank you very much!

Best regards,
Gunther Schwab

Device:
MT_dialog
Offline
Last seen:2 months 2 weeks ago
工作人员
加入:2015-06-08 11:34
Hi ghscwab,

Hi ghscwab,

Each BLE device is distinguished by its BLE address, on the 68x SDK when the device is using a public address the device will take the BD address from the NVMS_PARAM_PART of the flash, if there is no valid address in that part then the device will read a static address from a default value stored in the SDK at the defaultBLE_STATIC_ADDRESS definition. Regarding production the PLT is taking care of the bd address with different kind of schemes please check the production line tool documentation. If not using the PLT tool one should write that specific part of the partion in the flash in order for the device to obtain the bd address. In the SDK a script is also included in order to write that specific partion, in the pxp_reporter project in the config folder in the platform_nvparam_values.h file if you change the value of the TAG_BLE_PLATFORM_BD_ADDRESS and then use the program_qspi_nv_param_win you will write the corresponding file in the parameters partition.

Thanks MT_dialog