No static BD_ADDR on nRF9160dk

[PopradiArpad]

Hi,

I want to use Bluetooth Mesh on the nRF9160dk and the mesh stack seems to work
(I can provision and use a model with nRF Mesh 2.4.1) but when I provision a second nRF9160dk
that setup overwrites the one of the unit before.
I use HCI UART on the nRF52840.

The only strange thing which I found is that the BD_ADDR of nRF9160dk is different at each turn on.
According this HCI UART should have static BD_ADDR when

CONFIG_BT_PRIVACY=n

and the controller has a factory BD_ADDR.

HCI UART has CONFIG_BT_PRIVACY=n.

Does the nRF5280 in the nRF9160dk have a factory BD_ADDR?
If yes, how can I use it?
If not, how can I write it (only for test on the dk, not for production)?

Best regards,
Árpád

[Amanda Hsieh]

Hi Árpád, 

Please try my colleague Hung's solution in this post, and let me know it can help or not. Thanks. 

-Amanda H.

[PopradiArpad]

Hi Amanda,

thank you for your fast reply. The link solves the random static address problem but not my original.

I assume that's a wrong mesh implementation by me, so I close this issue.

[PopradiArpad]

Hi Amanda,

the problem was the same hardcoded Device UUID :). I mixed up the BLE BD_ADDR with the mesh Device UUID as identificator.