Using FICR->DEVICEADDR in production?

[mlac]

Hi there,

I'm developing a product which is composed of two nRF52 devices factory-paired to each other. I want to use their BLE address as a basis for pairing. Our product will be FCC/CE certified and mass-produced.

Is it allowed to use the built-in FICR->DEVICEADDR random static address not only in development but also in the production firmware? I'm asking because I know that it's possible to register a manufacturer-specific OUI and use it as the first 3 bytes of the addresses.

If the OUI is not required, please explain why it exists and in which scenarios one would use it.

Thanks in advance!

- Laci

[Simonr]

Hi Laci

All nRF devices come with a random static address generated during Nordic production test and programmed to FICR-->DEVICEADDR. There is no problem using this address in production as long as you don't mind it being random.

The Company identifier (which I assume you're referring to) are unique numbers assigned by the Bluetooth SIG to member companies requesting one. It is not necessary to put as part of your device address, but rather as part of your advertising data/device information. The device address itself is independent of this, but when you certify a BLE product you always set a "company ID" for your device during production. More information on company identifiers for Bluetooth products can be found in the following: 

• Bluetooth Core Specification [Vol 4] Part E, Section 7.1.45 [4].
• Bluetooth Core Specification [Vol 4] Part E, Section 7.4.1 [4].
• Bluetooth Core Specification [Vol 4] Part E, Section 7.4.8 [4].
• Bluetooth Core Specification [Vol 4] Part E, Section 7.4.10 [4].
• Bluetooth Core Specification [Vol 4] Part E, Section 7.7.12 [4].
• Bluetooth Core Specification [Vol 4] Part E, Section 7.8.109 [4].
• Bluetooth Core Specification [Vol 6] Part B, Section 2.4.2.13 [4].
• Supplement to the Bluetooth Core Specification Part A, Section 1.4.1 [22].
  
  

Best regards,

Simon