AIROC™ Bluetooth Forum Discussions
Hi Infineon.
Are PSoC BLE devices Cyber Resilience(Laws and regulations that add security requirements to RED(RADIO EQUIPMENT DIRECTIVE)) compliant?
If not, are there any plans to support it in the future?
Best Regards.
YuMa
Show LessAIROC™ Bluetooth® SDK 4.5.1 is targeted for the CYW20706, CYW20719B2, CYW20721B2, CYW20736, CYW20835B1, CYW20819, CYW20820, CYW20829, CYW89820, CYW43012 AIROC™ Wi-Fi & Bluetooth® combo chips (for embedded Bluetooth® development only), and CYW5557x AIROC™ Wi-Fi & Bluetooth® combo chips. ModusToolbox™ software with the Bluetooth® SDK software library provides a complete development environment to allow you to quickly create Bluetooth®-enabled IoT solutions such as smartwatches, medical devices, or home automation platforms. This document describes the features and known limitations of Bluetooth® SDK 4.5.1.
Show Lesshi Sir,
CYW20721 DS mentioned I2S clock in master mode could be:
- 44.1 kHz x 32 bits per frame = 1411.2 kHz
- 48 kHz x 32 bits per frame = 1536 kHz
May I know how to setting I2S Clock for those 2 setting?
Thanks.
Austin
Show LessHi infineon.
Could you please let us know RED(Radio Equipment Directive) compliance status at PSoC4100BLE/PSoC4200BLE/PSoC63BLE?
Best Regards.
YuMa
Show LessHello
I had initially created example project Bluetooth_LE_HelloSensor and added my SPI driver code. It works well.
When I replicate the same setting for Battery Server example with OTA, the SPI gets stuck here:
I am not using hal driver but pdl one. What can be the issue?
Show Less
hello,
i am trying to connect my central device to my peripheral CY-BT 343026 EV board and when i am try BTM_ENCRYPTION_STATUS_EVT this event call often and 3 times at a time and i don't know what this mean, can anyone explain me?
these are the logs of CY-BT 343026
hello_sensor_conn_up d1 92 29 82 b9 bf id:1
:NVRAM write 155
hello_sensor_gatts_req_cb. conn 1, type 5
req_mtu: 170
hello_sensor_management_cback: 0xc Encryption Status Event: bd ( d1 92 29 82 b9 bf ) res 0encryp change bd ( d1 92 29 82 b9 bf )
res: 0 hello_sensor_management_cback: 0xc Encryption Status Event: bd ( d1 92 29 82 b9 bf ) res 0encryp change bd ( d1 92 29 82 b9 bf ) res: 0
hello_sensor_management_cback: 0xcEncryption Status Event: bd ( d1 92 29 82 b9 bf ) res 0encryp change bd ( d1 92 29 82 b9 bf ) res: 0
hello_sensor_management_cback: 0x17ncryption Status Event: bd ( d1 92 29 82 b9 bf ) res 0encryp change bd ( d1 92 29 82 b9 bf ) res: 0
Dear Team,
I had gone through detailed document available @ https://www.infineon.com/dgdl/Infineon-EZ-Serial_WICED_Firmware_Platform_User_Guide_for_CYBT-4830XX-02_EZ-BT-UserManual-v01_00-EN.pdf?fileId=8ac78c8c7ddc01d7017ddd0caa1f5d13&utm_source=cypress&utm_medium=referral&utm_campaign=202110_globe_en_all_integration-other_resource&redirId=OR267 and found typing mistake [Refer attached CYBT-483056-02 Snip.png] for Table 3-1 Binary Event Data of EZ-Serial BOOT Event as this being not used any where in this document.
And in Table 3-1 mention header value "80 12 02 01" but this should be "C0 12 02 01", correct ?
Realterm serial capture program gives correct output on command "$c0 0 4 $10 $6d" as "C0150410000012455A2D53657269616C2037433A34373A3341AD"
But while tried with below commands to run through, not able to found any response back. [Refer attached CYBT-483056-02 Realterm.png]
$80 04 02 01 05 03 00 01 $29 // No back response -> EZ-Serial application version
or
$c0 04 02 01 05 03 00 01 $69 // 80 02 02 02 09 02 2A or 80 02 02 02 0A 02 2B -> EZ-Serial application version
Let me know if I am lacking behind anywhere.
BR,
NaineshD.
Show Lesshi,
About program BD address by WICED_MOD_Prog_v1.5.19.102 tool
https://community.infineon.com/t5/Studio-Bluetooth/WICED-Module-Programmer-Download/td-p/290595
I am wondering where is proper address or SV ID BD address in the module??
May I use wiced_hal_write_nvram API to change BD address??
Thanks
Austin
Show Less