AIROC™ Bluetooth Forum Discussions
Here is link mentioned how to incresee SPP throughout.
Any sample doe of below structure and API wiced_bt_l2cap_register () based on RFCOMM_Serial_Port or RFCOMM_Serial_Port_Multi-Port sample??
I am working with a CYBT-333047-02 device and we are trying to see how we can program the device going through another MCU.
To explain quickly, since we are limited in space on our board, we want to use an MCU as a bridge between our PC and the CYBT. The setup is as follows:
PC <-> FTDI cable <-> some MCU that acts as a bridge <-> CYBT-333047-02
When I use the CYBT-333047-EVAL board connected to my PC through the FTDI cable, I can program the device just fine. But when I connect it through my MCU, it doesn't work.
I am using ModusToolbox to program my device.
Below is the error message that I see:
Programming target device ...
Detecting serial port ...
Found serial port : COM13
Downloading FW ...
Failed to execute DownloadMinidriver command
I used a logic analyzer to see what is going on, and here is what I see (picture is attached):
- Purple and blue are what the FTDI is sending/receiving
- Orange and white are what the CYBT-333047 sees on the other side of the bridge (between MCU and CYBT device)
Here is the sequence of messages that are exchanged:
- PC -> CYBT: 0x01 0x03 0x0C 0x00
- CYBT->PC 0x04 0x0E 0x04 0x01 0x03 0x0c 0x00
- some delay
- PC->CYBT: 0x01 0x4D 0xFC 0x05 0x1C 0xD2 0x00 0x00 0x01
- CYBT->PC 0x04 0x0E 0x05 0x01 0x4D 0xFC 0x00 0x21
What am I missing?
Any help would be appreciated
We know that it is possible to disable sniff mode on CYBT-343026 module with EZserial version 1.2.38-38 by sending this command:
This command seems to disable sniff mode indeed. However the mode 20 is not documented.
We want know if the setting is permanently stored to flash, or do we need to explicitly disable sniff mode every time we power up the module.
我按照‘Running transmitter (Tx) and receiver (Rx) sensitivity tests on CYW920829M2EVK-02’文档的描述操作时，在第三章第五步，执行double-click Reset命令后，文档描述是能收到command complete event。但我实际操作是没有收到这个event。 在设备管理器中查看检测到的端口名称为‘HCI UART’而不是文档描述的‘Kitprog3 USB-UART’,是驱动问题导致的HCI通讯异常么？Show Less
Dear Support Team,
I am currently working on a project that utilizes the CYW20703 chip on a Windows machine. To facilitate development, I have successfully installed the btwusb driver and am able to interact with the device using the cyBluetool.
However, I would like to take a step further and directly access and control the CYW20703 chip using C++. While I have the setup ready and functioning through cyBluetool, I am seeking guidance or an example on how to achieve direct access and control (SCO, ACL channels) through C++ code.
Could you please provide me with an example or any hints on how to interface with the CYW20703 chip programmatically using C++? Any sample code, documentation, or pointers to relevant resources would be immensely helpful.
I am looking forward to your support to enable direct communication with the chip in my development environment.
Thank you for your assistance.
P.S. Apologies if I have chosen the wrong category for this request.
I'm using CYW20819 and ModusToolbox and try to locate a variable at a fixed location in flash.
How can I do that?
I guess I need to define a section in the linker fil, and then use the CY_SECTION command to do that.
But CY_SECTION is not known by the compiler and I'm not sure how to adapt the linker file. I guess, I need to use the xip_section for that?
There is serial flash GD25WD80CEIG on CYW920835M2EVB-01 design.
Is it possible to change serial flash vendor with CYW20835 for CoB design?
Is there other vendor list for in reference design??
Please help to clarify this. Thanks.
Is the CYW89820 module designed to perform HCI_RESET at the stack level when a hardware error occurs? Also, what does Hardware Error code 0 mean? Could you please explain the structure?
#1 Event from HCI. Name: HCI_Hardware_Error (Hex Code: 0x10 Param Len: 1)
#2 Hardware Error Code : 0 (0x00)
#3 HCI CMD SENT  Command to HCI. Name: HCI_Reset (Hex Code: 0x0c03 Param Len: 0)