Smart Bluetooth Forum Discussions
Is there a PCB layout recommendation published in case we use the BCM20737S (SiP) AND INTERNAL ANTENNA?
I just found out that 20737 supports LE audio. Can you please elaborate this ?
Dear,
do you know if wiced smart product (BCM2073xS) are ARIB certify, or plan to be in future?
ARIB certification is an RF certification for Japanese market (www.arib.or.jp/english)
Thanks,
Giordano
Show LessI have a custom board which has HCI_TX, HCI_TX, GND and VDD pins. How do I see the trace output using these pins (I use a FTDI USB to TTL adapter) for debugging? What configuration changes/initializations do I need to do?
Show LessHi.
I am using WICED 1.0 SDK and BLE BCM20732 tag. I am developing an internal demo to verify if this technology, which is new to us, can be used. I read the BLE specifications quickly, and noticed there is SMP module inside, but I wonder how I can implement pin-based pairing using BCM kit.
Is it possible to do it? If so, how?
Show Less===
SDK: 2.2
Tag: 920737.
app: hello-sensor. 920736 tag change to 920737 in IDE.
===
There seem to have some problems when using SDK2.2 on 920737 tag which I never see by using SDK2.1.1 (this one is quite stable
although security is not working)
- By using Wiced IDE, when I modify 20737_EEPROM.btp for DLConfigBD_ADDRBase = "92073710ab01", a
desired MAC or I set BT_DEVICE_ADDRESS=92073710ab01 in build target, after downloading hello-sensor image,
it's very hard for a handset to scan this device and once it's connected with this device, when users try to disconnect
button via BLE APK (free), handset can not re-scan this device again, I need to disable/enable handset bluetooth again
to find it.
- If using OTA download, it seems it's working and handset can find the device.
- After re-downloading the hello-sensor image, i can not plug-in cable to see the trace and need to wait longer not as before.
- using hello-client, i prepare 1 hello-sensor device and 1 hello-client as a master, when this master connect to 2nd handset
, the connection will be drop as Disc reason = 0x8 and please refer to the log. Is any connection problem when using multi-client connection attempt cause this problem seems existed for a long time.
please check log line no 247,
Conn Down handle:41 Slave:1 Disc_Reason: 08
Hi,
i am new with Broadcom, and i have some questions about UART.
How configure UART ( key steps ) to P32,P33 for basic communication ( write something on Tx and catch response Rx pin ). What is best way? I tried sample from docs, but without success.
How to configure UART for using ble_trace ( to read messages from Tx pin )? What are key steps? Is it possible to use both at the sametime?
Show LessCentral and Peripheral
Role Central or Peripheral applies to the BLE connection itself. The device in the central role scans, looking for advertisement, and the device in the peripheral role makes the advertisement.
To understand the distinction, imagine that you have an Android phone and an activity tracker that is a BLE device. The phone supports the central role; the activity tracker supports the peripheral role (to establish a BLE connection you need one of each—two things that only support peripheral couldn't talk to each other, nor could two things that only support central).
Role Master and Slave
After a connection is established, the central device performs as a master and periodically polls the peripheral, which executes in slave role.
Before the Test
The BCM20732 does not support Master/Slave scenario. The BCM20736/BCM20737 will support the Master/Slave environment and is supported in the new SDK 2.x.
Read one of the following sessions to understand what are needed to test BLE. iOS device is used in my test. But Android device and Windows 8 PC can do the job as well.
Simultaneous Master/Slave
Test Configuration
The topology is as follows. EVB1 acts as Slave connected with iPhone. It acts as Master connected to EVB2 at the same time.
[Master:iPhone+LightBlue]
\_____
\
[Slave:BCM920736 EVB1+hello_client:Master]
\_____
\
[Slave:BCM920732/6/7 EVB2+hello_sensor]
Test Procedure
- Plug the EVB1(20736 or 20737, 20736 in this example) into your computer
- Build and download the application hello_client to EVB1 as showed in Figure 1
- Pair EVB1 with a client(iPhone4s or above with LightBlue)
- On iPhone(LightBlue) register for notifications
- Push a button on EVB1 to send notifications to the iPhone(LightBlue) as showed in Figure 2
- Build and download the application hello_sensor to EVB2 as showed in Figure 3. Make sure that your one slave device EVB2 (20732, 20736 or 20737 with hello_sensor) is up and advertising
- Push a button on EVB1 for 6 seconds. That will start connection process with EVB2.
- Push a button on the EVB2 with hello_sensor to deliver notification through hello_client device(EVB1) up to iPhone(LightBlue) as .
Figure 1
Figure 2
Figure 3
Figure 4
Multiple Slaves
Test Configuration
The topology is as follows. EVB1 acts as Slave connected with iPhone. It acts as Master connected to EVBx(x>=2) at the same time.
[Master:iPhone+LightBlue]
\_____
\
[Slave:BCM920736 EVB1+hello_client:Master]
\_____
\
[Slave:BCM920732/6/7 EVB2+hello_sensor]
[Slave:BCM920732/6/7 EVB3+hello_sensor]
[Slave:BCM920732/6/7 EVB4+hello_sensor]
[Slave:BCM920732/6/7 EVB5+hello_sensor]
Test Procedure
Repeat steps from 6 to 8 with another EVBx(x>=2) as showed in Figure 5, you can add more EVB with hello_sensor to the net and report notification.
Show Less
Hardware Requirement
You must have an Android device that support Bluetooth Low Energy(4.0 or above), such as Nexus 5, Nexus 4, Nexus 7, Nexus 10, Samsung Galaxy Series and so on.
Software Requirement
The android device should run version 4.3 and above. Earlier version before Android 4.3 will not work.
Install LEHelloClient apk from attachment. It’s an updated version based on SDK release in <\WICED-Smart-SDK>\Apps\hello_sensor\peerapps\Android\LeHelloClient\bin. Modifications are as follows:
- UI layout changed to accommodate small screen
- Text box moved next to read button
- Fixed bug: can’t display characteristic value when button “Read” is clicked
Build and Download Example Application “LE Hello Client”
Follow instructions in “Session 02_Install Driver, Build and Download Application” to build and download example application “hello sensor” to WICED Smart Tag. Use make target “hello_sensor-BCM92073xTAG_Q32 download”.
Test “Hello Sensor” TAG with LE Hello Client
- Keep EVB BCM92073xTAG_Q32 powered on and application running.
- Turn on Bluetooth on Android device.
- Start the application LE Hello Client on Android device. Click Tap to select a device to select a peripheral.
Figure 1
Figure 2
- If the hello sensor app is working correctly, the LE Hello Client App shows Hello peripheral in a list as shown in Figure 1.The longer the blue bar, the closer the peripheral.
- Click the button Connect to connect your Android device to WICED Smart EVB as illustrated in Figure 2.
- When connection is established, the status connected will be shown below MAC address as illustrated in Figure 3.
- Slide down the screen. You can see service Device Information and service Battery. There are three characteristics in Device Information and one characteristic in Battery as showed in Figure 4. Manufacture Name String is showed as Broadcom. Model Number String is showed as 1234. System ID is showed as 71919F 5F8063b893. We can also get battery level as 0 under service Battery Service.
Figure 3
Figure 4
- Slide up the screen. There are two characteristics, {8AC32D3F-5CB9-4D44-BEC2-EE689169F626} and {1B7E8251-2877-41C3-B46E-CF057C562023}, under service hello service as showed in Figure 5.
- Push the middle (application) button on the EVB (as showed in Figure 10/Figure 11) then click button Read as showed in Figure 6. The Hello X message is updated. Each time the button is pressed, the message number X increments.
- Choose Allow Notifications or Allow Indications from the download list (as showed in Figure 7) to enable notification or indication. Then push the middle (application) button on EVB. The Hello X message is updated automatically. Each time the button is pressed, the message number X increments, as is shown in figure 8.
Figure 5
Figure 6
Figure 7
Figure 8
- Change the value for the characteristic {5E9BF2A8-F93F-4481-A67E-3B2F4A07891A} to 0x03 and then click button Write(as showed in Figure 9) . The EVB emits an audible beep, and the LED flashes three times to acknowledge the write.
- Push the Application button (Figure 10/Figure 11) on the WICED Smart EVB. The LED on the EVB blinks three times.
Figure 9
Figure 10
Figure 11
Show Less