Studio Bluetooth

Hello! I'm using the CYBT-343026-01 module and I've been having problems with the  packetization modes of CYSPP. (I'm sending messages via BT and recieving it on PUART) 

I was using the deafult anticipated mode but It was sending corrupted messages with a baud rate of 9600. So i decided to change to Immediate mode and it worked perfectly. My problem is that sometimes the module doesn't "remember" it's in immediate mode and works in anticipated mode aparently (It's sending corrupted messages). 

When this happens I send a  .CYSPPGK command to get the packetization mode, and it indicates its on immediate mode despite it's not working that way. 

UART Commands:

 13:48:55.836 -> .CYSPPGK
13:48:55.836 -> @R,0022,.CYSPPGK,0000,M=00,W=0A,L=14,E=0D 

How can I  make the module to always work correctly? Is there some parameter I'm missing to configure?

Hi,

I have a question about "user_data" parameter in interrupt handler.
In the prototype of wiced_hal_gpio_register_pin_for_interrupt() API, 3'rd param(void *userdata) is "Will be passed back to userfn as-is". However, when I test it with following test code, it looks not working. I guessed "udata" must be printed out "123" but printed out "168". I am not sure if my test code is incorrect or it's SDK bug.

Q) May I ask what's wrong with following test code?

H/W : CYW920706WCDEVAL

S/W : WICED SDK 6.4.0 

void headset_set_input_interrupt(void)
{
          uint8_t my_data = 123;

          wiced_hal_gpio_register_pin_for_interrupt( WICED_GPIO_BUTTON, headset_interrupt_handler, (void *)&my_data );
          wiced_hal_gpio_configure_pin( WICED_GPIO_BUTTON, WICED_GPIO_BUTTON_SETTINGS( GPIO_EN_INT_BOTH_EDGE ), WICED_GPIO_BUTTON_DEFAULT_STATE );
}

void headset_interrupt_handler( void *user_data, uint8_t value )
{
        WICED_BT_TRACE("[%s] enter...\n", __FUNCTION__);

        if ( wiced_hal_gpio_get_pin_input_status(WICED_GPIO_BUTTON) == BUTTON_PRESSED )
        {
                 WICED_BT_TRACE( "Button pressed\n");
         }
        else
        {
                uint8_t udata = (uint8_t *)user_data;

                WICED_BT_TRACE( "Button released\n" );
                WICED_BT_TRACE( "udata = %d\n", udata);
      }
}

Thanks,

Liam

Hi,

I am running the A2DP sink example on CYBT-343026-EVAL board. I play a 48kHz (sample rate) test audio file from a Pixel 4A android device.

The oscilloscope show the I2S word select signal to always be at 44.1kHz. I enabled android developer options, and sure enough this is the only sample rate that is selectable (i.e. not grayed out).

It seems that the 48kHz cannot be negotiated.

Any suggestion on how to make the 48kHz available? I would expect this to work after reading KBA228409 and this page https://community.cypress.com/t5/Resource-Library/A2DP-Sink-Example-on-CYW20706/ta-p/246388.

Thanks, Davide

Hello All,

     I was trying to implement a new use case in which audio data has to be processed by codec DSP. so with SPI  I am trying to read audio data from codec memory region. But here I am facing one issue that is I am unable to find API's to give audio data packets. I am using latest-v3.x wiced_btsdk. In available sdk I2S is configured to route audio data but how audio data is handling in I2S interrupt handler and transferring to BT controller code is hidden it seems. so can anyone help me How Audio data is routing to BT stack. Even in playback case also I am unable to understand How Audio data is SBC (or) any codec  standard decoded and sent to codec.

Thanks in Advance.

Nagarjuna

i used the API of "wiced_hal_write_nvram" for write to nvram about 132byte.

but, sometimes it is fail with 0x004 error code.

my code is as below.

bytes_written = wiced_hal_write_nvram( 0x01, sizeof(setting_t), setting, &result);

and if i use the API "wiced_hal_write_nvram" for write to nvram, result is repeat as below.

save_setting(result: 4, written: 0)

save_setting(result: 0, written: 132)

where is the result of API of "wiced_hal_write_nvram"?

i want to know what is mean the result is 4. could you help me?

Hello!
I'm new to bT domain and I'm based in France & would like some assistance to choose the perfect Cypress module for my application.

My use case: BT Audio Earphones (HFP, A2DP, AVRCP & SPP together) , HFP slave initiating BT- reconnection incase of disconnection + Custom data commands 1) under HFP 2) under RFCOMM 
My custom commands are to interface with another Encrypted BT HFP AG device as Walkie - Talkie. 

My previous setup: WT32-IA under IWARP I'm able to achieve these above functions using the "ECHO" Command on IWARP API. now I'm planning to upgrade it to BT 5.0 specs & I'm looking to change to cypress. 

Please suggest which product is best for my purpose & especially can I achieve the Custom data command + HFP reconnection? Also suggest me which cypress chip should I go for ? 

Thanks for your input 

Hi,

I'm using the CYBT 423028-02 on your evaluation board with EZSerial 1.0.4.21 installed.

When I try to connect to a device that prefers 2M Physical Layer I will be disconnected after a short while and I'm also unable to discover any services until the disconnect.

When I force the client to use 1M Phy instead everything works stable....

So I'm wondering if EZSerial does support 2M Phy?

Best regards

Alex

Hi ALL: 

I'm trying to compiling the '20706-A2_Bluetooth' exampel project for CYBT-343026-EVAL following the guide document（AN223400）using with WICED-Studio-6.2. 

But there occurs some errors: 

Symbol 'errno' could not be resolved;

Symbol 'optarg' could not be resolved;

Symbol 'optind'could not be resolved;

How to resolve them? 

I'm appreciate if someone can help me figure out these. Tks！