AIROC™ Bluetooth Forum Discussions
This is an inquiry with Audio_sink in the sample code.
I have "ENABLE_EBUG?=1" as below, but it doesn't recognize ENABLE_DEBUG as 1.
I do a make clean and make ENABLE_DEBUG=1 program. but it has no effect.
How do I get ENABLE_DEBUG to be 1?
I'm try to develope new feature that needs to use multi advertise for different advertising data at each instance.
According to API description, before start multi advertisements, it needs to configure advertise parameters and data.
But after these data are configured and start advertisements, I can't scanned the BLE advertising packet from my device.
The paremeters are using the setting described at function declaration of "wiced_set_multi_advertisement_params"; The advertise data just include complete name.
Is there any configuration that I missed?
I have a custom board with a CYBT-483039-02 module on it. The peripheral UART is connected to my CPU's UART, and the HCI UART is connected to an 8-pin connector on the PCB. Once I have my bluetooth application (BLE-Midi) working:
1. Can the module be programmed in place on the board, or must programming be done prior to soldering it on the PCB?
2. If the latter, how? The programming module CYBT-483039-PROG is available nowhere in the world, apparently.
Our customer has to download Mass F/W download for each chips.
But, they are struggling with download speed consumption.
Their current download method is like as below
1. Using 'cgs.exe' to combilne f/w and own BD Address. and then, make hex file.
2. After that, download firmware with chiploader.
3. Download in same time with CYW20719 as maximum count 15
They have to find a more efficient way.
Please let me know the proper way to solve that issue above.
I'm implementing out of band pairing with the CYBT-413055 as peripheral and an Android smartphone as central. During the out of band pairing procedure the pairing is aborted because of unmatching commitment values. After that I checked how this commitment value is calculated inside the bluetooth specs. The calculation is described as follows:
commitment(key, message) = AES-CMAC(secure_connections_random_value, (public_key_x_of_a || public_key_x_of_a || 0x00)).
So for the key the random value exchanged via the oob interface is used and for the message a concatenation of two times the public key x of the device and 0x00 is used. I calculated the AES-CMAC manually using data generated by the function wiced_bt_smp_create_local_sc_oob_data. With the manual calculation I couldn't reproduce the commitment value. So could it be that the algorithm used inside the function wiced_bt_smp_create_local_sc_oob_data is not the same as described in the bluetooth specs? And how can I solve this issue?Show Less
I want to make an demo board for Audio Speaker with CYW920706.
I want to control volume from Server Side(Peripheral Device CYW920706 Module) with using AVRCP profile.
Is there any application for my design?
Mandatory condition : 1. Volume should be controlled from Server side(CYW920706).
2. Volume control should be controlled from Client Side( ex Mobile Phone).
3. Volume bar sync should be operated normally.
Please suggest it for me.
I've been using a CYBT-353027-02 in ASCII text mode to successfully connect to other Bluetooth classic devices with the version 22.214.171.124 ez-serial firmware version.
Now I'm trying to communicate with a BLE device and not able to fully accomplish this. Using the CYBT-353027-02 I am able to scan and see the remote BLE device, and then I can connect to the remote device. I can discover services and discover characteristics and descriptors in the remote device.
The screen shot below shows various characteristics discovered. When I attempt to read the device model info from GUID 2A24 (using handle 0035 with the gattc_read_handle command /RRH) it doesn't report back the actual model info string. It just reports back the GUID and the value of the R field in the discovery list and 0x02.
All the reads behave like this except for the few descriptors that have descriptive text about a characteristic. The descriptive text actually does come through.
So, working now on trying to get the right combination of SSBP parameters and pairing/bonding procedure.
After I connect, I set the SSBP to use BLE secure, MITM, and bonding, display only, and use passkey, and auto-accept pairing. I'm not sure if this is correct. Ignore the blue text.
I configure my CYBT-353027-02 using the SSBP message, I set a passkey value that the remote device should expect (This is where I'm not sure this is even right), and then I send a /P pair message which triggers the P, CU, ENC, PR, CU event messages to come out. PR result reports 0 which is good. And when I look at the bond table, the 3CA4 node is now in there that I am connected to.
However, when I attempt to read the characteristic again, it still just returns GUID and handle information. Not the expected data.
Also when I connect to 3CA4 node again, the connection message reports B=0 which is NOT bonded.
I believe that I am not getting expected data because the pairing/bonding process must not actually be completing properly???
I am able to connect to the remote BLE device with an Android cell phone and pair/bond, and then read the characteristic and receive the proper text string for the model number. So I know it CAN work, but just not sure what am I doing wrong with my ez-serial protocol commands, etc...
Note: When I use windows to connect to this remote BLE device, windows makes me put in a passkey that was given to me on a piece of paper with the remote device. I am able to finish the pairing process and windows seems to be happy.
I copied the code from the midi_server example over to a new MTW project and I can send Midi notes to iOS apps (Garageband, MidiWrench). However the server does not seem to receive any Midi events from the phone. I added LEGATTDB_CHAR_PROP_WRITE_NO_RESPONSE to the GATT db in the HANDLE_HSENS_SERVICE_CHAR_NOTIFY characteristic entry, and now the iOS apps do see that the device is capable of Input as well as Output.
I expected that when the client sends a Midi note or CC that the callback I registered (midi_server_gatts_callback) would get called but that does not seem to happen. Am I missing some obvious step?
Unfortunately, the MTW documentation is pretty light on tutorials and overviews 😞
Thanks, NormShow Less
STM32H747I-DISCO STMicroelectronics | Mouser
LBEE0ZZ1WE-TEMP Murata Electronics | Mouser
・Wi-Fi/BT module: 1DX M.2 Module
1LV M.2 Module - Embedded Artists
< Project >
・STM32 Connectivity Expansion Pack 1.1.0
I was checking the operation waveform of the example with an oscilloscope.
After sending the HCI_RESET command, RTS does not return from High to Low during the response as shown in the figure below, and the response data is interrupted.Is this normal?
What can I do if this is not normal?
Correspondence with each signal.
A0：TX(OUT) / A1：RX(IN) /
Ch1：BT_REG_ON(OUT) / Ch2：RTS(OUT) / Ch3：CTS(IN)