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 22.214.171.124 (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
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
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.
We use AP6212 (BCM43438 based) module on our board and we need wl utility to do compliance testing. Local FAE could provide the wl binary with bcmdhd driver, but we use brcmfmac driver, can anyone help me to provide this? Thanks
Our hardware platform / Env:
- Linux Kernel 4.19, armhf
- Wi-Fi driver: brcmfmac
- Raspberry Pi CM3+ based
We are using Murata 1MW chip for BLE+WIFI with am335x processor.
To get the drivers, we have downloaded the fmac release cypress-fmac-v5.4.18-2020_0925 and tried cross compiling but getting below errors:
| Your kernel headers are incomplete/not installed.
| Please install kernel headers, including a .config
| file or use the KLIB/KLIB_BUILD make variables to
| set the kernel to build against, e.g.
| make KLIB=/lib/modules/3.1.7/
| to compile/install for the installed kernel 3.1.7
| (that isn't currently running.)
Makefile:40: recipe for target 'defconfig-brcmfmac' failed
make: *** [defconfig-brcmfmac] Error 1
Running linux version 4.15, even in makefile it is mentioned as KLIB = (uname -r), then why is it giving error for 3.17 kernel headers.
Can you please have a look on this and also let me know which fmac release can be used for am335x and kernel version 4.19.94