- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
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.
Thanks!
Magnus
bt_dualmode_server
================
WICED DCT BT NAME: WICED DUAL MODE
WICED DCT BT DEVICE CLASS : 20 04 1c
00000007 GKI_create_task func=0x801dd91 id=1 name=BTU stack=0x0 stackSize=6144
00000014 GKI_create_task func=0x8024451 id=0 name=HCISU stack=0x0 stackSize=4096
Bluetooth Management Event: 0x15
Bluetooth Management Event: 0x0
Bluetooth enabled (success)
Local Bluetooth Address: [43:34:1B:00:1F:AC]
WICED DCT BT ADDR 0x11:0x22:0x33:0xaa:0xbb:0xcc
Bluetooth Management Event: 0x17
---->>> New ADV state: 3
Waiting for proximity monitor to connect...
Waiting for RFCOMM connection (scn=1)...
Bluetooth Management Event: 0x14
Bluetooth Management Event: 0x14
GATT connection to [00:00:00:00:00:00] established.
Bluetooth Management Event: 0x17
---->>> New ADV state: 0
Local TX power: 4
GATT connection to [00:00:00:00:00:00] released.
Bluetooth Management Event: 0x17
---->>> New ADV state: 3
Waiting for proximity monitor to connect...
Bluetooth Management Event: 0x17
---->>> New ADV state: 4
Bluetooth Management Event: 0x17
---->>> New ADV state: 0
ble_proximity_reporter
=================
Starting WICED v3.5.2
Platform BCM943341WCD1 initialised
Started ThreadX v5.6
Initialising NetX_Duo v5.7_sp2
Creating Packet pools
WWD SDIO interface initialised
WLAN MAC Address : 6C:AD:F8:F0:E9:37
WLAN Firmware : wl0: Nov 25 2015 14:01:39 version 6.49.2 (r602357) FWID 01-1302682f
00000360 GKI_create_task func=0x8022115 id=1 name=BTU stack=0x0 stackSize=6144
00000367 GKI_create_task func=0x80235b5 id=0 name=HCISU stack=0x0 stackSize=4096
Unhandled Bluetooth Management Event: 0x15
Bluetooth enabled (success)
Local Bluetooth Address: [43:34:1B:00:1F:AC]
---->>> New ADV state: 3
Waiting for proximity monitor to connect...
Unhandled Bluetooth Management Event: 0x14
Unhandled Bluetooth Management Event: 0x14
GATT connection to [56:B0:CB:05:B7:27] established.
---->>> New ADV state: 0
Local TX power: 4
---->>> New ADV state: 0
GATT connection to [56:B0:CB:05:B7:27] released.
---->>> New ADV state: 3
Waiting for proximity monitor to connect...
---->>> New ADV state: 4
---->>> New ADV state: 0
Solved! Go to Solution.
- Labels:
-
SDK 3.x
- Tags:
- bluetooth
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Me again. You can probably close this one now. The problem in was that powersave was disabled.
Now I can list the GATT services.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Me again. You can probably close this one now. The problem in was that powersave was disabled.
Now I can list the GATT services.