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.

set unique MAC address to WL1271 WiFi in WinCE

Other Parts Discussed in Thread: WL1271

Hi All,

We are using customized board based on Mistral EVM REV G with TiWi-BLE module under WinCE6.0. The WiFi module can connect to AP and I can browse Internet.

One thing I noticed that the MAC address of WiFi is 08:00:28:32:66:66 which comes from nvs_map.reg. I can also manually  modify MAC address by using WL1271_Manager_App. However it's fine for R&D, not for mass production. I read the document from TI http://processors.wiki.ti.com/index.php/OMAP_Wireless_Connectivity_Station_MAC_Change.

It mentions 3 User space implementations:

User Space Implementation

A new calibrator application generates the .nvs file. To support the application, the following new features are added:

  • The first feature is a simple command to read and print the MAC addresses assigned to the current device.
  • The second feature automatically assigns an address to the .nvs file using one of three methods:
    • Custom: The custom address assignment is the simplest method, in which the tool simply writes the specified address to the .nvs file.
    • Default: The default address assignment directs the tool to determine whether the BD_ADDR is available in the current device. If so, this method writes the blank address (00:00:00:00:00:00) to the .nvs file and the driver retrieves the address from the fuse ROM at runtime. If the address is not available (either because the driver does not support this new feature or the hardware PG version does not contain the address in ROM), the tool returns an error. Nevertheless, the user can force the default address to be used by passing as an argument a custom address set to 00:00:00:00:00:00.
    • from_fuse: Similar to the default address assignment, the from_fuse address assignment checks whether the address is available and fails if not. The difference is that instead of writing the default MAC address to the .nvs file, from_fuse writes the actual MAC address derived from the BD_ADDR from the fuse

    The _fuse implementation is preferred by us. 

  • My question is that if the _fuse way is implemented in WinCE6.0 driver?

Any input is appreciated.

Thanks,

James