CC3301: Writing MAC address to cc3301 chip using calibrator tool

Part Number: CC3301

 

 

Details from previous ticket:

Number: CS3175999
Contact: Heikki Kujala
First name: Heikki
Last name: Kujala
Short description: Custom Base MAC Address
Email: heikki.kujala@bittium.com
Language: English
State: Open
Provide case details or comments:

Technical & design support -> Product-specific information

Calibrator Tool — Linux CC33XX User's Guide 01.00.00.09 documentation states that calibrator tool can be used to write MAC address into cc3301.

The MAC Address can be programmed with the following:

calibrator wlan0 cc33xx_plt set_efuse -mac_addr xx:xx:xx:xx:xx:xx -token <TOKEN_ID>

How to request valid token to enable writing? 

Is it always minimum 3 MAC addresses needed for chip or can we configure cc3301 so that only AP and BLE are in use and 2 MACs are enough?

 

In short:

1- How can I obtain valid TOKEN so I can try writing mac address to chip

2- How to limit needed MAC address to 2. One for AP and one for BLE.

 

Heikki

 

 
  • Hi Heikki,

    1. Please contact your Field Application Engineer contact for a valid token ID, they should be able to provide this to you.
    2. By default, there should be 2 MAC addresses burned-in to the device, so the minimum would be 2 MAC addresses. The third MAC address is optional. You can read more information in the Mac Address Allocation section of the User's Guide under Wi-Fi Fundamentals.

    Please let me know if you have any additional questions!

    Best Regards,

    Josh Prushing

  • The documentation is misleading.

    There is one MAC address programmed into EFuse. That MAC address is used for Wi-Fi. BLE uses that same MAC address, plus 1. So there is one MAC address programmed, and two addresses are allocated from it.

    Calibrator tool lets you program one MAC address. That MAC address overrides the one in EFuse. It becomes the new Wi-Fi MAC, and BT will be that address plus 1. There is no mechanism to program more than one MAC address. If you are going to program MAC addresses, be sure to account for the fact the usage of MAC+1.

    The additional MAC addresses are created by setting the Locally Administered bit on the base MAC, and base MAC+1.

  • The documentation is misleading.

    There is one MAC address programmed into EFuse. That MAC address is used for Wi-Fi. BLE uses that same MAC address, plus 1. So there is one MAC address programmed, and two addresses are allocated from it.

    Calibrator tool lets you program one MAC address. That MAC address overrides the one in EFuse. It becomes the new Wi-Fi MAC, and BT will be that address plus 1. There is no mechanism to program more than one MAC address. If you are going to program MAC addresses, be sure to account for the fact the usage of MAC+1.

    The additional MAC addresses are created by setting the Locally Administered bit on the base MAC, and base MAC+1.

  • Hi Dean, Heikki,

    After discussing with the team, I realized that I have provided incorrect information in my previous post. Apologies for the confusion!

    So there is one MAC address programmed, and two addresses are allocated from it.

    This is correct, each device is allocated two addresses, and one is burned-in.

    In light of the above information  , the burned-in MAC address can serve as the address for your AP and the MAC+1 address can serve as the address for your BLE. From my understanding, this meets your requirements of needing only 2 MAC addresses.

    Please let me know if there are any further questions!

    Best Regards,

    Josh Prushing

  • Hi, 

    Thank you for clarification.

    This meets the requirement. "burned-in MAC address can serve as the address for your AP and the MAC+1 address can serve as the address for your BLE." 

    Now I just need to get valid TOKEN so I can test how abouve can be done with Calibration tool.

    Heikki

  • Documentation state "request TOKEN_ID, consult TI via e2e.ti.com"

    Writing to the OTP bits will require a TOKEN_ID, which will not be mentioned in this document. To request TOKEN_ID, consult TI via e2e.ti.com.

    At moment I do not have direct FAE contanct.

    H

  • Hi Heikki,

    I believe a TI FAE representative has reached out to you, they should be able to provide the Token ID you are looking for.

    Please let me know if you have any other questions!

    Best Regards,

    Josh Prushing