Studio Bluetooth Forum Discussions

Hello,

i am using 4 GPIO pins. Two are INPUT Configure as button input.

wiced_hal_gpio_configure_pin(WICED_P32,GPIO_INPUT_ENABLE|GPIO_PULL_UP|GPIO_EN_INT_RISING_EDGE,GPIO_PIN_OUTPUT_LOW);

wiced_hal_gpio_configure_pin(WICED_P31,GPIO_INPUT_ENABLE|GPIO_EN_INT_FALLING_EDGE,GPIO_PIN_OUTPUT_HIGH);

wiced_hal_gpio_register_pin_for_interrupt( WICED_P32, hello_sensor_interrupt_handler, NULL );

wiced_hal_gpio_register_pin_for_interrupt( WICED_P31, hello_sensor_interrupt_handler, NULL );

AND i am using the smae interrupt handler for both the buttons? is this okay?

Two as Output pin Configure as LED output

wiced_hal_gpio_configure_pin(WICED_P28,GPIO_OUTPUT_ENABLE,GPIO_PIN_OUTPUT_HIGH);

wiced_hal_gpio_configure_pin(WICED_P30,GPIO_OUTPUT_ENABLE,GPIO_PIN_OUTPUT_LOW);

1. As i press button, i get output as my LED glows, but when i switch off the module, that time the output led glows? Does it mean Interrupt is detected? Any debouncing logic?

2. Sometimes my CYBT-343026-01 gets hang i think becuase it doesn't perform the function, so i restart it by switching on and off power?

Hello,

My application is based on the CYW920719Q40EVB-01 Evaluation Board. First, I need to define a GPIO pin, then divide the 24MHz clock into 32kHz, and finally output the 32kHz clock through the defined GPIO pin to external use. The problem is that how to use WICED-Studio-IDE to implement this function? Please provide some references and operation steps.

Thank you very much!

Hi everyone,

[CYW20819] Revised data sheet for Tx Power description

A miss was found in your data sheet regarding the Tx Power description.

https://community.cypress.com/thread/55948?q=[CYW20819]%20About%20Tx%20Power

The customer wants to know when the revision can be done.

Thanks,

Yang

Hello,  AnjanaM_61​

I am using Hello sensor code. I am using an inextra output pin to drive an led(active low).  In hello_sensor_application_init() funct. After platform led() I have written.

Wiced_hal_gpio_configure_pin(wiced_p26, GPIO_OUTPUT_ENABLE | GPIO_PULL_UP, GPIO_PIN_OUTPUT_HIGH);

Wiced_hal_gpii_set_pin_output(wiced_P26,1);

The problem is on power up. The Led turn on for few milliseconds and then turn off?  (After I reached to the initialisation). But I don't want the Led to be Turn On on power up?

Thank you.

We are using the CYW 20706 as the target device for connecting to a BT audio source (using the 'Headset' demo from wiced studio). A mobile phone (android) can conenct correctly and send audio data (verified via I2S output). but our target communication device (security transceiver) can pair but not connect to the device.

When the connection is attempted the CYW 20706 sends the connection status event data (with correct connection status data) but immediatly sends a secondary Connection status event with Connection broken data and Error code 0X13.

The datasheet and 'WICED-HCI-Control-Protocol.pdf' don't refer to the Connection status event so i can't figure out what the problem is.

Can anybody explain what this errorcode measn and how i can fix it?

Hi,

"CYW20719 datasheet" says there is a 448KB-RAM in the chip.

I used a large array:

...

static uint8_t data[640*480];

...

The program was built and downloaded into CYW20719 normally (WICED-Studio-6.4).

But CYW920719Q40EVB-01 didn't run.

WICED-Studio-6.4 outputs:

--------------------------------------------------------------------------------

Patch code starts at              0x00270400 (RAM address)

Patch code ends at                0x0027A518 (RAM address)

Patch RW/ZI size                  2572 bytes

Application starts at             0x002155FC (RAM address)

Application ends at               0x00261414 (RAM address)

Patch code size                        41240 bytes

Application RAM footprint             310808 bytes

                                      ------

