AIROC™ Bluetooth Forum Discussions
Hi Infineon team,
We are facing some issue when migrating from the development board to integrating the module on to our own platform.
The issues we face are,
1. When in the 'application' mode, the UART interface is communicating at a baud rate of 137.3626 kbps, which is different from the standard baud rate we had found in the evaluation board of 115.2 kbps.
2. We have not gained full understanding of the 'Recover' mode of the Bluetooth module. Would you be elaborate what the 'Recovery' button does and if a connection to MOSI pin is required for our platform?
Kind regards,
Remo
Show Less
While running Hello World example in cyw920829m2evk-02 kit using Eclipse Modus Toolbox IDE the code sucessfully gets programmed but does not work. While analysing noticed that in cycfg_pins.h file, the configuration pins are disabled,tried out other examples similar issue is faced.
Show LessHi Communities,
We are planning to use CYBT-343026-01 for making an application using HFP and AVRCP.
Is it possible to make an application using HFP and AVRCP with CYBT-343026-01?
According to the QDID, I checked the launchstudio as below, but I could not find HFP and AVRCP in the supported layers.
https://launchstudio.bluetooth.com/listingdetails/124893
If CYBT-343026-01 is not appropriate for the application, are there any other suitable devices?
Best Regards,
T. Shibutani / Nexty
Show Less
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 [0] Command to HCI. Name: HCI_Reset (Hex Code: 0x0c03 Param Len: 0)
The project uses 6-10 burners in parallel, to burn at the same time Now found that can not be burned at the same time, only a single burner found that can be burned at the same time burner are 17/18, can not be burned at the same time burner is the beginning of 21
Does this have anything to do with version? Is there a version requirement for parallel use?
If it's a version issue , what was updated at the beginning of 21?
Please help with the answer!
smartconx_target@Q!w2e3r4t5y6u7i8o9p0||/t5/PSoC-Creator-Designer/CY8CKIT-002-%E7%83%A7%E5%BD%95%E5%99%A8%E8%BF%87%E7%A8%8B%E4%B8%AD%E7%9A%84%E4%B8%8D%E8%83%BD%E5%90%8C%E6%97%B6%E7%83%A7%E5%BD%95%E7%9A%84%E9%97%AE%E9%A2%98/td-p/712855
Show LessHi,
The QDID 160340 for CYW20706A2 HOST STACK has expired and new QDID information is required. Can you provide the updated details?
Hi.
I use the CYBT-413061 module (CYW20721B2) on a custom board and try to run the RFCOMM_Serial_Port SPP demo in ModusToolbox 3.2. The code seems to load OK, but when starting the Client Control App and open the serial port, nothing happens - the controls are all greyed out. I then also run BTSpy and connects from a Windows 10 PC as suggested in the instructions - the Client Control App then seems to connect (not greyed out anymore), but nothing happens when pressing any buttons. BTSpy however, seems to display everything, like when hitting a key on Windows/TeraTerm BTSpy, it displays the messages - but nothing shows up on the Client Control App SPP tab or message window.
What could be wrong?
Regards, Roger
Show LessHi~
I recently update MTB 3.2 from 2.4
I added some example for the 343026 BSP
But I cannot find client control application in tools category.
How can I solve the problem?
Many thanks
BRs
Daniel Lim
Show Less
We are using CYW20704UA2KFFB1G BT device on the VIP6102 Android platform (with BCM SoC 7271) . When the BLE devices (example BT remote controller , headphone , mouse ) are in discoverable mode they are not getting added to visible list . We could see the MAC address of the device. we see the error "no link key or ble key found" .
Could you please suggest when we could get such error and if there is any possible way to solve it .
Show Lessgetting error
Break at address "0x50dc3e" with no debug information available, or outside of program code. if i debug using OpenOCD and cable used is kitprog3 (provided with the board).
Info : Listening on port 3333 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
[CYW20820A1.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x61000000 pc: 0x0050dc42 psp: 0x00227670
Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
===== arm v7m registers