• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 52 subscribers
  • Views 3023 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MAC address at mass production

Koichi Matsuo
Prodigy 180 points
Other Parts Discussed in Thread: CC2650

Regarding programming MAC address on CC2650, I would like to verify the step for customer support.

Our customer's step at mass production

---------------------------------------------------------------

1) Buy unique address from IEEE.

2) Program above unique mac address to Customer Configuration (CCFG) of each device.

* Currently the area of sample code like SensorTag is written all 0xFF. When I read BD address using GAPRole_GetPrameter, the vale is 0x68C90B055D82.

Since this is NOT random address with Tx Add =0 in Adv PDU Header, I guess that BLE stack automatically generate this address inside. If my understanding is not correct, would you correct me?

 

Questions

Is it necessary to set unique address bought from IEEE at 1st start up when our customers start mass production?

Currently BLE stack automatically seems to generate unique address due to 0xFF value of Customer Configuration (CCFG).

If 0xFF is not written in CCFG, does BLE stack stop to generate unique address and then can they activate with unique address written in CCFG?

At debug display

Regards,

Koichi

  • 0
    TI__Guru** 105180 points
    Hello Koichi,

    The CC26xx is factory programmed with a unique Bluetooth device address by TI. There is no need for you to purchase an address.
    Please see "9.2 Factory Configuration (FCFG)" in the CC26xx TRM (SWCU117).

    Best wishes
  • 0 in reply to JXS
    Prodigy 180 points
    Hello JXS,

    Thank you for your prompt response.

    According to your suggestion, I checked "Factory configuration's chapter".
    Consequently, although offset address of each parameter is written, I could not find top's absolute address.

    I would appreciate it if you comment whether or not I can see the values with Memory Browser in debug display of CCS.

    Regards,
    Koichi
  • 0 in reply to Koichi Matsuo
    TI__Guru** 105180 points
    Hi Koichi,

    The memory map is detailed in Sec 3.2.8 Cortex-M3 Memory (Rev F of the TRM).

    Refer to FCFG1 - Factory Configuration Area 1 at 0x50001000.

    Best wishes
  • 0 in reply to JXS
    Prodigy 180 points

    Hello JXS,

    Thank you for teaching.

    According to your suggenstion, checked "AdvA address" at Sniffer.

    and then could verify at "Memory Browser".

    Regards,

    Koichi