Wireless Connectivity Forum Discussions

I've been using a CYBT-353027-02 in ASCII text mode to successfully connect to other Bluetooth classic devices with the version 1.2.29.29 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.

Thanks.

Hi~

One of our customer asked for the Bluetooth module driver for OS(Windows, etc)

If their end-cusotmer want to find a driver, they will provide this for end-customer.

If bt driver is installed automatically, It doesn't matter.

Buit if it doesn't, they have to find a secondary solution manually.

Many Thanks

BRs

Dear Sir,

chip:CYW43455

Module:AW-CM390SM

I find a reference information and try to modify a NVRAM file to fixed the issue.

https://community.infineon.com/t5/AIROC-Wi-Fi-and-Wi-Fi-Bluetooth/Wl-tool-channel-13-not-working/m-p/280617

After adding a command “ccode=0” in the NVRAM, the symptom still appears.

Do you have any suggestions?

BTW, channel information is shown as below.

B.R.

Bill.

Hello,

I'm trying to flash a hex file (from modustoolbox) to a prototype which uses a CYW20721 module (CYBT-423060-02).

For this purpose, I will use a FTDI to program the module using UART.

I saw this article : https://community.infineon.com/t5/Knowledge-Base-Articles/WICED-Module-Programmer-User-Guide-KBA225060/ta-p/253337 that explains how to do this for older modules. Since the article is from 2018, the provided software "WICED Programmer guide" doesn't support CYW20721 based modules.

So, my question is: does someone know where to find an up to date version of this software (or the name of the software that replaced it) ?

Best regards,

Théo

Hello, I need to play short sound on CYW20706 HFP device when I turn on the device. I know that some functionality as voice route is disabled. But each HFP wireless headset has welcome sound. So how can I send short sound via pcm to speaker?

We are attempting to use the bluetooth stack package provided via the connectivity expansion pack.  We have initialized the btstack.  We call the rfcommcreateconnection and receive a handler hardfault.  I have traced this back to a function port_allocate_port.  The system uses the LAIRD_EWB.    

After checking the UART waveform by running the sample "ble_wifi_onbording" that comes with "STM32 Connectivity Expansion Pack 1.1.0", I have a question.

Is it normal for the CTS line to always go low after debug starts?

The CTS line is always low, even if the TX and RX lines are moving.

If this was an anomaly, what do you think caused it?

I checked the waveform between STM32H747 Disco Kit and uRata uSD-M2 Adapter.

<Device>
・STM32H747I-DISCO
　STM32H747I-DISCO STMicroelectronics | Mouser
・LBEE0ZZ1WE-TEMP
　LBEE0ZZ1WE-TEMP Murata Electronics | Mouser
・Wi-Fi/BT module: 1DX M.2 Module
　1LV M.2 Module - Embedded Artists