Studio Bluetooth Forum Discussions
How do I change the SPP transfer rate of CYBT-343026-01 ?
Can I change the transfer rate using the WICED studio ?
And, please let me know the default rate.
Show LessHi! Is it possible to somehow get the audio data from I2S port into the app when CYW20719 streams audio from I2S port to the A2DP BT sink? (20719 is source).
My project should simultaneously stream audio to the headset and the same audio data to the Android device via serial protocol.
Maybe reading an audio buffer, which is used for A2DP codec?
And one more question - is there any documetation to GATT serial protocol (from hci_serial_gatt_service demo app)?
Thank you.
Show LessCan you please tell me if there is a document on which I can parse data from "p_eir_data"?
I tried to find an answer on the forum but could not.
from wiced_bt_dev.h:
/**
* Inquiry result callback.
*
* @param p_inquiry_result : Inquiry result data (NULL if inquiry is complete)
* @param p_eir_data : Extended inquiry response data
*
* @return Nothing
*/
typedef void (wiced_bt_inquiry_result_cback_t) (wiced_bt_dev_inquiry_scan_result_t *p_inquiry_result, uint8_t *p_eir_data); /**< inquiry result callback */
Thanck you!
Show LessI've been developing a BT SPP app on a CYBT-413034 eval module using Wiced Studio 6.2. I have noi problem building, loading and running my code from the Studio IDE.
Now I would like to allow other team members to program their modules with the resulting hex code, using the Wiced Module Programmer tool, rather than the full blown IDE. I connect to the programmer with the same method I connect to Studio, via a USB cable to the PC. I've configured the DUT serial port to be the same as used by Studio, and pointed the firmware file path to the release.hex file generated by Studio.
I then place the module in recovery mode and begin the program process. I've been unable to program the module using this tool, here is the resulting log:
10-06-2020 09:33:43.504: LogManager: Started
10-06-2020 09:33:43.864: COM1: NewSerialPort[3]
10-06-2020 09:33:43.876: COM1: NewSerialPort[4]
10-06-2020 09:33:43.887: COM1: NewSerialPort[5]
10-06-2020 09:33:43.897: COM1: NewSerialPort[6]
10-06-2020 09:33:43.907: COM1: NewSerialPort[7]
10-06-2020 09:33:43.917: COM1: NewSerialPort[8]
10-06-2020 09:33:43.927: COM1: NewSerialPort[9]
10-06-2020 09:33:43.937: COM1: NewSerialPort[10]
10-06-2020 09:33:44.029: COM1: NewSerialPort[11]
10-06-2020 09:33:44.059: WICEDModuleProg: ToggleComponentsByRunningStatus@6 - DutPropChanged - Stopped - False
10-06-2020 09:33:44.061: WICEDModuleProg: #######RefreshGUIByTestItem
10-06-2020 09:33:44.063: WICEDModuleProg: Module Family: CYW20719_SFlash
10-06-2020 09:33:44.084: WICEDModuleProg: ToggleComponentsByRunningStatus@6 - DutPropChanged - Stopped - False
10-06-2020 09:33:44.084: WICEDModuleProg: #######RefreshGUIByTestItem
10-06-2020 09:33:44.084: WICEDModuleProg: Module Family: CYW20719_SFlash
10-06-2020 09:33:44.095: WICEDModuleProg: ToggleComponentsByRunningStatus@7 - ProgBoardChanged - Stopped - False
10-06-2020 09:33:44.095: WICEDModuleProg: #######RefreshGUIByTestItem
10-06-2020 09:33:44.096: WICEDModuleProg: Programming Board: CYBT-413034-02 ProgKit
10-06-2020 09:33:44.096: WICEDModuleProg: Initialization complete
10-06-2020 09:33:44.142: ProgramManager: Loading config file.
10-06-2020 09:33:44.144: ProgramManager: Config file successfully loaded from C:\Users\keith\Documents\WICED-Studio-6.2\20719-B1_Bluetooth\build\zengar-CYBT_413034_EVAL-rom-ram-Wiced-release\ZengarModule.xml
10-06-2020 09:33:44.152: WICEDModuleProg: ToggleComponentsByRunningStatus@0 - TestProgramChanged - Stopped - False
10-06-2020 09:33:44.152: WICEDModuleProg: #######RefreshGUIByTestItem
10-06-2020 09:33:44.178: COM6: OpenSerialPort[0]
10-06-2020 09:33:44.255: PortSetDlg[40]COM6DUT: Connected to "COM6 - USB Serial Port (COM6)" (115200, None)
10-06-2020 09:33:50.133: PortSetDlg[42]COM6DUT: Removing all serial ports.
10-06-2020 09:33:50.136: PortSetDlg[42]COM6DUT: Rediscovering serial ports.
10-06-2020 09:33:50.139: PortSetDlg[42]COM6DUT: 3 serial ports found.
10-06-2020 09:34:46.579: WICEDModuleProg: Running test program.
10-06-2020 09:34:46.581: WICEDModuleProg: ToggleComponentsByRunningStatus@2 - Run - Stopped - False
10-06-2020 09:34:46.698: ProgramManager: Selecting_DUT 1/8
10-06-2020 09:34:46.737: ProgramManager: Running_test_program 1/1
10-06-2020 09:34:46.792: ProgKit423028COM6: ###Enter Pin Mode###
10-06-2020 09:34:46.866: ProgKit423028COM6: Pull Dut#1 CTS_Pin to Low
10-06-2020 09:34:46.868: ProgKit423028COM6: Writting BCMHelper Cmd: C4
10-06-2020 09:34:47.125: ProgKit423028COM6: Exception on Pull Dut#1 CTS_Pin to LowSystem.TimeoutException: The operation has timed out.
at System.IO.Ports.SerialStream.ReadByte(Int32 timeout)
at System.IO.Ports.SerialStream.ReadByte()
at System.IO.Ports.SerialPort.ReadByte()
at CyBLE_MTK_Application.ProgBoard.PullDutPin_SAMI265(Int32 DutNo, DutPinName PinName, PullState PullTo, Int32 WaitTime)
10-06-2020 09:34:47.128: ProgKit423028COM6: Pull Dut#1 XRES_Pin to Low
10-06-2020 09:34:47.129: ProgKit423028COM6: Writting BCMHelper Cmd: C2
10-06-2020 09:34:47.386: ProgKit423028COM6: Exception on Pull Dut#1 XRES_Pin to LowSystem.TimeoutException: The operation has timed out.
at System.IO.Ports.SerialStream.ReadByte(Int32 timeout)
at System.IO.Ports.SerialStream.ReadByte()
at System.IO.Ports.SerialPort.ReadByte()
at CyBLE_MTK_Application.ProgBoard.PullDutPin_SAMI265(Int32 DutNo, DutPinName PinName, PullState PullTo, Int32 WaitTime)
10-06-2020 09:34:47.398: ProgKit423028COM6: Pull Dut#1 XRES_Pin to High
10-06-2020 09:34:47.400: ProgKit423028COM6: Writting BCMHelper Cmd: C3
10-06-2020 09:34:47.655: ProgKit423028COM6: Exception on Pull Dut#1 XRES_Pin to HighSystem.TimeoutException: The operation has timed out.
at System.IO.Ports.SerialStream.ReadByte(Int32 timeout)
at System.IO.Ports.SerialStream.ReadByte()
at System.IO.Ports.SerialPort.ReadByte()
at CyBLE_MTK_Application.ProgBoard.PullDutPin_SAMI265(Int32 DutNo, DutPinName PinName, PullState PullTo, Int32 WaitTime)
10-06-2020 09:34:47.846: ProgKit423028COM6: ###Exit Pin Mode###
10-06-2020 09:34:47.848: ModeSelectBCM20719: Reset DUT#1 to HCI
10-06-2020 09:34:47.851: Prog[0]COM6 : Write HCI Cmd (COM6): 01 03 0C 00
10-06-2020 09:34:49.160: Prog[0]COM6 : No HCI Event in 1000 (1000) ms
10-06-2020 09:34:49.162: Prog[0]COM6 : Reset (COM6) Timeout!
10-06-2020 09:34:49.163: Prog[0]COM6 : Soft-Reset Fail COM6
10-06-2020 09:34:49.165: Prog[0]COM6 : Failed to reset on baudrate = 115200
10-06-2020 09:34:49.167: Prog[0]COM6 : Failed to reset DUT
10-06-2020 09:34:49.179: ProgramManager: ---->SetResult [1,1] = TestFailed
10-06-2020 09:34:49.182: ProgramManager: ---->SetResult [2,1] = ProgrammerNotConfigured
10-06-2020 09:34:49.184: ProgramManager: ---->SetResult [3,1] = ProgrammerNotConfigured
10-06-2020 09:34:49.186: ProgramManager: ---->SetResult [4,1] = ProgrammerNotConfigured
10-06-2020 09:34:49.187: ProgramManager: ---->SetResult [5,1] = ProgrammerNotConfigured
10-06-2020 09:34:49.190: ProgramManager: ---->SetResult [6,1] = ProgrammerNotConfigured
10-06-2020 09:34:49.192: ProgramManager: ---->SetResult [7,1] = ProgrammerNotConfigured
10-06-2020 09:34:49.194: ProgramManager: ---->SetResult [8,1] = ProgrammerNotConfigured
10-06-2020 09:34:49.238: ProgramManager: Selecting_DUT 2/8
10-06-2020 09:34:49.253: ProgramManager: Running_test_program 1/1
Show LessHi,
I'm interested to find out how can CYBT-413034-02 Controller QDID be used together with a Linux Host QDID say BlueZ 5.X to create a complete Bluetooth SIG listing?
Thanks.
Show LessIf you perform BLE connection with a smartphone in the following procedure, pairing with the smartphone will be performed without a passkey.
I think that WICED's BLE library has a specification that devices that store bonding information are paired without a passkey even if there is no bonding information on the smartphone side. The ring will always require a passkey entry, unless both the device and smartphone (Central / Peripheral) have bonding information.
I will attach the source of the device. (BLE_test, TEST_board.zip)
I have a question here.
◆ QA
1. Is there any awareness of this behavior?
2. I want to enter the passkey unless both the device and smartphone (Central / Peripheral) have the bonding information. Is it possible to modify the application? After all, is it necessary to change the Bluetooth library?
3. Do you plan to fix it in future version upgrades?
◆ Procedure
1. Start BLE_test program (no bonding information)
2. Check that there is no "BLE_test" from [Settings]-[Bluetooth] on the smartphone (either iOS or Android is possible).
3. Start the application (use LightBlue, nRFConnect is also possible) from the smartphone, tap "BLE_test1" from "Peripherals", enter the passkey, and perform pairing.
4. Delete "BLE_test" from [Settings]-[Bluetooth] on the smartphone.
5. Launch the smartphone application and tap "BLE_test1" from "Peripherals". You will be connected without inputting the passkey.
6. "BLE_test" exists in [Settings]-[Bluetooth] on the smartphone.
◆ Environment
● Smartphone
・ Device: iPad 4
・ IOS: 7.1 (11D167)
・ APP: LightBlue 2.4.0
● Device
・ App: BLE_test
・ SDK: WICED SDK 6.4.0
<Japanese>
スマートフォンとペアリング(パスキー入力)⇒スマートフォンのボンディング情報削除⇒BLE接続を行うと、パスキーなしで、ペアリングされる
スマートフォンとBLE接続を以下の手順で行うと、スマートフォンとのペアリングで、パスキーなしでペアリングします。
WICEDのBLEライブラリが、ボンディング情報を保存しているデバイスは、スマートフォン側にボンディング情報がなくても、パスキーなしでペアリングしている仕様になっているためと思いますが、他社のBLEのペアリングは、デバイス・スマートフォン(Central/Peripheral)の両方にボンディング情報がある場合以外は、パスキー入力が必ず発生します。
デバイス側のソースを添付いたします。(BLE_test、TEST_board.zip)
ここで、質問があります。
◆QA
1.この動作について、認識はありますか。
2.デバイス・スマートフォン(Central/Peripheral)の両方にボンディング情報がある場合以外は、パスキー入力を行いたいのですが、アプリケーションの修正で可能ですか。やはり、Bluetoothライブラリの変更が必要でしょうか。
3.今後のバージョンアップで、修正する予定はありますか。
◆手順
1.BLE_testプログラムを起動(ボンディング情報なし)
2.スマートフォン(iOS,Androidどちらでも可)の[設定]-[Bluetooth]から、「BLE_test」がないことを確認する。
3.スマートフォンから、アプリ(LightBlueを使用、nRFConnectでも可)を起動して、「Peripherals」から、「BLE_test1」をタップ、パスキー入力、ペアリングを行う。
4.スマートフォンの[設定]-[Bluetooth]から、「BLE_test」を削除する。
5.スマートフォンのアプリを起動して、「Peripherals」から、「BLE_test1」をタップする。パスキー入力がないまま、そのまま接続されてしまう。
6.スマートフォンの[設定]-[Bluetooth]に、「BLE_test」が存在する。
◆環境
●スマートフォン
・デバイス:iPad 4
・iOS:7.1(11D167)
・APP:LightBlue 2.4.0
●デバイス
・アプリ:BLE_test
・SDK:WICED SDK 6.4.0
Show LessHello,
I'm trying to send test commands to CYW920721Q40EVB-01.
My test command - Tx_Test:
0x3f 0x0051 0x00 0x01 0x02 0x03 0x04 0x05 0x01 0x00 0x03 0x01 0x00 0x02 0x00 0x00 0x00 0x00
If i use evaluation board and send this commands using wiced_bt_dev_vendor_specific_command() function embedded in the Bluetooth application - response is correct:
0E 04 01 51 FC 00
Also i have a handset with mounted Bluetooth chip and trying to send the same test command by UART, but i receive wrong responses:
The request breaks in the middle and I immediately begin to receive the wrong response (see request_response attachment):
0x19 0x03 0x00 0x04 0x00 0x00 0x10 0x01 0x00 0x19 0x03 0x00 0x04 0x00 0x01 0x03 0x03 0x00
After 1ms i receive one more response:
0x19 0x03 0x00 0x07 0x00 0x00 0x0e 0x04 0x01 0x03 0x0c 0x00
After 35ms i receive the sequence of responses.
The UART connection is correct, i can upgrade Bluetooth chip using the same enviroment (with HCI command for upgrade).
I'm using Logical analyser connected to the Bluetooth chip to see logs.
Logs are attached as screenshots from Logical analyser.
Could you please explain, why do i receive this incorrect responses? why don't i receive 0E 04 01 51 FC 00 ? !
Show LessHello,
How can I debug CYBT-343026-EVAL with Modus 2.5?
I do not have MiniProg3/4 and JLINK.
Can I debug without the above emulator?
Best Regards,
Takahashi
Show LessgfreenetamAnjanaM_61MichaelF_56DaZh_2976111
i am using CYW920719Q40EVB-01 kit and i'm using WICED studio 6.4.0.61 IDE for software development.
when i try to download a demo project(hello sensor)or snips , it can build successfully but it does not getting download in the board
it says
Detecting device...
+------------------------------------------------------------------------------------------+
| No CYW207x9 device detected.
| 1. Verify the CYW207x9 WICED eval board is connected _AND_ powered
| 2. Verify all switches are set to the default positions
| - see "Connect the WICED Evaluation Board" in the Quick Start Guide or Kit Guide
| for defaults
| 3. Press the reset button on the WICED eval board and retry
|
| See 20719-B1_Bluetooth/README.txt for more info.
| If this problem persists, the board EEPROM may need to be reset to factory defaults.
| Please see Recovery instructions in the Quick Start Guide or Kit Guide.
+------------------------------------------------------------------------------------------+
i have tried the recovery and resetting options in the board but it still does not working. when i check the device manager it shows all the drivers are installed but still not downloading.
please help me to resolve this issue.
thanks and regards
Danny.
Message was edited by: danny baker
Show Lesstest board : CYW989820EVB-01 (CYW89820)
When sending data to the board using hci uart, the board stop if the length is shorter than the header(5byte) or the actual length does not match.
As shown in the capture below, a large amount of unknown data may be transmitted.
The same thing happens when I insert an error handling code under that condition. Is there any way to solve it?
Show Less