Studio Bluetooth Forum Discussions

Hello,

I'm trying [3.6.5 Detecting and Processing Written Data from a Remote Client] in the User Guide.

The following settings are made.

[Command]

/CAC,T=00,P=2,L=0012,D=002800B10C2000089A9EE21115A133333365

/CAC,T=00,P=2,L=0015,D=032808180001B10C2000089A9EE21115A133333365

/CAC,T=01,P=8A,L=0001,D=

/CAC,T=00,P=2,L=0012,D=002800B10C2000089A9EE21115A133333365

・T = 00 : Type (0: structure)

・P = 02 : Permission bit (0x02: Readable)

・L = 0012 : Data Length (0x0012: 18Byte)

・D = 002800B10C2000089A9EE21115A133333365 (18Byte)

            - 0028 : Attribute type (0x2800: Primary Service Declaration)

            - 00B10C2000089A9EE21115A133333365 : Service UUID (0x65333333A11511E29E9A0800200CB100)

/CAC,T=00,P=2,L=0015,D=032808180001B10C2000089A9EE21115A133333365

・T = 00 : Type (0: structure)

・P = 02 : Permission bit (0x02: Readable)

・L = 0015 : Data Length (0x0015: 21Byte)

・D = 032808180001B10C2000089A9EE21115A133333365 (21Byte)

            - 0328 : Attribute type (0x2803: Characteristic Declaration)

            - 08 : Characteristic properties bit (0x08: Write)

            - 1800 : Handle of value attribute (0x0018)

            - 01B10C2000089A9EE21115A133333365 : Characteristic UUID (0x65333333A11511E29E9A0800200CB101)

/CAC,T=01,P=8A,L=0001,D=

・T = 01 : Type (1: characteristic value)

・P = 8A : Permission bit (0x02: Readable | 0x08: Write request [acknowledged] | 0x80: UUID is 128 bits??)

・L = 0001 : Data Length (0x0001: 1Byte)

・D =

However, even with this setting, the "W" Event is not issued even if the Write command is issued from the Central App [CySmart etc] after Connection.

[Q1]

What could be the reason why the "W" Event (gatts_data_written ID = 5/2) is not issued?

On the app side, an "Invalid Offset (0x07)" Error will be returned.

Is this a problem?

[Q2]

What is "Invalid Offset (0x07)"?

Is the "/CAC" setting incorrect?

[Q3]

There is no description of "0x80" in the User Guide for the "P" option of "/CAC".

If you check gatts_db_entry_blob (DGATT, ID = 5/4), it says "Bit 7 (0x80) = UUID is 128 bits".

Can I think of "0x80" as a "UUID is 128 bits" permission bit?

Best regards,

Takahashi

Dear Cypress,

We are in the process of Bluetooth certification for a product with CYBT-413034 and got an EOL notice some time ago. We saw that the LE controller QDID expired for the EOL product and we were wondering:

- Are there plans to renew the controller QDID for the CYBT-413034?

- If not, what new QDID can we use for the new drop-in replacement module?

Thank you for your response.

Hello,

In the following Community, it is described in MTU Size of PSoC BLE version.

Re: How to change MTU size for EZ-Serial BLE​

Similarly, what is the MTU Size allowed by the EZ-Serial Firmware of the CYW2070 x-based Module (CYBT-343026)?

Best regards,

Takahashi

Hello

●Does CYBT-343026-01 match with the recognition that software compatible with the WICED HCI control protocol is written at the time of delivery?

●I would like to use it as a standard control protocol, but is it possible to deliver it in a clean state that is not the WICED HCI control protocol?

Best Regards

Hayato

Hello,

I am using WICED Studio 6.2 with CYBT-343026-01 and I am using GPIO06 pin for reading input with pullup as the default state. But When I trying to check the status of GPIO06 it shows 0 continuously. it should be 1 when the button is not pressed. and I am expecting it should be 0 only If the button is pressed. Also, I have checked with GPIO 3 pin and it works perfectly.

Is there any limitation that I cannot use this GPIO6 pin as input?

Thanks and regards,

Neeraj

Hello,

I am using WICED Studio 6.2 with CYBT-343026-01 and currently, I am using deep sleep by using wiced_power_save_start(WICED_WAKE_SOURCE_TIMEOUT,30000); API, and as per documentation after deep sleep on wake it reboots the controller every time. But my problem here is that it gives a spike in current consumption up to 8~9 milliampere on boot. Why so? Also, I have noticed that some GPIO pin goes high for some milliseconds during reboot of the controller. Is this is Cypress's known behavior?

Thanks and regards,

Neeraj

I was wondering if it was possible to remove the reliance of client control for the watch demo (such that it can connect MAC addresses hard coded into the demo). I am struggling to get it to work without opening the COM port using client control.

Is there a setting that disables functionality unless it is connected via Client Control? If so how can i disable it?

Good day!

I am new to Cypress devices but have some experience in BLE design.

I have CYBT-352027-EZ EVAL-01 and I need to use CYBT-353027-02 in my design for standalone operation.

It is good because it has suitable dimensions and good functionality.

I got some questions:

1) Can the module be programmed to work in BLE and Classic Bluetooth network simultaneously?

E.g. be a master to control heartrate in BLE and be a master to work in headset or A2DP Sink profile in Classical Bluetooth. Possible?

2) As far as I understand CYBT-353027-02 has CYW20706 core in it. Right?

3) I have installed WICED-Studio-6.2 and tried hello_sensor demo example (hello_sensor-CYBT_353027_EVAL download UART=COM77). It works fine and could connect to my CYBT-353027-02 and discover it GATT structure from smartphone. But I don't understand how to debug the program in WICED Studio (use breakpoints, go by steps, enter functions and so on).

What is the way to debug program?

Thanks!

Best regards,

Sergey

Hello AnjanaM_61​ and Cypress Team,

I'm using the CYW20706 part. My application requires the use of the SPI_1 bus. This bus uses the same physical pins as the PUART, so I've switched over to using the HCI UART is the debug interface. However, I noticed once I enable the SPI_1 bus, the HCI UART output is corrupted. I came across this earlier post which explains that the SPI_1 bus and HCI UART share a hardware fifo, and hence can't be used at the same time.

CYBT-343026 enabling peripheral SPI kills HCI UART

As I would like to use both the SPI bus and the HCI UART, I would like to disable the SPI bus when it is not needed so I can see debug information. How can the SPI bus be disabled / de-initialized? I initialize the SPI bus with this api call:

wiced_hal_pspi_init(......);

But the API doesn't seem to have a disable / de-initialize function, at least when acting as a SPI master.

As for the HCI UART, it appears I can enable and disable the HCI UART with these API calls:

enable:

wiced_set_debug_uart( WICED_ROUTE_DEBUG_TO_HCI_UART );

and disable:

wiced_set_debug_uart( WICED_ROUTE_DEBUG_NONE);

Please let me know how to disable / de-initialize the SPI bus so that I can use the HCI UART when I'm not using the SPI bus.

Thanks,

Rob

Hi I am trying to automatically pair with a known MAC address bluetooth headphone and establish a A2DP connection with it (without HCI).

I have looked through demo/watch, however I still can't seem to connect to the bluetooth headphones.

I have set the bluetooth device to be connectable, discoverable and pairable and it is able to find the headphones using wiced_bt_start_inquiry( &params, &inquiry_result_cback). Do i use wiced_bt_dev_sec_bond(); to establish a connection to the headphones?

Any help would be greatly appreciated, I have been stuck on this for the whole week.