BCM4343w modules have the same Bluetooth MAC address

[RoDe_1773541]

I'm using SDK 3.5.2 with two different evaluation modules, one is the Avnet BCM4343w and the other is the Broadcom BCM4343WWCD_1 module and they have the same Bluetooth MAC address, which makes it impossible to operate both at the same time. I tried using the wiced_bt_set_local_bdaddr function, which does change the MAC address but I'm not able to pair with the device after changing the MAC address.  Is there some way to assign a unique mac address?

-Rob

[MichaelF_56]

I think this has come up before: https://community.broadcom.com/message/25344?et=watches.email.thread#25344

vik86​ jaeyoung​ andrew997​ nsankar​

[RoDe_1773541]

I read the thread but it doesn't look like the problem was solved...

-Rob

[MichaelF_56]

Unfortunately, I found out that this is a bug that will be resolved in the next release of the WICED SDK, 3.6.3

This SDK is due to be released shortly.

[Anonymous]

Is this still a problem in WICED SDK 3.7.0?

I used two BCM943341WCD1 has the same problem.

[RoDe_1773541]

It's not fixed.  I downloaded SDK 3.7.0 and ran the ble_hello_sensor app with the default bluetooth mac address and I was able to bond to it without any problems.  Then I changed the mac address using the wiced_bt_set_local_bdaddr() function and when I try and bond to it, the device immediately disconnects.

I'm calling wiced_bt_set_local_bdaddr() in hello_sensor_application_init().  Is that the correct way to change the mac address?

-Rob

[VikramR_26]

Kindly refer here

Changing the Bluetooth MAC Address

aky​

[RoDe_1773541]

I checked the code and I'm setting the mac address the same way and the demo app displays the same behavior.

Steps to reproduce.

1. Compile and program ble_addr_toggle app on BCM94343WWCD1 evaluation platform

2. Connect to HELLO board with default MAC address of 43:43:A1:12:6C:66

3. Bond BLE connection: <- This works

4. Press SW2 to change BLE address to 66:55:44:33:22:11

5. Connect to HELLO board at new BLE address

6. Bond BLE connection: <- This fails.  The device simply drops the connection and starts advertising again

This is the console output. 

Stopping Advertisements

ble_addr_toggle_management_callback: d

ble_addr_toggle_management_callback: a

ble_addr_toggle_management_callback: b

Pairing Complete: 4connection_down  conn_id:2 reason:22

ble_addr_toggle_management_callback: 17

Advertisement State Change: 4

wiced_bt_start_advertisements 0

The board terminates the connection with GATT_CONN_TERMINATE_LOCAL_HOST reason.

-Rob