Smart Bluetooth Forum Discussions
In the document "BCM2073X Product Portfolio", it says that BCM20737 chip has NFC paring. Is there any documentation on this? Does that mean BCM20737 has both BLE and NFC capability?
I can't find any info on the BCM20737 chip.
-Mehrdad
Show LessHi,
I've looked through the SDK (v1.1.0) a bit and done some file searches but I can't find how to set the OOB data. I'm trying to have the Broadcom module be used in peripheral mode, and only allow OOB pairing.
I've seen the OOB flag in the LESMP_PAIRING_REQ_CMD structure, so I would assume that if that flag is set (by both devices), then the OOB pairing method will be used. But it requires the OOB data to also be set and I haven't been able to find that yet.
Along with this, I'd like to then use OOB only and disallow the other pairing methods. I believe this can be done when a pairing request comes in by checking the OOB flag and if it is false, sending back an error response. I was able to test this in another BLE stack. I wanted to know if I do get a callback when there is a pairing request and what it is called.
Thanks,
Mike
Show LessI have about 500 byte that is sent through UART and currently I am only gettin about 14 bytes through the BLE which is received by the iPhone. I understand the buffer size for UART is only 14 bytes and I tried buffering it but still no avail is there any other methods or functions that can be used to get all the bytes?
Show LessI install wiced android app in my smartphone, my android is 4.3 JWR66V.
I can use this app to connect with 20732 tag and get the exposed service from hello_sensor.
bletrace like this:
hello_sensor_timeout:140
bleprofile_connUp()
BLE_no_adv
BLE_idleconn:timer(3)
hello_sensor_connection_up: 98d6f7b62c9e 64
BLE_no_adv
profile:idletimer stopped
hello_sensor_timeout:141
But sometimes, my app can't get exposed service because these information appear in bletrace:
hello_sensor_timeout:115
bleprofile_connUp()
BLE_no_adv
BLE_idleconn:timer(3)
hello_sensor_connection_up: 98d6f7b62c9e 64
BLE_no_adv
profile:idletimer stopped
smp conn down
bleprofile_connDown()
bleprofile_connDown stop Idle Timer
hello_sensor_connection_down:98d6f7b62c9e handle:64
BLE_low_un_adv:timer(1)
ADV start: 000000000000
hello_sensor_timeout:116
what does cause the connection fragmentized? why connection was broken immediately after connection just established?
For our application we want to be able to download a larger amount of data from the tag upon request (>>22 bytes).
Is there a suggested best approach to doing this?
We're looking at designing the protocol based on the tag sending 4 notifications per connection event, with acks returned in a writable characteristic.
For this purpose it would be great to be gain more insight on how notifications work within the stack.
How large is the queue of unsent notifications in the stack? Is there any way to find out how many unsent notifications are currently pending? What happens if there is no room in the queue?
Is there any way to receive a callback to trigger after a notify is sent?
Is there any way to receive a callback when a connection event is over?
For our manufacturing process we will need to configure our device with a MAC address. I was thinking to do this by communicating via the peripheral UART during a manufacturing test process. If my software knows the MAC address to use, how can I install it in the device?
Also, what are the guidelines on selecting MAC addresses? Is there a certain range we should use or do we need to acquire a range from an authority?
Show LessBeen struggling with this one a few days...
Central attempts connection (connUP) with peripheral.
Central gets connUP callback.
Sometimes, instead of bond, central gets connDOWN callback.
Central attempts again but gets connDOWN again, a few more times.
Central finally gets bond, and sends write-request,
but does not receive expected notification from peripheral.
Central turns on scan.
But gets no ad receive callback.
Can't do anything to restore scan.
Must reset to get it working again.
Show LessHow can ulp_rand() be seeded after boot, to change its first returned number?
I want to randomly generate a unique ID for each of our peripheral, when peripheral boots.
Show Less