Smart Bluetooth Forum Discussions
Hi,
Please point me to the file that have pin assignment definitions for J7 - J10 on BCM920737 TAG3 board.
I have searched for these pin assignments and find no glues.
Thanks!
Show LessHi,
like in the hello_client example, i need to scan and advertise at the same time. So i call:
...
blecen_Create();
blecen_Scan(LOW_SCAN);
bleprofile_Discoverable(HIGH_UNDIRECTED_DISCOVERABLE, NULL);
That seems to work, i see the device advertising and scanning. But if i try to modify the advertising data with a call to the bleprofile_GenerateADVData, then something goes broken and the device does not advertise anymore.
Is it possible to change the advertising data while in central role?
Thank you.
Fabrizio
Show LessWhat are the minimum scan interval and window values?
This is a continuation of the thread here: Custom Hardware Stops
Ok, the supplier of my board supplier is mouser (as I order little quantity for prototypes).
I have another issue with PWM, and it's maybe related, I'm using the PMU clock for one the four available.
After 30 sec I have
a blecm event
After this event, my PWM change frequency.
Any clue ?
Here you can find what I can extract from my schmatic. Without too much problem.
You can see that the C8 100nF is on the same side of the board, we have only 1 side where component are sold.
This was taken from all doc we could find, if something is wrong, let me know ...
Show Less
I've seen threads that discuss the interval for advertisements using blecm_startAdv() but there is no mention about how long the device advertises for every interval. Is it just as long as it takes to transmit all the bytes in the adv packet?
By using bleprofile_Discoverable() we can use the builtin state machine and that has a duration setting but how can we set duration when using blecm_startAdv()?
Show LessHello,
we are making a new design with the 737S (system on chip)
as we want the lowest consumption of our circuit, what is recommended for the pins of the gpio that we don't use, leave it floating or put to ground ?
best regards
Show LessHello,
When I want to install BTW pour Window 7, it shows that 'Please plug in or turn on your Bluetooth device'. But I had my BCM92073X development kit connected with PC. How to solve this problem?
Thanks in advance
Show LessHello,
I would like to add an additional Notification in the hello_sensor app. The app already has the following Characteristic Notification defined...
// Handle 0x29: characteristic Hello Notification, handle 0x2a characteristic value | |
// we support both notification and indication. Peer need to allow notifications | |
// or indications by writing in the Characteristic Client Configuration Descriptor | |
// (see handle 2b below). Note that UUID of the vendor specific characteristic is | |
// 16 bytes, unlike standard Bluetooth UUIDs which are 2 bytes. _UUID128 version | |
// of the macro should be used. | |
CHARACTERISTIC_UUID128 (0x0029, HANDLE_HELLO_SENSOR_VALUE_NOTIFY, UUID_HELLO_CHARACTERISTIC_NOTIFY, | |
LEGATTDB_CHAR_PROP_READ | LEGATTDB_CHAR_PROP_NOTIFY | LEGATTDB_CHAR_PROP_INDICATE, | |
LEGATTDB_PERM_READABLE, 7), | |
'H','e','l','l','o',' ','0', |
// Handle 0x2b: Characteristic Client Configuration Descriptor.
// This is standard GATT characteristic descriptor. 2 byte value 0 means that | |
// message to the client is disabled. Peer can write value 1 or 2 to enable | |
// notifications or indications respectively. Not _WRITABLE in the macro. This | |
// means that attribute can be written by the peer. | |
CHAR_DESCRIPTOR_UUID16_WRITABLE (HANDLE_HELLO_SENSOR_CLIENT_CONFIGURATION_DESCRIPTOR, | |
UUID_DESCRIPTOR_CLIENT_CHARACTERISTIC_CONFIGURATION, | |
LEGATTDB_PERM_READABLE | LEGATTDB_PERM_WRITE_REQ, 2), | |
0x00,0x00, |
Now lets say I want to add another Characteristic Notification as such Do I also need to add an additional Characteristic Client Configuration Descriptor for this 2nd Notification/Indication? If so how does the BTLE Stack recognize that the 2nd Client Configuration Descriptor is for the 2nd Characteristic Notification? Is it simply that it follows the Handle ID # in increasing value?
To avoid messing up any of the rest of the handles I would insert this after handle after Handle 0x2D as such
// Handle 0x2E: characteristic Hello Notification, handle 0x2F characteristic value
CHARACTERISTIC_UUID128 (0x002E, HANDLE_COMMAND_ACK_NOTIFY, UUID_HELLO_CHARACTERISTIC_NOTIFY, | |
LEGATTDB_CHAR_PROP_READ | LEGATTDB_CHAR_PROP_NOTIFY | LEGATTDB_CHAR_PROP_INDICATE, | |
LEGATTDB_PERM_READABLE, 2), 0x00, 0x00 |
Now do I need to add another Client Configuration descriptor to Enable the Notifications/Indications?
// Handle 0x30: Characteristic Client Configuration Descriptor.
CHAR_DESCRIPTOR_UUID16_WRITABLE (HANDLE_SENSOR_CLIENT_CONFIGURATION_DESCRIPTOR,
UUID_DESCRIPTOR_CLIENT_CHARACTERISTIC_CONFIGURATION,
LEGATTDB_PERM_READABLE | LEGATTDB_PERM_WRITE_REQ, 2),
0x00,0x00,
Is there anything additional that needs to be done to have this additional notification be usable?
Regards,
Frank
I am trying to get rssi value from wiced sense.
I am using raspberry pi with a ble dongle. I use bluez and gattool to connect and read data from the sense.
I have a python script reading the sensor data. However I would like to get rssi also. I tried to do hcidump, but rssi doesnt show up on the dump I checked the advertisement packet format and it says the flag for rssi is 0xA ( is rssi same as tx power level here? I am not familiar with physical layer terms).
I used gattool to connect to the sense and dumped the raw data. Can you please tell me which packet has data I can get rssi from?
HCI sniffer - Bluetooth packet analyzer ver 5.30
device: hci0 snap_len: 1500 filter: 0xffffffff
< 01 0D 20 19 60 00 30 00 00 00 A2 19 17 6A 73 20 00 28 00 38
00 00 00 2A 00 00 00 00 00
> 04 0F 04 00 01 0D 20
> 04 3E 13 01 00 48 00 00 00 A2 19 17 6A 73 20 38 00 00 00 2A
00 00
> 02 48 20 10 00 0C 00 05 00 12 01 08 00 40 00 60 00 00 00 F4
01
< 02 48 00 0A 00 06 00 05 00 13 01 02 00 00 00
< 01 13 20 0E 48 00 40 00 60 00 00 00 F4 01 00 00 00 00
> 02 48 20 06 00 02 00 06 00 0B 01
< 02 48 00 06 00 02 00 06 00 05 05
> 04 0F 04 00 01 13 20
> 04 13 05 01 48 00 01 00
> 04 13 05 01 48 00 01 00
> 04 3E 0A 03 00 48 00 60 00 00 00 F4 01
Show Less