Although document cypress-fmac-v5.4.18-2021_0527/README and cypress-fmac-v5.4.18-2021_0527/docs/Infineon_Wi-Fi_Software_UserGuide.pdf does not metioned it, but i really wana to known when this CONFIG_MAC80211 option be used?
This description doesn't make me clear:
This option enables the hardware independent IEEE 802.11 networking stack.
Hi, I am having trouble programming the OTP memory on the CYW43364 (Murata 1FX). When I run cisdump, I get the following error:
# wl cisdump Failed cisdump request: -45 wl: error -23
As I understand it, error 23 is BCME_UNSUPPORTED and indicates that the firmware does not support the operation. I also tried the sd_cis, nvram_dump, and otpdump commands with the same results. I am using the latest firmware as of today:
# wl ver 1.28 RC0.0 wl0: Mar 30 2021 01:12:21 version 184.108.40.206 (7d96287 CY) FWID 01-32059766
Do I need a special firmware which supports the above commands?
Additionally, I read through several application notes, and I was unable to determine what the hardware header for CYW43364 should be. I noticed several variations in which header to use, depending on the exact chipset. What should the hardware header be?Show Less
I can't find any nvram(parameters) file in cypress-fmac-v5.4.18-2021_0527.zip 's firmware directory, which downloaded form https://www.cypress.com/documentation/software-and-drivers-archive/wifi-bt-linux-archive.
I also notice AN232689 ( Wi-Fi software user guide) says:
NVRAM parameters might be included in the firmware image. Do a strings command in /lib/firmware/cypress/cyfmac43430-sdio.bin to check if the nvram parameters are included in the tail of
aw-nm372sm/firmware$ strings cyfmac43430-sdio.bin
this command output a lot of strings, how to check whether nvram is included in firmware image.
if NVRAM parameters already included in the firmware image, Why the brcmfmac driver still look for the corresponding nvram file ？ look like：
"brcmfmac: brcmf_fw_request_firmware: no board-specific nvram available (err=-2), device will use cypress/cyfmac43430-sdio.txt"
if NVRAM parameters not included in the firmware image, , how to get one?Show Less
The driver at https://www.cypress.com/documentation/software-and-drivers-archive/wifi-bt-linux-archive, is too new for me .
How can i find one suitable for linux kernel 3.10.
Any help is greatly appreciatedShow Less
I face a issue about ‘HT Avail timeout’， which lead to exit the wifi driver probe.
I find servel related subject about this. But no one confirm the exact root cause of the issue. Some people say that the isuue is related to LPO_IN, which must be supplied with a 32.768KHz clock.
I search info about CYW43438's LPO and find that LPO is only a option iteam.
The AW-NM372SM uses an internal 26MHz xtal for normal operation and an external secondary low frequency clock for low-power-mode timing. Either the internal low-precision LPO or an external 32.768 kHz precision oscillator is required.
In my design, 32.768KHz clock is not supplied to LPO_IN. Can someone tell me if the issue is caused by this reason？ or there are other reasons？
Is there any way to make the wifi module work normally without connecting the 32.768kHz LPO input?
Any help is appreciated.
Here is my wifi log:
[ 101.970000] Loading modules backported from Linux version v5.4.18-2021_0527-0-gc6ec8acef0b8
[ 102.000000] Backport generated by backports.git v5.4.27-1-0-gf6e8852f
[ 108.260000] brcmfmac_module_init No platform data available.
[ 108.300000] brcmf_ops_sdio_probe Enter
[ 108.350000] brcmf_ops_sdio_probe Class=0
[ 108.350000] brcmf_ops_sdio_probe sdio vendor ID: 0x02d0
[ 108.350000] brcmf_ops_sdio_probe sdio device ID: 0xa9a6
[ 108.390000] brcmf_ops_sdio_probe Function#: 1
[ 108.390000] brcmf_ops_sdio_probe Enter
[ 108.420000] brcmf_ops_sdio_probe Class=0
[ 108.420000] brcmf_ops_sdio_probe sdio vendor ID: 0x02d0
[ 108.460000] brcmf_ops_sdio_probe sdio device ID: 0xa9a6
[ 108.500000] brcmf_ops_sdio_probe Function#: 2
[ 108.500000] brcmf_ops_sdio_probe F2 found, calling brcmf_sdiod_probe...
[ 108.530000] brcmf_sdiod_probe set F2 blocksize to 512
[ 108.530000] brcmf_sdio_probe Enter
[ 108.530000] brcmf_chip_recognition found AXI chip: BCM43430/1
[ 108.560000] brcmf_chip_cores_check [1 ] core 0x800:49 base 0x18000000 wrap 0x18100000
[ 108.560000] brcmf_chip_cores_check [2 ] core 0x812:39 base 0x18001000 wrap 0x18101000
[ 108.570000] brcmf_chip_cores_check [3 ] core 0x829:21 base 0x18002000 wrap 0x18102000
[ 108.580000] brcmf_chip_cores_check [4 ] core 0x82a:9 base 0x18003000 wrap 0x18103000
[ 108.590000] brcmf_chip_cores_check [5 ] core 0x80e:22 base 0x18004000 wrap 0x18104000
[ 108.600000] brcmf_chip_cores_check [6 ] core 0x135:0 base 0x00000000 wrap 0x18105000
[ 108.610000] brcmf_chip_cores_check [7 ] core 0x240:0 base 0x00000000 wrap 0x18106000
[ 108.620000] brcmf_chip_set_passive Enter
[ 108.640000] brcmf_chip_get_raminfo RAM: base=0x0 size=524288 (0x80000) sr=65536 (0x10000)
[ 108.640000] brcmf_chip_setup ccrev=49, pmurev=24, pmucaps=0x39d25f18
[ 108.660000] brcmf_get_module_param Enter, bus=0, chip=43430, rev=1
[ 108.660000] brcmf_sdiod_sgtable_alloc nents=35
[ 108.670000] brcmf_sdio_kso_init Enter
[ 108.670000] brcmf_sdio_drivestrengthinit No SDIO driver strength init needed for chip BCM43430/1 rev 1 pmurev 24
[ 108.690000] brcmf_sdio_probe completed!!
[ 108.690000] brcmfmac: brcmf_fw_alloc_request: using cypress/cyfmac43430-sdio for chip BCM43430/1
[ 108.700000] brcmf_fw_get_firmwares enter: dev=mmc0:0001:1
[ 108.710000] brcmf_ops_sdio_probe F2 init completed...
[ 109.830000] brcmf_fw_complete_request firmware cypress/cyfmac43430-sdio.bin found
[ 165.600000] cfg80211: failed to load regulatory.db
[ 169.920000] brcmfmac: brcmf_fw_request_firmware: no board-specific nvram available (err=-2), device will use cypress/cyfmac43430-sdio.txt
[ 169.940000] brcmf_fw_complete_request firmware cypress/cyfmac43430-sdio.txt found
[ 169.960000] brcmf_fw_request_nvram_done enter: dev=mmc0:0001:1
[ 169.960000] brcmf_fw_request_nvram_done nvram c39ab000 len 684
[ 169.980000] brcmf_sdio_firmware_callback Enter: dev=mmc0:0001:1, err=0
[ 169.980000] brcmf_sdio_clkctl Enter
[ 170.000000] brcmf_sdio_htclk Enter
[ 170.000000] brcmf_sdio_htclk CLKCTL: turned ON
[ 170.000000] brcmf_sdio_clkctl 1 -> 3
[ 170.010000] brcmf_sdio_download_firmware firmware rstvec: 0
[ 170.020000] brcmf_sdio_download_code_file Enter
[ 170.030000] brcmf_sdiod_ramrw write 32768 bytes at offset 0x00000000 in window 0x00000000
[ 170.040000] brcmf_sdiod_ramrw write 32768 bytes at offset 0x00000000 in window 0x00008000
[ 170.170000] brcmf_sdiod_ramrw write 32768 bytes at offset 0x00000000 in window 0x00058000
[ 170.180000] brcmf_sdiod_ramrw write 26582 bytes at offset 0x00000000 in window 0x00060000
[ 170.190000] brcmf_sdio_verifymemory Compare RAM dl & ul at 0x00000000; size=419798
[ 170.200000] brcmf_sdiod_ramrw read 2048 bytes at offset 0x00000000 in window 0x00000000
[ 170.210000] brcmf_sdiod_ramrw read 2048 bytes at offset 0x00000800 in window 0x00000000
[ 172.350000] brcmf_sdiod_ramrw read 2048 bytes at offset 0x00005800 in window 0x00060000
[ 172.360000] brcmf_sdiod_ramrw read 2006 bytes at offset 0x00006000 in window 0x00060000
[ 172.370000] brcmf_sdio_download_nvram Enter
[ 172.370000] brcmf_sdiod_ramrw write 684 bytes at offset 0x00007d54 in window 0x00078000
[ 172.380000] brcmf_sdio_verifymemory Compare RAM dl & ul at 0x0007fd54; size=684
[ 172.390000] brcmf_sdiod_ramrw read 684 bytes at offset 0x00007d54 in window 0x00078000
[ 172.400000] brcmf_chip_set_active Enter
[ 172.410000] brcmf_sdio_clkctl Enter
[ 172.410000] brcmf_sdio_htclk Enter
[ 172.410000] brcmf_sdio_htclk CLKCTL: turned OFF
[ 172.420000] brcmf_sdio_clkctl 3 -> 1
[ 172.420000] brcmf_sdio_clkctl Enter
[ 172.430000] brcmf_sdio_htclk Enter
[ 173.450000] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 173.450000] brcmf_sdio_clkctl 1 -> 1
[ 173.460000] brcmf_sdio_firmware_callback failed: dev=mmc0:0001:1, err=0
[ 173.460000] brcmf_ops_sdio_remove Enter
[ 173.470000] brcmf_ops_sdio_remove sdio vendor ID: 0x02d0
[ 173.470000] brcmf_ops_sdio_remove sdio device ID: 0xa9a6
[ 173.480000] brcmf_ops_sdio_remove Function: 2
[ 173.490000] brcmf_sdiod_intr_unregister Entering oob=0 sd=0
[ 173.490000] brcmf_ops_sdio_remove Enter
[ 173.500000] brcmf_ops_sdio_remove sdio vendor ID: 0x02d0
[ 173.500000] brcmf_ops_sdio_remove sdio device ID: 0xa9a6
[ 173.510000] brcmf_ops_sdio_remove Function: 1
[ 173.510000] brcmf_sdiod_intr_unregister Entering oob=0 sd=0
[ 173.520000] brcmf_sdio_remove Enter
[ 173.530000] brcmf_sdiod_intr_unregister Entering oob=0 sd=0
[ 173.530000] brcmf_detach Enter
[ 173.540000] brcmf_sdio_clkctl Enter
[ 173.540000] brcmf_sdio_htclk Enter
[ 174.560000] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
[ 174.560000] brcmf_sdio_clkctl 1 -> 1
[ 174.600000] brcmf_chip_set_passive Enter
[ 174.650000] brcmf_chip_reset_watchdog Enter
[ 174.650000] brcmf_sdio_clkctl Enter
[ 174.660000] brcmf_sdio_sdclk Enter
[ 174.660000] brcmf_sdio_clkctl 1 -> 0
[ 174.660000] brcmf_sdio_remove Disconnected
[ 174.670000] brcmf_ops_sdio_remove Exit
We are using IMX7D with android 9.0 in our product with a 1MW module. I want to set a static random address for the device.
How can this be achieved in android, can someone please shed some on light on it?
Thank youShow Less
Please find the below different cases we experimented and the issue we are facing :
case 1) BT Classic application and connecting using Android shutter Bluetooth symbol
When there is only a BT classic application running on the board, and an Android device is used to connect to the board. The shutter on Android device is swiped to touch upon the 'bluetooth symbol' to turn on the bluetooth, and then the device is selected, which upon touching, pops up a window for pairing, and subsequently upon entering the pass code the Android device connects to the board successfully. Absolutely no issue in this case.
case 2) BT Classic application and BLE application on target board and connecting using BLE scanner app on Android device
When there is BT Classic app and BLE app, two different applications running simultaneously on the board, and BLE scanner app on Android device is used to connect to the board. But this time, we used an Android application called "BLE scanner" to get connected to the board, and the connection was smooth and successful without any prompt for pass code [as we know, BLE does need pass code to get connected to any device]. Absolutely no issue in this case as well.
case 3) BT Classic application and BLE application on target board and connecting to board using Android shutter bluetooth symbol intending to connect to BT Classic only.
Now, When we run BT Classic app and BLE app, two different applications both simultaneously on our custom board, and an Android device is used to connect to the board. The same way as in case (1) we tried to connect to the board using 'bluetooth symbol' on shutter, intending to connect to BT app only on target board, but this time around the pop up on the Android device doesn't ask for pass code, it simply gives two options either to "PAIR" or "CANCEL" , upon selecting "PAIR' option the device gets connected successfully, and from the log on the target custom board, we found that, it is getting connected to the BLE application, but not to the BT application. Typically, when we connect to the BT Classic, the android device should produce a pop up for pass code, but it is not happening so.
We are curious to know, why is the device getting connected to the BLE but not to the BT Classic even when we select the 'bluetooth symbol' on the Android shutter, and to be noted that, we are not running the BLE android application [BLE scanner] on the Android device.
Even in the case when we have BLE enabled on the target board, the user should be prompted for pass code on the Android device when user tries to connect.
Kindly shed some light on this issue i.e., How BT classic can still send pass code to the client Android device even when there is BLE enabled on the target board.
I have a WIFI/BT module from USI that uses the 43438 chipset. This module is connected to an IMX6 processor running Android 9. Bluetooth classic and BLE client works well, but BLE server (advertiser) not.
Using BLE apps from PlayStore I get messages like your device doesnt support this functionality or more specific ADVERTISE_FAILED_TOO_MANY_ADVERTISERS.
USI has send me a more recent HCD file, but not work too. Could someone with experience at BLE and Android give me some directions about this? What I need to do to enable BLE server in Android? Is something related to HCD or libbt?
My company is using LBEE5HY1MW in our product. According to the datasheet its support Bluetooth 5.0, However, the LMP version I read through hcitool is 4.1.
I would like to know, does the chip also supports the BLE security as specified in Bluetooth core specification 4.2?
Or does it support any of the Bluetooth 4.2 Core specifications?
The 1MW module in our product is involved in security-related compliance.
Any help is really appreciated.
We gonna choose a module that uses CYW43438 chipsets and I searched all over the related websites but cannot found any FMAC driver for 5.10, however the kernel 5.10 builtin the bcm43x FMAC driver, but I'm not sure if the bcm43438 was supported.