Total RAM footprint                   313380 bytes (306.0kiB)

--------------------------------------------------------------------------------

If I canceled “static uint8_t data[640*480]”, CYW920719Q40EVB-01 started correctlly.

WICED-Studio-6.4 outputs:

--------------------------------------------------------------------------------

Patch code starts at              0x00270400 (RAM address)

Patch code ends at                0x0027A518 (RAM address)

Patch RW/ZI size                  2572 bytes

Application starts at             0x002155FC (RAM address)

Application ends at               0x0021639C (RAM address)

Patch code size                        41240 bytes

Application RAM footprint               3488 bytes

                                      ------

Total RAM footprint                     6060 bytes (5.9kiB)

--------------------------------------------------------------------------------

Best regards.

Can i get debug configuration for CYBT-343026

1) debug configuration in wiced studio.

2) debug pin configuration in cyw920706 board.

3) debug connecting process

here i am having some doubts on cybt-343026 module.

1) this modules are comes with same mac id?if yes then how can i change mac id?

2)how can i change device name and how can i store name in flash?

3)actually i try to change device name it changed but after switch off and on again device name not changed.

regarding this problem can i get solution.

Hi

I send HCI commands to CYBT-423028-EVAL with CyBluetool.

However, I can't use these HCI commands to setup connection with my phone BT.

How to do the throughput test and sco throughput test by CyBluetool??

These HCI commands/event are:

HCI RESET

Write_Scan_Enable

      Then， phone send the connection req

HCI Event:

Connection Request

HCI Command:

Accept_Connection_Request

HCI Event:

Command Status

HCI Event

PIN Code Request

HCI Command

PIN_Code_Request_Reply

HCI Command Complete Event

PIN_Code_Request_Reply

HCI Event

Link Key Notification

Connection Complete

HCI Event

com3@115200

[03 0B ]: 00 0B 00 D6 0C D1 E0 87 94 01 00

event = 0x03 (3,"Connection Complete")

Status = 0x0 (0, "Success", "Success")

Connection_Handle = 0x0B (11)

BD_ADDR = "9487E0D10CD6"

Link_Type = 0x1 (1, "ACL connection")

Encryption_Status = 0x0 (0, "Link level encryption disabled")

Max Slots Change

HCI Event

com3@115200

[1B 03 ]: 0B 00 05

event = 0x1B (27,"Max Slots Change")

Connection_Handle = 0x0B (11)

LMP_Max_Slots = 0x5 (5)

ACL Data (rx)

com3@115200

[0B 20 0A 00 ]: 06 00 01 00 0A 02 02 00 02 00

Broadcast_Flag = 0x00 (0, "Point-to-point")

Packet_Boundary_Flag = 0x02 (2, "First automatically flushable packet")

Connection_Handle = 0x0B (11)

Data_Total_Length = 0x0A (10)

data = "06 00 01 00 0A 02 02 00 02 00"

ACL Data (rx)

com3@115200

[0B 20 0C 00 ]: 08 00 01 00 02 03 04 00 01 00 44 00

Broadcast_Flag = 0x00 (0, "Point-to-point")

Packet_Boundary_Flag = 0x02 (2, "First automatically flushable packet")

Connection_Handle = 0x0B (11)

Data_Total_Length = 0x0C (12)

data = "08 00 01 00 02 03 04 00 01 00 44 00"

ACL Data (rx)

com3@115200

[0B 20 0C 00 ]: 08 00 01 00 02 04 04 00 01 00 45 00

Broadcast_Flag = 0x00 (0, "Point-to-point")

Packet_Boundary_Flag = 0x02 (2, "First automatically flushable packet")

Connection_Handle = 0x0B (11)

Data_Total_Length = 0x0C (12)

data = "08 00 01 00 02 04 04 00 01 00 45 00"

Disconnection Complete

HCI Event

com3@115200

[05 04 ]: 00 0B 00 13

event = 0x05 (5,"Disconnection Complete")

Status = 0x0 (0, "Success", "Success")

Connection_Handle = 0x0B (11)

Reason = 0x13 (19, "Remote User Terminated Connection")

why happens disconnection complete in the last step??