Use-Case

1. We are using the CYBT-333047 module (CYW20706)
2. We would like to use EZ-Serial with the CySPP communication interface
3. The module should work as Peripheral / Server
4. The module acts as a bidirectional gateway from UART (PUART at the module) and BLE 5
5. The connection must be encrypted. Enycryption in this case means that a communication should only be possible, if the central device has typed in a valid passkey before writing to any characteristic. The passkey should be generated in the peripheral and is shown at the display of our device. So the central device needs physical proximity to the device to establish a communication. Pairing is not required.
6. In my opinion the best example to start is the fixed passkey example.

Documentation issues

Refer to EZ-Serial WICED Firmware Platform User Guide for CYW2070x-based Modules​ (p. 48)

In my opinion, the yellow colored information doesn't fit together. I use the text format, so the formulated text and the text content fit, but the binary content seems to be different?!

Example reproduction

This is my communication protocol.

It seems, that there is missing the ENCryption event. Instead of the ENCryption event, I get a DISconnect event.

I tired this example with the Cypress CySMART App (Android and iOS) serveral times, and I'm sure, that I typed in the passkey correctly.

It would be great if anyone could reproduce this behaviour!

Understanding encryption

What is the API command .CYSPPGP responsible for?

It seems that I just can secure the first characteristic with UUID 65333333-A115-11E2-9E9A-0800200CA101. All other characteristics can be written and read independent of the server_security settings in .CYSPPGP Is that right? In our scenario all characteristics should be secured and not read or writeable until a secured connection is established.

Best Regards!

Hi everyone

Customer wants to confirm below information:

When dropping the power supply (VDDIN) voltage of the BT module,

is it OK to drop the VDDIN power supply immediately without setting a reset?

(* At power-on, after VDDIN stabilizes, wait for + 50ms to release reset.)

Thanks

Yang

We are using CYBT-333047 module with EZ-Serial communication interface.

The gap_query_rssi (/QSS BLE) and the bt_query_rssi (/BTQSS BT-Classic) commands are not working for me.

1. /QSS always returns 0, even if there is an active BLE connection
2. /BTQSS always returns error (E=020D), even if there is an active BT-Classic connection

Please reproduce this issues and let me knwo, if they can be fixed!

Best Reagrds!

Hello Cypress support team.

We would like to establish HSP(AG) on CYBT-333032 if possible.

According to folloing thread, CYW20706 supports HSP(AG) with WICED solution.

https://community.cypress.com/message/186417#186417

Where can we find the HSP(AG) sample codes in WICED Studio 6.4.0?   Notes: Not HFP(AG)

Thanks,

Yoshinori

Hi

I succeed to run HCI standard command, but didn't succeed to see the name or mac address of the chip advertisement.

Also tried to download one of the demo app using the client control to the RAM (don't have flash).

I see the success message but no MAC/name advertisement and UI disabled.

I played with the baud rate also in the code of those demo apps with no change.

Hi,

To use a CYBT-423028-02 module on a custom PCB, what is the best practice to have capabilities for (1) programming the module on board using a standard USB-UART bridge (using a connector) and (2) communications including HCI commends with a host MCU?

I understand that the only way to program the module (with CYW20719) is to use HCI UART interface (explained in KBA223458). The question is: if the HCI UART interface is exclusively used for programming, how the MCU can send HCI commends to CYW20719 after programming the module? Can PUART be used after the programming to send HCI commends in application mode or the HCI UART should be used?

The Introduction of "WICED HCI UART Control Protocol (Doc. No.: 002-16618 Re)" page 9 explains that:

"In the Bluetooth HCI mode, the MCU communicates to the CYW207xx device using the standard Bluetooth HCI protocol. In the Application mode, the MCU uses the WICED HCI protocol defined in this document."

We are just confused how the connections should be designed on the pcb so both normal operation with a host MCU and programming using an external USB-UART bridge (see KBA223458 for example) are possible.

Thanks!

Hi Cypress

Does Cypress have planing for LE audio now? Is it possible for existing modules to support LE Audio in the future?How about the Roadmap schedule? Thank !!

Hi  all:

the pwm calculation: 

   Initial count = 0xFFFF - (Input Clock Freq / PWM Freq out)

   Toggle count = 0xFFFF - ((duty cycle in percentage) * (Input Clock Freq / PWM Freq out) / 100)

   so the PWM  resolution is 1/100, I want to know if I can change the PWM resolution to 1/1000

   Calculation formula:

   Initial count = 0xFFFF - (Input Clock Freq / PWM Freq out)

   Toggle count = 0xFFFF - ((duty cycle in thousandth) * (Input Clock Freq / PWM Freq out) / 1000)

thanks!

mandy

Hello,

I am trying to build a Bluetooth headset with the CYW20706. I am new to PSoCs but I have been able to get the transducer output working via a DAC/AMP combo. However, we have been unable to get the our MEMS microphone to work consistently: https://media.digikey.com/pdf/Data%20Sheets/Knowles%20Acoustics%20PDFs/SPH0645LM4H-B.pdf

I found out that the I2S clock is only ~512kHz whereas the mic requires 1.024 MHz to go into active mode (even though the spec sheet says it runs at 1.5 MHz or 2.4 MHz?) I found out another potential issue is that the CYW20706 only takes 16 bits while the microphone outputs 24 bits, however we should be getting some kind of noise at all times? The microphone does not output anything even when its output pin is not connected to the eval board's I2S input pin. However, sometimes we are able to get audio SOMETIMES by first physically floating the LRC and SEL pins on the mic, which creates some noise, then plugging both into VCC. Occasionally after the noise appears it is able to pick up human audio. We are stumped as to what the issue is as we cannot repeat this phenomenon. We are using HFP. Any guidance would be greatly appreciated.