Wireless Connectivity Forum Discussions
Browse the Community
AIROC™ Wi-Fi and Wi-Fi Bluetooth Combos
AIROC™ Wi-Fi MCUs
AIROC™ Bluetooth
Featured Discussions
I'm using both the 1dx and 1mw module from murata :
https://www.murata.com/en-us/products/connectivitymodule/wi-fi-bluetooth/overview/nxp-imx
These use the CYW4343W and the CYW43455 respectively, and communicate over an sdio bus.
But every now and then it fails to load the firmware giving me only this error:
brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
But I have no idea what is causing this and its driving me mad, I thought it might be that it was powering on to late, so i gave it power early, but it didn't help, tried the latest firmware, didn't help.
These messages related to the module also show up in dmesg:
mmc1: SDHCI controller on 30b50000.mmc [30b50000.mmc] using ADMA
mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
mmc1: queuing unknown CIS tuple 0x80 (6 bytes)
mmc1: new ultra high speed SDR104 SDIO card at address 0001
brcmfmac: F1 signature read @0x18000000=0x15264345
brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.bin failed with error -2
brcmfmac mmc1:0001:1: Falling back to sysfs fallback for: brcm/brcmfmac43455-sdio.bin
Details of the system using it:
Linux kernel 5.10.72
Debian 11 Bullseye
imx8mm processor (aarch64)
I feel like it used to be more stable, but i can't think of anything i changed that affects it.
Can anyone help me figure out this error or point me to some documentation that can help me?
Show LessDear sir,
Does cypress-fmac-v5.15.58-2023_0222 apply for linux kernel 5.10.153? thanks.
Hello,
Is it possible to run the CYW20706 off an external frequency reference?
Using an external frequency reference was documented under the older version of the cyw20706 datasheet ( Document Number: 002-14790 Rev. *B). This part of the documentation has since been removed in the subsequent datasheets (Document No. 002-19479 Rev. *B).
We are currently trying to run CYW20706UA2KFFB4G off an external 24MHz frequency reference (20 ppm frequency tolerance) with no success. The CYW20706 responds over HCI, and replies success to HCI test commands such as the radio TX test (01 51 FC 10 66 55 44 33 22 11 01 00 03 01 03 11 00 08 FD 00). However, we could not see any transmission over the PHY on our Bluetooth spectrum analyzer. As the antenna design and supply voltages are identical to another working custom board that ran on a crystal oscillator, we have a strong suspicion that it is the external frequency reference.
Would really appreciate if anyone could shed some light on this.
Thanks
Tong
Show Less
Hi,
I successfully tested the TCP Client and TCP Server example using 2 CY8CKIT-062-WIFI-BT. The only configuration setting I changed was the SSID and Password. Everything worked as expected.
I then ported the TCP Client example to my custom board based on CY8C6247FDI-D32 and CY4343W and it is failing in netifapi_netif_add() when calling tcpip_api_call(). Any suggestion?
Just wanted to add that the WiFi Scan example from modus toolbox works fine on my board - this proves that the board itself is OK from HW point of view.
Show Less
I am trying to get started using the CYBL013025 device on a Cypress EVAL board plugged into USB.
My first problem is that the documents say that the device will come from the factory in TEXT mode, but it is in BINARY mode. Very hard to work with using a terminal in Binary mode. I bought a second unit and EVAL board only to find it is also in BINARY mode from the factory. I have no idea how to get it into TEXT mode.
The next problem is that they discuss the CYSPP pin over and over, but I have NO IDEA which pin that is. I have looked every where and it never says. How do I know which pin is the CYSPP pin?
Please help! If I can just get started I will be able to learn!
Topher
Show Less
Hi,
I am programming the CYBT-343026 bluetooth module, and couldn't find any information on setting the low power sniff mode and pade mode.
Please help on this subject.
Show LessHi,
For our product under development, we need to implement some basic tests commands, and I've been able to implement the Set_Tx_Carrier_Frequency_ARM Cypress Vendor Specific HCI Command (as per described in "BLUETOOTH RADIO TEST CASES AND PROVISIONING HCI COMMANDS" documentation from infineon/cypress).
I call this command from the embedded application in the CYBT-483056-02 CPU using wiced_bt_dev_vendor_specific_command API call. I've observed that the command was running fine only if there's no call to wiced_bt_dev_set_connectability or wiced_bt_dev_set_discoverability commands with page_mode different from BTM_NON_CONNECTABLE and/or inq_mode different from BTM_NON_DISCOVERABLE. I mean that if I call one of this function to enable discoverability or connectability, then the test command will not work (there's no TX on the antenna in this case). I've also tried to reset the discoverability and connectability to BTM_NON_CONNECTABLE and BTM_NON_DISCOVERABLE before sending the hci test command, but it do not work. We need to reset the device before being able to issue the test mode hci command.
Also, the call to wiced_bt_dev_vendor_specific_command will not return an error when the TX is not working (after discoverability or connectability) so there's no way for us to warn the test tool that something is wrong with the configuration...
Can you help us by looking at the ROM code to find out what can cause the problem and maybe find a workaround ?
The HCI code that I send is OGF:0x3F, OCF:0x0014, which result in opcode 0xfc14.
Also, I can reproduce the same behavior in the following cases :
* On the eval board with modificed empty wiced app (only call the two functions wiced_bt_dev_set_connectability and wiced_bt_dev_set_discoverability to enable discoverability and connectability, the send the test command using wiced_bt_dev_vendor_specific_command call)
* By using the empty wiced app without modification and using CyBluetool to drive the eval board through HCI commands and agian, setting discoverability on or connectability on then sending the test command...
All this indicate that it's not related to our software, but rather to some ROM code behavior that might be normal, but is not described in the documentation, and for which we would like to find a workaround.
Regards, Jerome
Show LessWhat is the best way to develop for the CYW54590? Relatively new electrical engineer here, and I don't see any development boards or anything similar available for this chip.
Show LessHi, I want to send data via HCI to the attached microcontroller. I followed the example, mtb-example-btsdk-rfcomm-spp-multi-port-master, from github and I've initialized transport with the following:
const wiced_transport_cfg_t transport_cfg =
{
.type = WICED_TRANSPORT_UART,
.cfg =
{
.uart_cfg =
{
.mode = WICED_TRANSPORT_UART_HCI_MODE,
.baud_rate = HCI_UART_DEFAULT_BAUD
},
},
.rx_buff_pool_cfg =
{
.buffer_size = TRANS_UART_BUFFER_SIZE,
.buffer_count = 4
},
.p_status_handler = NULL,
.p_data_handler = process_rx_command,
.p_tx_complete_cback = NULL // tx_complete_callback
};
but whenever I call any of the wiced_transport_send_buffer, wiced_transport_send_data, or wiced_transport_send_hci_trace I get a result of WICED_ERROR. Is there anything else that I need to enable or turn on in order for transport to work? Thanks.
Show LessI'm having trouble finding the cyfmac43455-sdio.bin and cyfmac43455-sdio.clm_blob files in the latest tarballs. They were included in previous releases, but seem to be missing now. However, according to the Infineon_Wi-Fi_Software_UserGuide.pdf, the CYW43455 is still listed as a supported device. Can anyone shed some light on this issue or provide some guidance on how to proceed?
Show Less