Studio Bluetooth Forum Discussions
Hello,
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?
Best regards
John Bergelin
Show LessI 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
and
-- 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 LessHi,
wow I'm here again!
Simple code that I've had working on ESP32 & DA14585...
Basically this is the code:
uint32_t commands_val;
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.
Any suggestions?
Thanks.
Show LessI 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 LessHi
Could you tell me the QDID of the below profile?
---------------------------------------------
1. Interoperability Profile(IOPT)
2. Object Push Profile(OPP)
3. Phone Book Access Profile(PBAP)
4. Video Distribution Profile (VDP)
---------------------------------------------
Thanks
Yang
Show LessHi forum,
I'm trying to upgrade to WICED 6.2.1.2 from 6.0. The WICED_BT_SCO_OVER_APP_CB option is missing from wiced_bt_sco.h for 20706. Is it not supported anymore?
Thanks,
LJ
Show LessI'm developing an application using the 20719 silicon, namely the CYBT-423028-02 module. The application is designed to collect data from a sensor over a hardware serial bus, and forward it over the Bluetooth connection using the serial port profile.
The basic application is working in that it catches the sensor pin interrupt and does the appropriate transaction to collect the data which is then forwarded over Bluetooth. The issue I'm having is that if I start pushing the data rate towards what I require for the application (250 samples per second), the module will crash. From experimentation, I've found that the module will crash even if I do not initialize the Bluetooth stack at all (commenting out wiced_bt_stack_init call) and only have the application reading data from the sensor. But it won't crash if I remove the call to actually read the sensor, which is an approximate 300us SPI transaction. If I just toggle a pin state and return, the module will continue running normally.
So from this information, I'm guessing that if you get a callback generated by a pin interrupt which was registered with wiced_platform_register_button_callback, you must return within a set time period. What is this time period exactly, and where is it documented? Further, does this callback execute from interrupt context and is holding off other critical system interrupts, which is why the chip is crashing? If that's the case, is there a way for me to tell the module that I need to execute something from the main context instead so that I don't hold off the module's critical functions? Normally I would use a worker thread, but WICED Studio does not implement the RTOS for this module as far as I am aware (it has the header file, but is missing the (SDK directory)/WICED/RTOS folder which defines the RTOS).
Thanks for any help in advance, let me know if you need more information to answer my questions in paragraph 3.
Show LessOur product use CYW20704UA2 for BT4.2 HOST application.
But refer Qualification and Certification – KBA222020 CYW20732/20736/20737/20706/20707 Qualification and Certification – KBA222020 & find at Launch Studio - Listing Search
When we provide QDID#104467 for certification, LAB mention this QDID is BT5.0 not BT4.2.
Then we provide another QDID#72771 ,LAB also mention this expired over 3 years.
Have any wrong for the communication?
Now I can't find suitable QDID for certification.
Show LessHi.
The header file WICED-Studio-6.2\20706-A2_Bluetooth\include/wiced_bt_dev.h contains a prototype for a function called wiced_bt_dev_read_tx_power(). But if I call that function the link fails saying there is an 'undefined reference to `wiced_bt_dev_read_tx_power''. Is there an extra library that needs to be linked in? If so which one?
Thanks
Nigel
Show Less