AIROC™ Bluetooth Forum Discussions
- I noticed that the only "supervision timeout" parameter in the bt configuration struct (wiced_bt_cfg_settings_t) is the conn_supervision_timeout under ble_scan_cfg which is obviously for BLE, not BR/EDR. Is this the value changed when calling wiced_bt_dev_set_link_supervision_timeout()? does wiced_bt_dev_set_link_supervision_timeout() even makes sense for BR/EDR?
- What is the unit of the timeout argument to wiced_bt_dev_set_link_supervision_timeout()? Acording to some forum posts it is "multiple of 10ms" aka 500 = 5000ms. However, acording to the Bluetooth Core Spec it is "Time = N * 0.625 ms"
Initially, I implemented the factory reset and reboot commands on my module (cybt-343026-01 firmware ver 1.2.29) using the following:
/RFAC
/RBT
Following that, I attempted to establish pwm0 modulation with these commands:
SPWM,N=0,E=1,D=01,S=00,P=0400,C=0100
@R,000A,SPWM,020C
GPWM,N=0
@R,0027,GPWM,0000,E=00,D=00,S=00,P=0000,C=0000
See attached screenshot:
I did get the E=1; if I only sent "SPWM,N=0000,E=1"
However, it seems that I'm unsuccessful in configuring the pwm0 registers. Additionally, the scope probe connected to the pin doesn't indicate any clock activity. Could you clarify if I'm missing any critical commands in this process?
thanks,
Show LessRightnow I'm using CYBT-213043-MESH for my experiment. My problem is there is not much information for CYBT-213043-MESH.Especially the Block diagram or schematic diagram of CYBT-213043-MESH. I wonder if anyone has the information about Block diagram or schematic diagram of CYBT-213043-MESH?
Thank you!!
Show LessI am using CYW20706 and MTB(Modus Tool Box) SDK.
We are using "wiced_bt_iap2_get_auth_chip_info" located in iap2_main.c for MFI chip verification in the production process.
In the absence of the MFI chip, "bsc_OpExtended" did not return and not only failed to process the error, but also found that the watchdog was jammed and reset.
We don't have much time. Please check as soon as possible.
Show LessHi,
We are experiencing unexpected reboot of a CYBT-483056-02 module used on a CYBT-403056-EVAL board under some circumstance (two connection created). We have no clue of what is happening, and during the research for debugging options, I came accross this topic (https://community.infineon.com/t5/Resource-Library/CYW20719-and-CYW20735-Clocks-RTC-WatchDog-Timer-Application-Timer-and-PWM/ta-p/246352) where it's stated that when the device crash, there's a core dump output on the HCI Uart.
Indeed, looking at the data output on HCI Uart, I can see strings that belong to the firmware (version string and also some libraries strings). The HCI format seems to start with a pattern (0x04 0xFF 0xF4 0x1B 0x03), followed by what seems to be a memory address. Unfortunately I couldn't find any document that describe the HCI vendor command for this, and BT-Spy do not seem to identify that this is a core dump (simply print some weird chars).
Can you please help me converting the core-dump to an file that I can examine with GDB ? We already played with many parameters to find the issue.
Also, I found out that using the wiced_bt_printf API will corrupt the traces send on HCI-uart for debug (I used this API to format some strings that we use for our software usage, and found that this was generating some partial repetitions on the traces send to wiced_bt_trace). I've used a custom printf/snprintf implementation and the problem is solved.
Regards, Jerome
Show LessHi, I'm confused regarding what BT version (4.x or 5.x) that is supported by the Sterling LWB5 radio module.
I'm using a Variscite SoM (System on Module) DART-MX8M-MINI which uses the LWB5 module. In the datasheet of this SoM it is says the LWB5 supports BT 5.2 (see screenshot from datasheet below)
(link to pdf: https://www.variscite.com/wp-content/uploads/2019/02/DART-MX8M-MINI-Datasheet.pdf)
If I look into the Lairds datasheet for Sterling LWB5 it also claims support for BT 5.2, see screenshot below:
(link to pdf: https://www.lairdconnect.com/documentation/datasheet-sterling-lwb5)
However, when looking into the datasheets of the CYW43353 (the chip used on the Sterling LWB5) it only says support for BT 4.1 (see screenshot below):
(link to pdf: https://www.infineon.com/dgdl/Infineon-CYW43353_Single-Chip_5G_MAC_Baseband_Radio_with_Integrated_Bluetooth_4.1_for_Automotive_and_Industrial_Applications-DataSheet-v09_00-EN.pdf?fileId=8ac78c8c7d0d8da4017d0ee21d2b6876)
What is the truth here? What BT version does CYW43353 actually supports?
Hello,
With reference to the community ticket,
there is a restriction of 23(3 bytes opcode and attribute) bytes MTU across the BLE Server and BLE Client.
How to extend this value.
Regards
Show Less
Dear members,
i try to implement the UART_to_BLE_central workspace from the mentioned project in Android. Unfortunately Android is not able to finalize a service discovery with the defined Server_UART (0003CDD0-0000-1000-8000-00805f9b0131). I tested with AIROC™ , bluetoothctl and with nRF Toolbox but they all fail.
Compared also the BLE component configuration to other projects where the discovery works but i can not see any settings there which can lead to this behavior.
I am thankful for all hints and ideas how to solve that issue.
Kind regards
Daniel
I am useing the PIC18 as host and CYBLE-013025-00 as BLE slave.
I found the "EZ-Serial_Host_API_Protocol_Library" drivers to integrate Host MCU with CYBLE-013025-00.
But the problem is "EZ-Serial_Host_API_Protocol_Library" is written in C language and our product code is written in Assembly language.
please provide the Assembly language for "Serial_Host_API_Protocol_Library" or suggest any way to convert this "Serial_Host_API_Protocol_Library" into Assembly language.
all suggestions are welcome
Show Less
hi,
Could you please help us check the I2S master mode maximum audio sample rate is 16KHz ?
From the CYW89820 Datasheet:
The clock rate in master mode as follows:
• 16kHz 16 bits per frame = 256 kHz
The master clock is generated from the reference clock using an N/M clock divider. In the slave mode, any clock
rate is supported up to a maximum of 3.072 MHz.