Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
I tried starting the bt_dualmode_server from WICED SDK 3.5.2 on a BCM943341WCD1 eval board. Then I tried connecting to it using the "Wiced SMART Find Me" app from Google Play. I can discover the "WICED DUAL MODE" device but it doesn't connect correctly. The GATT connection reports my phone having bd_addr 00:00:00:00:00:00. Also, the bd_addr shown in the app is different every time I restart the board and is not at all similar to the address reported by the log. The log is below.
Then I tried the ble_proximity_reporter example and that is working better, but the address of my phone reported by the GATT connction is also different every time. And if I connect and set the app to alarm when I lose connection, it simply doesn't. This log is also below.
I guess there could be more problems lurking here, the one I'm most interested in is to get BLE working in dualmode and to see the correct bd_addr reported.
I've had some progress with this one on my own. The dualmode server works better if I add a wiced_init() line in the beginning of application_start().
I also realized the random BD addresses is a BLE feature, so no worries there.
I'm still having problems getting BLE to work in a non-WICED controlled environment though. I'm still running RTOS and still calling wiced_init, but it doesn't send me the list of services when I ask for it.