I am attempting to set the I2S interface in SLAVE mode for the Call Audio configuration.
So I have one doubt regarding this :
In slave mode do we need to set the WBS and I2SPCM sample rate and clock rate.
If yes then , As the clock will be provided from external source then why we need to set the clock and sample rate?
Thanks for your help
Nitin kumarShow Less
Hi - I am attempting to use the HCI UART method to change the BT device address per the Cypress Developer Community link below, and it appears that we have to add some code to our project in order to enable the HCI interface. Although there are some HCI samples, they seem pretty specific (audio, HID, etc.) and all we need to do is add code that allows us to use the ClientControl.exe Windows app provided by Cypress to update the BT device address. Although the ClientControl app can attach to the HCI COM port, it can't connect to the board so none of the functions in the ClientControl app are enabled.
Thanks for your help,
I am running the client control app on a MAC and the program shuts down every time I start a device discovery. Anyone having the same issue or suggestions on the solution?Show Less
I'm trying to configure one of the ACLK pins to provide a clock to an external device. I've tried adding the following lines but it does not appear to have any affect:
wiced_hal_gpio_configure_pin(WICED_P36, GPIO_OUTPUT_ENABLE, 0);
wiced_hal_aclk_enable(24000000, ACLK0, ACLK_FREQ_24_MHZ);
I could not find anything that explicitly tells the GPIO driver what function I want on the pin, how does it know I want ACLK0 on P36 (rather than P32).
Similar to this question but a different device: CYW20735 ACLK on pin
I have the CYW20719Q40EVB-01 board and am trying to conduct througput tests over BLE and BR/EDR between the board an a Sony Xperia XZ2 Compact (supporting Bluetooth 5). The problems I'm experiencing only regards BLE. When connecting to the device I'm setting the preffered PHY to LE_2M which returns SUCCESS but when I'm sending bigger chunks of data and calculate the throughput, it seems that the PDU-size has not been extended to enable 251 byte payloads. The carachteristics for transmitting data have been setup for 247 bytes.
Is there a way to increase the Link Layer RX/TX payload size in wiced studio?
John BergelinShow Less
I have an application that requires one Bluetooth device to connect to 2 other devices simultaneously.
-- one for remote control data (small packets) connected to another embedded device
-- one inbound audio stream connected to a mobile phone
What development kit would you recommend?
Are there any example projects that fit this requirement?Show Less
wow I'm here again!
Simple code that I've had working on ESP32 & DA14585...
Basically this is the code:
commands_val = 0x11223344;
wiced_bt_gatt_send_notification(conn_id, HANDLE_COMMANDS_VAL, 4, (uint8_t*)commands_val);
This is received incorrectly on my test environment (MacOS). The other platforms - ESP32 and DA14585 respond correctly. A temporary work around is to read the handle again if the value is what is expected, this then reads the correct value 0x11223344.
I am having a problem with my bluetooth module. I am trying to use client control to launch a .hcd file from ram. While I can get it to download, the launch ram command only seems to cause it reboot from whatever is in flash.
I can program the board from wiced studio and have successfully built hello sensor as sell as hal.gpio. For my application I need to boot the firmware from the hci port. I have 2 programs that work so I wanted to test using client control. If I install hal.gpio in wiced studio, and then use client control to upload hello.sensor, it just boots hal.gpio . This is confirmed by monitoring the puart.
Has anyone gotten this module to launch firmware from ram?
I also found another issue too in that if I tried to install hello sensor from wiced studio which works and then try to load hello sensor.hcd to ram using client control, the board ends up corrupted.
How is the hciuart firmware upload doing that?Show Less