Hello,
Hello,
Hi Joe
The nRF52 won't come with a "preprogrammed" MAC address, and you need to flash it onto the board if you don't want to use CONFIG_BT_PRIVACY to generate the address for you. Since it's not set, you can write BT_ID_DEFAULT to be whatever you'd like and it should be set up. I'm sorry, if I'm misunderstanding, but I don't really see the problem here.
Best regards,
Simon
Hi Joe
The nRF52 won't come with a "preprogrammed" MAC address, and you need to flash it onto the board if you don't want to use CONFIG_BT_PRIVACY to generate the address for you. Since it's not set, you can write BT_ID_DEFAULT to be whatever you'd like and it should be set up. I'm sorry, if I'm misunderstanding, but I don't really see the problem here.
Best regards,
Simon
Hi Simon,
Okay that makes sense now. Having a unique static address that's readable from the get-go is valuable to me because it's a really easy way to allow the app-side to identify the device. I can randomize BT_ID_DEFAULT and store it in NVS.
Thanks!
EDIT: Sorry, could you please clarify, is this a nRF52 DK behaviour, or a nRF52832 in general behaviour?