When 20706 as BLE peripheral, how to update connecnt parameter. I didn't find any API
because of HCI_ERR_INSTANT_PASSED (0x28) connect down event occur frequently,
I want to update slave_latency when connect up.
and I also find wiced_bt_ble_get_connection_parameters didn't work well, when using this API 20706 will pending and watch dog reset.
Do you have any throughput reports (5G/2.5G)for our reference?
My environment is Sigmastar SAV530Q(SDIO 2.0)+Linux kernel 4.9.84+CYW43455.
We received a question from a customer regarding the CYBLE-212006-01.
The CYBLE-212006-01 supports Extended Range, but is there any particular problem with using it at home?
They are wondering if there is any impact on other devices when the transmit power is increased to support Extended Range.
I thought that CYBLE-212006-01 has no particular problem since it has already obtained FCC, MIC, CE, and other certifications.
Am I correct in my thinking? Also, is there anything I should be aware of?
Hi cypress team,
I am work on spp sample code with CYBT-343026. And I want to keep my 343026 in slave, but sometimes there's a role switch that my 343026 become master. I have tride wiced_bt_dev_switch_role to switch it back to slave but it doesn't work. What can I do to keep it in slave mode.Show Less
Our customer is planning to use the BT module as follows.
They want to know the recommended current supply capability when using the module at 3.3V.
Could you tell me where I can find the answer for that?
What is the Bluetooth class of CYBLE-416045-02?
I saw the sentence "TX output power: -20 dbm to +4 dbm" in the datasheet, is it Class2?
I would like to update the application via the HCI-UART. I have read the
- AIROC™ HCI Firmware Download Guide
- AIROC™ HCI Control Protocol
- AIROC™ Over-the-Air Firmware Upgrade Library
When I sniff the ModusTool when it downloads firmware to the device, I have these phases,
- HCI_RESET - expected.
> 01 4d fc 05 1c d2 00 00 01 < 04 0e 05 01 4d fc 00 ab <fail>
- Mini-driver download
- Launch ram
- Update baud rate
- A strange response ... after baud change... < 04 0e 04 01 ce ff 00 ???
- Config/SS write
- Main image write
In 6, it looks like a response to a chip erase? Was this just garbage or does the mini-driver erase the flash?
Can I skip 7,8 if I just want to update the application software, but keep all MAC, etc initial parameters.
Is the packet in '2' of any consequence. Could I skip it. Is it documented?
Does CYW43439 support WPA3-Personal in SoftAP mode by linux FMAC driver?